# Windsurf MCP: Post to Social Media From Windsurf

**Source:** https://posteverywhere.ai/connectors/windsurf

---

# Add PostEverywhere to Windsurf in one JSON block

Yes. Windsurf reads a standard MCP config file, so adding PostEverywhere is one JSON block and a restart.

Windsurf uses the standard Model Context Protocol config format, so PostEverywhere drops in the same way any other MCP server does. Add the block, restart, and the publishing tools are available to Cascade alongside everything else it can already do.

The only Windsurf-specific detail is where the file lives. It is not in the app settings UI, it is a JSON file at ~/.codeium/windsurf/mcp_config.json, and Windsurf reads it at startup rather than watching it, so a restart is genuinely required.

Because the configuration is a file rather than a settings screen, it is easy to version or copy between machines. It is also easy to forget, so if you move to a new laptop the server will not follow you until the file does.

[Start your 7 day trial](https://app.posteverywhere.ai/signup)[All connectors →](https://posteverywhere.ai/connectors)Card required · $0 charged today · cancel any time

## How to connect PostEverywhere to Windsurf

Windsurf reads its MCP config from a file rather than a settings screen, so this is a copy, paste and restart.

Before you start

- Windsurf installed, with access to your home directory to edit the config file.
- Node on your PATH, since the server runs through npx.
- A PostEverywhere API key and at least one authorised social account.
~/.codeium/windsurf/mcp_config.jsonjson`{
  "mcpServers": {
    "posteverywhere": {
      "command": "npx",
      "args": ["-y", "@posteverywhere/mcp"],
      "env": { "POSTEVERYWHERE_API_KEY": "pe_live_YOUR_KEY" }
    }
  }
}`

- 1Get an API key from your PostEverywhere account. The same key works for the REST API and the SDK.

- 2Add the block below to ~/.codeium/windsurf/mcp_config.json.

- 3Restart Windsurf. The 33 tools appear once it reloads its MCP configuration.

**Worth knowing:** Windsurf reads the config at startup, not continuously. If the server does not show up, a restart is almost always the answer.

## What you can ask Windsurf once it is connected

Windsurf suits the moment just after you ship, when the announcement is the last thing standing between you and moving on. Each one maps onto a real tool, covering scheduling, [AI captions](https://posteverywhere.ai/ai-content-generator) and [analytics](https://posteverywhere.ai/social-media-analytics). The [AI agents page](https://posteverywhere.ai/agents) has the full surface.

Announce a shipped feature without breaking flow

Draft a launch post while the branch is still open

Turn a set of release notes into posts for each platform

Check what is already scheduled before adding more

Reschedule anything that clashes with a launch

Retry a post that failed, and read the reason

Cascade gains the publishing tools alongside everything else it can already do, so shipping and announcing become one task rather than two.

### What the tools cover

The local server exposes the same 33 tools as the hosted one, so nothing is traded away by running it yourself. Scheduling, media upload, campaigns, analytics and account health are all present, and Cascade can chain them, which is what makes a single prompt able to draft, check the queue and schedule in one pass.

### Prompts that work, and what comes back

“Write a release note for what I just merged and schedule it for tomorrow at 9.”

Cascade uses the change you are looking at as the source, drafts the note and queues it.

“Draft three posts from this README and space them over the week.”

It writes three distinct angles rather than three rewrites of the same sentence, then schedules them.

“Show me what is scheduled before I add anything else.”

It lists the queue with times, so you can see the gaps rather than guess at them.

## Windsurf MCP troubleshooting

The three things that actually go wrong, and what fixes each one.

The server does not appear after saving the file

Windsurf reads mcp_config.json at startup rather than watching it. Restart Windsurf completely; reloading the window is not always enough.

The file has a syntax error and Windsurf says nothing

A trailing comma or a missing brace makes the whole file invalid, and it fails quietly. Paste it through a JSON validator before restarting.

npx is not found

The local server shells out to npx, so Node has to be installed and on the PATH that Windsurf inherits. Launching from a terminal rather than the dock sometimes fixes a stale PATH.

## What it will not do

Worth knowing now rather than after you have started a trial.

- The server only runs while Windsurf is running. Already-scheduled posts still publish from our side.
- Editing the config while Windsurf is open does nothing until you restart it.
- It does not sync between machines. The config is a local file, so a new laptop needs the same block again.

## When to use Windsurf rather than another editor

Windsurf suits someone who already keeps their tooling in config files and wants publishing to live there too, rather than behind a browser login.

Reference material: [Windsurf MCP documentation](https://docs.windsurf.com/windsurf/cascade/mcp), [The Model Context Protocol spec](https://modelcontextprotocol.io). The full agent surface, including the REST API, is on the [AI agents page](https://posteverywhere.ai/agents).

## Included on every paid plan from $9/mo

The server is free and open source. You need a PostEverywhere plan for the API key, from $9 a month. One key covers the connector, the [REST API](https://posteverywhere.ai/social-media-api) and the SDK. Using a different editor? [See all connectors](https://posteverywhere.ai/connectors), wire it up from [n8n, Make or Zapier](https://posteverywhere.ai/integrations), or read how the whole [agent setup](https://posteverywhere.ai/agents) fits together.

[Start your 7 day trial](https://app.posteverywhere.ai/signup)

## Windsurf MCP FAQ

### How do I connect PostEverywhere to Windsurf?

Get an API key from your PostEverywhere account. The same key works for the REST API and the SDK. Then: Add the block below to ~/.codeium/windsurf/mcp_config.json. Then: Restart Windsurf. The 33 tools appear once it reloads its MCP configuration. There is no plan restriction on this client.

### Can Windsurf post to social media?

Yes. Windsurf reads a standard MCP config file, so adding PostEverywhere is one JSON block and a restart. Windsurf suits the moment just after you ship, when the announcement is the last thing standing between you and moving on.

### Where does the Windsurf MCP config file live?

At ~/.codeium/windsurf/mcp_config.json. It is a file rather than a settings screen, so you edit it directly. Windsurf reads it on startup, so restart after saving or the server will not appear.

### Do I need the hosted server or the local one?

Windsurf uses the local open-source server, which runs through npx and authenticates with an API key. The hosted OAuth connector is for Claude, ChatGPT, Grok and Cursor. Both expose the same 33 tools.

### Does this work with Cascade?

Yes. Once the server is registered, the tools are available to Cascade like any other MCP tool, so publishing can be one step of a longer task rather than a separate errand.

### What does it cost to use Windsurf this way?

The server is free and open source. You need a PostEverywhere plan for the API key, from $9 a month. Every plan has a 7-day trial and a card is required to start it.

## Other assistants

[Claude](https://posteverywhere.ai/connectors/claude)[ChatGPT](https://posteverywhere.ai/connectors/chatgpt)[Cursor](https://posteverywhere.ai/connectors/cursor)[Claude Code](https://posteverywhere.ai/connectors/claude-code)[Grok](https://posteverywhere.ai/connectors/grok)[Cline](https://posteverywhere.ai/connectors/cline)[Zed](https://posteverywhere.ai/connectors/zed)[Codex CLI](https://posteverywhere.ai/connectors/codex-cli)