Windsurf · agentic IDE

Publish with Windsurf

Windsurf's Cascade agent loads MCP servers from a JSON config. With Inklate connected, 'ship it' can include the post about shipping it.

What Windsurf can do

The full pipeline, by prompt

Create and edit posts in your organization's library, ready for review or straight to the queue.

Queue posts with explicit timezone offsets — 9am always means 9am, never a UTC surprise.

Push posts live to connected LinkedIn profiles and company pages the moment you say so.

Read impressions, reactions, comments, shares, and clicks — the same self-updating numbers as the dashboard.

Setup

You'll need an Inklate organization and, for key-based setups, an API key from Settings → API keys in the dashboard.

1
Edit the MCP config
Add Inklate to ~/.codeium/windsurf/mcp_config.json with your organization API key.
mcp_config.json
```
{
  "mcpServers": {
    "inklate": {
      "serverUrl": "https://api.inklate.com/mcp",
      "headers": { "Authorization": "Bearer inklate_your_org_key" }
    }
  }
}
```
2
Refresh Cascade
Open the Cascade panel, refresh MCP servers, and confirm Inklate's tools are listed.
3
Publish from the flow
Ask Cascade for drafts, schedules, or analytics mid-task — no context switch, no copy-paste.

Try these first

“Draft a post about the new onboarding flow and schedule it for Thursday 9:00 AM CET.”

“Reschedule anything queued for Friday to next Monday morning.”

“Show me this week's engagement numbers by post.”

Questions

Does Windsurf support remote MCP servers?

Yes — Cascade supports remote servers via serverUrl in mcp_config.json. If your build is stdio-only, bridge with mcp-remote.

Also works with

Create an organization, connect LinkedIn, and your agent publishes with the same guardrails as your team.