GUIDE
MCP for social media: let your AI agent post for you
Last updated
Short answer
A social media MCP server exposes a scheduler's actions (create a post, check channel limits, schedule, list channels) as Model Context Protocol tools, so an MCP client like Claude, Claude Code, Cursor or Codex can post for you. Mynahcast's server is at https://api.mynahcast.xyz/mcp, and posts from agent keys wait for human approval.
How a social media MCP server works
The Model Context Protocol (MCP) is an open standard for connecting AI applications to tools. A server lists tools with JSON schemas; the client (Claude Desktop, Claude Code, Cursor, Codex and others) shows them to the model, and the model calls them with arguments.
Mynahcast's MCP server speaks stateless JSON-RPC over streamable HTTP at https://api.mynahcast.xyz/mcp. Every request carries an API key as Authorization: Bearer; keys never go in the URL. Tools are named mynahcast_* and filtered by the key's scopes, and every tool that changes something accepts dry_run so an agent can rehearse a post before saving it.
Connect Claude Code to Mynahcast in three steps
- 1In Mynahcast, open Agents & API and create a key with the Agent preset. Copy it; it is shown once.
- 2Export it as MYNAHCAST_KEY and run: claude mcp add --transport http mynahcast https://api.mynahcast.xyz/mcp --header "Authorization: Bearer $MYNAHCAST_KEY"
- 3Run /mcp inside Claude Code to check the server is connected, then ask for a post. It lands in your Approvals queue.
{
"mcpServers": {
"mynahcast": {
"url": "https://api.mynahcast.xyz/mcp",
"headers": { "Authorization": "Bearer myn_live_…" }
}
}
}Keeping an agent from posting on its own
- Use an Agent key. It can validate, draft and schedule, but the server refuses approval decisions from agents, so a person approves every post.
- An edit after approval voids the approval, so an agent can't change a post once you've said yes.
- Use dry_run while you test prompts: nothing is saved or published.
- Revoke the key from Agents & API at any time.
Which social media schedulers have an MCP server
From each vendor's public pages on 17 October 2026:
| Scheduler | MCP | Plan |
|---|---|---|
| Mynahcast | Yes (bearer key) | Every account, free in beta |
| Postiz | Yes, plus a CLI | Every paid plan (from $29/mo) |
| Buffer | Social media MCP page; Claude, ChatGPT, Cursor integrations | Listed on all plans |
| Typefully | Yes (OAuth or API key) | Including the free plan |
| Publer | Yes | Business plan |
| Hootsuite | "MCP connectors" in Wisdom AI | Paid plans |
Frequently asked questions
- Does Mynahcast work with claude.ai custom connectors?
- Not yet. Custom connectors on claude.ai need OAuth, and Mynahcast's MCP server uses a bearer API key today. Claude Desktop works through the open-source mcp-remote bridge, and Claude Code connects directly over HTTP.
- Does ChatGPT support the Mynahcast MCP server?
- ChatGPT's MCP apps accept OAuth or no authentication, so for now ChatGPT connects through a custom GPT action imported from https://api.mynahcast.xyz/v1/openapi.json with the key as a bearer token.
- What tools does the Mynahcast MCP server expose?
- Tools to validate, create, read, list, update, reschedule and delete posts, read a post's timeline, submit for approval, list channels and their limits, upload media, and read or update the brand voice. Every tool that changes something accepts dry_run.