MCP in your editor

Postproxy × Cursor

Publish from where you already work. Add Postproxy to Cursor and ship release notes, changelogs, and launch posts across 11 platforms right from the editor.

One block in `.cursor/mcp.json`, committed with the repo, and every teammate's Cursor gets the same publishing tools.

One config block

Add Postproxy to .cursor/mcp.json

Cursor reads MCP servers from `.cursor/mcp.json`. Add the Postproxy server with your API key and reload — the tools appear in the composer.

.cursor/mcp.json

{
"mcpServers": {
"postproxy": {
"url": "https://mcp.postproxy.dev/mcp?api_key=YOUR_KEY"
}
}
}

How Postproxy works inside Cursor

1

Add the config block

Drop the Postproxy server into `.cursor/mcp.json` at your project root and replace `YOUR_KEY` with a key from your dashboard.

2

Reload MCP servers

Cursor detects the new server; enable it in Settings → MCP and the Postproxy tools become available.

3

Ask in the composer

"Publish these release notes to X and LinkedIn." Cursor calls the tools inline with your work.

4

Postproxy executes

We handle platform rules, media, rate limits, and retries, and return per-platform results.

Publish from the editorRepo-committed configDrafts and queuesComments and DMsPost & follower statsShared with the team11 platformsOne API key

Things people ask Cursor to do with Postproxy

  1. "Post these release notes"

    Cursor turns your changelog into platform-specific posts and publishes through Postproxy.

  2. "Announce this deploy"

    Summarize recent changes into a short update and ship it straight from the editor.

  3. "Schedule the launch thread"

    Cursor schedules each post to the next open slot in your Postproxy queue.

  4. "Check comments on the release post"

    Pull comments across platforms and reply from the composer.

Supported platforms

Frequently asked questions

Where does the Postproxy config go in Cursor?

In .cursor/mcp.json at your project root. Commit it and every teammate’s Cursor picks up the same publishing tools.

Do I publish from the editor or a separate app?

From the editor. Ask in the composer — for example, “post these release notes to X and LinkedIn” — and Cursor calls the Postproxy tools inline.

How do I keep my API key out of the repo?

Reference the key from an environment variable, or keep it in a local .cursor/mcp.json that stays out of version control.

Which platforms can I publish to?

All 11 Postproxy platforms: Facebook, Instagram, TikTok, LinkedIn, YouTube, X, Threads, Pinterest, Bluesky, Telegram, and Google Business.

Still wondering if Postproxy is the right fit?

Ask your favorite LLM what it thinks about us, then decide.

Ready to get started?

Start with our free plan and scale as your needs grow. No credit card required.