MCP server

A social media MCP server that keeps you in the loop

Connect Claude, Codex, Cursor or any MCP client to Surgr. Your agent drafts posts for X and proposes when they should go out. Nothing is scheduled until you approve it.

Why there's a review step

Agents write fast, and a public post is hard to take back. Surgr sits between the two: your agent does the drafting and the scheduling legwork, and you make the call. An approval covers the exact revision, accounts and time you saw, so an edit after you approve means a fresh review rather than a surprise post.

Prepare for review

The recommended connection. Your agent creates drafts, uploads media and proposes times. You approve every post.

Schedule approved posts only

For automations that run after you sign off. It can't create or edit drafts; it only schedules posts you already approved.

What your agent can do

Six tools, each limited by the permissions of the connection it uses.

create_review_post: Create a draft for review, optionally with a proposed time. It never approves or publishes.

update_review_post: Revise a draft you haven't approved yet, and send it back to your review queue.

get_review_feedback: Read a post's current revision, the changes you asked for, and its activity.

list_schedule: Read what's scheduled, proposed and recently published, with its real review and delivery state.

schedule_approved_post: Schedule-approved connections only: send a post you already approved, at the time you approved.

read_results: Read publish receipts and metrics. Missing or stale numbers are labeled, not guessed.

Connect in two minutes

  1. Sign in to Surgr, open Agents and choose Connect agent.
  2. Name the connection after your agent, pick its access and copy the key. It's shown once.
  3. Add Surgr to your client with one of the snippets below, then ask your agent to draft a post.

Endpoint: https://surgr.ai/api/mcp, over Streamable HTTP, with the key sent as Authorization: Bearer.

Claude Code

Run once in your terminal.

claude mcp add --transport http surgr https://surgr.ai/api/mcp \
  --header "Authorization: Bearer $SURGR_API_KEY"

Codex

Add to ~/.codex/config.toml, with your key in SURGR_API_KEY.

[mcp_servers.surgr]
url = "https://surgr.ai/api/mcp"
bearer_token_env_var = "SURGR_API_KEY"

Cursor

Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json.

{
  "mcpServers": {
    "surgr": {
      "url": "https://surgr.ai/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_SURGR_API_KEY" }
    }
  }
}

Questions

Can my agent publish without me?
No. Over MCP an agent can create and revise drafts and propose times, but only you approve a post. A schedule-approved connection can send a post you already approved, at the approved time, and nothing else.
Which MCP clients work?
Any client that connects to a remote server over Streamable HTTP and can send a bearer token, including Claude Code, Codex and Cursor.
Which platforms can it post to?
Publishing starts with X. Other channels depend on each platform's approval and your connected account; Channels in Surgr shows what's ready.
Is there a REST API too?
Yes. The same key works with Surgr's API at /api/v1, with the same permissions.
What does it cost?
API and MCP access are part of Early Pro at $9 a month. The Free plan covers drafting, scheduling and your first 10 publishes each month.

More: schedule tweets with Surgr, compare Surgr with other schedulers.