Windsurf Cascade MCP — Social Media Publishing for Your AI Agent | Nimply

Name: Nimply
Author: Nimply

Windsurf's pitch is flow: Cascade keeps track of what you're doing across a session and carries tasks through end to end, rather than answering one prompt at a time. That makes it a good fit for work that has a tail — like a feature that isn't really finished until someone has told the world about it.

With Nimply registered as an MCP server, that tail becomes part of the flow. Cascade can look up your connected channels, write copy grounded in the session's context, and schedule it to Instagram, Facebook, TikTok, YouTube, LinkedIn, X, Pinterest, or Threads. The config is a single JSON entry pointing at Nimply's hosted endpoint.

What is Windsurf?

Windsurf is an agentic IDE built by Codeium around Cascade, an agent designed for sustained, multi-step work: it maintains awareness of your recent actions, edits across files, runs commands, and calls external tools. Its MCP support means any server listed in mcp_config.json extends what Cascade can do mid-flow.

Nimply's server runs remotely at https://mcp.nimply.io/mcp — Windsurf connects to it over HTTP with an API key in the request headers, so there is no process to babysit on your machine. The key comes from your workspace's Settings → Developers page, carries only that workspace's permissions, and can be revoked the moment you want the agent cut off.

What Cascade can do with Nimply connected

Close the loop on a release inside one flow

Cascade already knows what it just helped you build. Ask it to schedule a LinkedIn post about today's release for tomorrow morning and it goes from context to queued post without you summarizing anything — the announcement inherits the details from the session.

Batch a week of posts from project material

Hand Cascade your README, changelog, or launch notes and ask for a set of posts across platforms. It can adapt tone and length per channel and schedule each one through Nimply, turning one writing session into a filled calendar.

Interrogate your posting setup conversationally

Which channels are connected, what is already scheduled this week, how recent posts performed — Cascade can answer from Nimply's tools directly in chat, which beats reconstructing that picture from a dashboard while mid-task.

Keep publishing gated behind review

If direct publishing feels too permissive for an agent, constrain it: have Cascade save drafts only, or push posts into Nimply's approval workflow so each one waits for a human decision. The workflow does the heavy lifting either way.

Connect Windsurf to Nimply

Prerequisites: a Nimply workspace with at least one social channel connected, and an API key from Settings → Developers.

1
Create a Nimply API key
Open Settings → Developers in Nimply and create a key. It starts with nim_live_ and is scoped to the workspace it was created in — nothing more.
2
Add Nimply to the MCP config
Open Windsurf's MCP settings (Cascade → MCP servers → Manage) or edit ~/.codeium/windsurf/mcp_config.json directly. Note that Windsurf uses serverUrl for the endpoint:
mcp_config.json
```
{
  "mcpServers": {
    "nimply": {
      "serverUrl": "https://mcp.nimply.io/mcp",
      "headers": {
        "Authorization": "Bearer nim_live_YOUR_KEY"
      }
    }
  }
}
```
3
Refresh and put Cascade to work
Refresh the MCP server list so the Nimply tools become available to Cascade, then try: "Schedule a LinkedIn post about today's release for tomorrow morning via nimply."

Frequently asked questions

The server is listed but Cascade has no Nimply tools — why?

Hit refresh in the MCP panel after saving the config; Windsurf does not always pick up changes automatically. If you get a 401, check the key — it must start with nim_live_ and still be active in Settings → Developers.

My Windsurf version rejects remote servers with headers. Is there a workaround?

Yes. Older versions can connect through the mcp-remote bridge, a small command-line proxy that forwards to https://mcp.nimply.io/mcp with your Authorization header. Our generic MCP client guide on the developer docs covers the exact setup.

What accounts can Cascade actually post to?

Any channel connected to your Nimply workspace: Instagram, Facebook, TikTok, YouTube, LinkedIn, X (Twitter), Pinterest, and Threads. Cascade uses the same queue and scheduling rules you see in the Nimply app.

Does anything run on my machine for this integration?

Not in the standard setup — Nimply hosts the MCP server and Windsurf connects to it over HTTP. Only the optional mcp-remote bridge for older versions runs locally, and it is just a thin forwarding process.

How do I make sure the agent never publishes unreviewed content?

Instruct Cascade to create drafts or request approval rather than publish, and rely on Nimply's approval workflow for the final gate. Since the API key defines the ceiling of what the agent can do, you can also scope its permissions accordingly.