Claude Code
Coding agent
One claude mcp add command with an API key, or a shared .mcp.json for a team.
Post to X from your AI agent
calmposts is an X (Twitter) MCP server for AI agents that help with social media: give your agent one address and it can draft, schedule and check your posts on X and Bluesky. By default every post waits for your yes.
Server address https://calmposts.com/mcp
How it works
Every client on this page talks to the same server, https://calmposts.com/mcp, over MCP's Streamable HTTP transport. Nothing runs on your computer: the client sends JSON-RPC calls, calmposts answers with its tools and runs them in your workspace.
There are two ways to sign in. An API key, created in calmposts under API & MCP and sent as Authorization: Bearer cp_live_…, suits coding agents, automations and anything that runs on its own. OAuth suits chat apps: the app registers itself, you sign in to calmposts and approve, and no key leaves your hands.
Whatever the client, the agent can only do what the tools allow: read your channels and limits, write drafts and threads, put them in the queue or at a time, edit, retry and delete. It cannot reply, follow, like or send DMs.
Setup guides
Claude Desktop
Chat app
A custom connector: paste the address, sign in to calmposts, approve.
Cursor
Coding agent
A few lines in ~/.cursor/mcp.json, with the key from an environment variable, or OAuth.
Codex CLI
Coding agent
codex mcp add with --bearer-token-env-var, or four lines in ~/.codex/config.toml.
Gemini CLI
Coding agent
gemini mcp add --transport http with an Authorization header, or httpUrl in settings.json.
n8n
Workflow automation
The MCP Client Tool for an AI Agent, or the MCP Client node as a step, with a Bearer Auth credential.
Manus
Autonomous agent
A custom MCP server by URL with a Bearer token, or the REST API as a Custom API.
OpenClaw
Autonomous agent
An mcp.servers entry with transport streamable-http and the key from ~/.openclaw/.env.
Which client, which setup
| Client | Kind | Sign-in | Where you set it up |
|---|---|---|---|
| Claude Code | Coding agent | API key in the Authorization header | claude mcp add, or .mcp.json in the project |
| Claude Desktop | Chat app | OAuth: you sign in to calmposts and approve, no key; API key in the Authorization header | Customize → Connectors in Claude |
| Cursor | Coding agent | API key in the Authorization header; OAuth: you sign in to calmposts and approve, no key | ~/.cursor/mcp.json or .cursor/mcp.json |
| Codex CLI | Coding agent | API key in the Authorization header | ~/.codex/config.toml, via codex mcp add |
| Gemini CLI | Coding agent | API key in the Authorization header | ~/.gemini/settings.json or .gemini/settings.json |
| n8n | Workflow automation | API key in the Authorization header | an MCP Client Tool or MCP Client node |
| Manus | Autonomous agent | API key in the Authorization header | Connectors → Create in Manus |
| OpenClaw | Autonomous agent | API key in the Authorization header | ~/.openclaw/openclaw.json, openclaw mcp set or Settings → MCP |
Which one to pick
- A coding agent, in a terminal or an editor, suits posts that come out of your work: release notes, a changelog, a thread about what you shipped. It reads the repository, writes the post and saves it as a draft or in the queue.
- A chat app suits writing with an assistant: you talk the post through, it fits it to each network, and the connector signs in with OAuth, so there is no key to copy.
- A workflow tool suits posts that follow an event: a new article in a feed, a release, a row in a sheet. Its agent or a fixed step calls the same tools on a schedule.
- An autonomous agent suits a longer task: research a topic, write a week of posts and leave them for you to approve.
Questions
Which networks can my agent post to?
Your agent can post to X and Bluesky. A thread goes out as a reply chain on X and Bluesky. Coming soon: Threads and LinkedIn.
What is an MCP server?
MCP, the Model Context Protocol, is how an AI client borrows tools from another service. calmposts' MCP server offers tools to read your channels and limits and to write, schedule, edit and retry posts; the client decides when to call them, and calmposts checks every call against your plan and each network's rules.
My client is not on the list. Can it connect?
If it speaks MCP over Streamable HTTP and can send an Authorization header, or sign in with OAuth and Dynamic Client Registration, it can: give it https://calmposts.com/mcp and an API key. A client that only starts local processes needs a bridge. Anything that speaks HTTP can use the REST API instead.
Does an agent cost extra?
No. Agents use your plan: its API keys, posts a day and posts with a link a month. The Free plan has no API keys.
Will the agent post without asking me?
Not by default: its posts wait for your approval in the app, in Telegram or by email. The workspace's owner can let agents publish directly, for the workspace and for each key.
Give your agent the address
Start the trial, connect your accounts, create a key and add calmposts to the client you already use.
Try it free