Post to X from Claude Desktop

What Claude Desktop can do with calmposts

Claude Desktop is where you think out loud: paste notes, a link or a rough draft, ask for a post or a thread, and keep refining it in the chat. With calmposts connected, Claude sees which accounts you have and how long each network lets a post be, and saves the result as a draft, in the queue or at the time you name.

The connector lives in your Claude account, not on this computer, so the same calmposts connection works in Claude on the web and in the mobile apps too. Claude reaches calmposts from Anthropic's servers; calmposts is on the public internet, so nothing needs opening on your side.

calmposts' X (Twitter) MCP server gives Claude Desktop 11 tools, the same set every client gets:

Set up calmposts in Claude Desktop

Check the key before you start

Create a key in calmposts under API & MCP (it's shown only once), then ask the server for its tools. A list of 11 tools means the address and the key are right; a 401 means the key is wrong or was sent without “Bearer ”.

curl -s https://calmposts.com/mcp \
  -H "Authorization: Bearer cp_live_…" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# 200 {"jsonrpc":"2.0","id":1,"result":{"tools":[…]}}

Setup 1: A custom connector with OAuth, no key

Claude registers itself with calmposts, and you approve it once.

1. In Claude Desktop, open Customize → Connectors, click + Add, then Add custom connector.

2. Name the connector and paste the server's address:

   Name:  calmposts
   URL:   https://calmposts.com/mcp

3. Keep the sign-in Claude detects, calmposts' OAuth. Where the dialog asks, choose:

   Authentication:  Sign in now
   OAuth client:    Register automatically

4. Click Add and sign in when Claude asks: calmposts opens, you sign in as the workspace's owner and click Allow.

5. In a chat, open + → Connectors and switch calmposts on for that conversation.

Setup 2: A fixed key in a request header (beta)

Where your organization has Claude's request headers, the connector can send a calmposts key instead of signing in. Claude marks the feature beta and offers it to some organizations only.

1. Create an API key in calmposts under API & MCP.

2. Add the custom connector with the same address, and choose:

   Authentication:   No sign-in
   Request headers:  authorization = Bearer cp_live_…

3. Click Add. Claude stores the value, never shows it again and sends it with every request.

Signing in: a key or OAuth

With OAuth, Claude registers itself with calmposts (Dynamic Client Registration), sends you to calmposts' consent page and exchanges the code with PKCE. Only the workspace's owner can approve, and only on a plan with agents.

The connection then holds a one-hour access token and a 30-day refresh token that is replaced each time it is used, so you sign in once. It is listed in calmposts under API & MCP → Connected apps; disconnecting it there ends Claude's access at once.

A connector follows the workspace's approval setting: its posts wait for approval unless the workspace lets agents publish. A key in a request header also follows that key's own setting.

On Team and Enterprise plans an Owner adds calmposts under Organization settings → Connectors (Add → Custom → Web), and each member then connects with their own calmposts account. A key in a request header there is shared by everyone who uses the connector: give it only the permissions they all should have.

Check that it works

• Customize → Connectors shows calmposts as connected.
• In calmposts, API & MCP → Connected apps lists Claude with the day you connected it.
• Ask “Which accounts do I have in calmposts?”: Claude asks to use list_accounts and answers with your channels.
• Ask for a draft and find it under Posts in calmposts, with the source mcp.

Prompts to try

Ask in your own words and the agent picks the tools. A few that work well:

• “Here are my notes from today's talk. Turn them into an X thread and a Bluesky post, and save both in calmposts as drafts.”
• “Rewrite this announcement so it fits one X post without the link, and schedule it for tomorrow at 9 a.m. my time.”
• “What is in my calmposts queue this week? Is anything there twice?”
• “Make a Bluesky version of my last scheduled post and put it in the queue.”
• “Which of last week's posts did best? Write two more in that style as drafts.” (plans with analytics)

Networks, threads and approval

Posts go to X and Bluesky. A thread goes out as a reply chain on X and Bluesky. Coming soon: Threads and LinkedIn.

Write once, post everywhere: your agent sends one text for every account it picks. If the text is longer than a network allows, calmposts posts it there as a thread, splitting at a paragraph break, then at the end of a sentence, then at a space, with nothing numbered or added. calmposts checks each network's rules and your plan's limits before it saves the post and names the field that's wrong, so the agent can fix the text and try again.

By default your agent's posts wait for you. They come back as pending_approval, and you approve or reject each one in the app, in Telegram or from the email calmposts sends. The workspace owner can let agents publish on their own, but only when both the workspace and the API key are set to publish. X expects an account that posts automatically to carry its Automated label (Settings → Your account → Account information → Automation).

Which networks work today→

Limits and costs

• Agents need a paid plan: the Free plan has no API keys and can't approve connected apps. API keys per plan: Pro 3 · Advanced 10 · Agency 25.
• Your agent's posts count the same as yours. Posts a day: Pro 20 · Advanced 100 · Agency 300. Posts with a link per month: Pro 30 · Advanced 300 · Agency 600. Each post in a thread counts.
• Posts with a link are counted separately because X charges every app $0.015 per post and $0.20 per post with a link. Your plan includes X's fees, so you don't need an X developer account or an X API bill of your own.
• Try it first: 7-day free trial. Card required. 5 posts with a link during the trial.
• Each key can make 60 requests a minute across MCP and REST; beyond that, the server returns 429 with Retry-After.

Pricing→

What to know about Claude Desktop

• Custom connectors are on every Claude plan; the Free plan allows one.
• A connector's sign-in cannot be changed later: to move from OAuth to a header, or back, remove calmposts and add it again.
• Claude Desktop does not read remote servers from claude_desktop_config.json; that file starts local programs. Add calmposts under Connectors.
• Claude's published identity needs a Client ID Metadata Document, which calmposts does not offer; Claude then registers automatically, as Claude's docs describe.
• Under Customize → Connectors you can set a tool, delete_post for example, to Blocked. Choose Allow always only for tools you are happy to see run unsupervised.

Without MCP: the REST API

Everything the tools do is also a REST call under /api/v1 with the same key, which suits a script or a workflow step that only speaks HTTP. calmposts posts through its own approved X app, so you don't need X API keys of your own.

export CALMPOSTS_API_KEY=cp_live_…
curl -H "Authorization: Bearer $CALMPOSTS_API_KEY" https://calmposts.com/api/v1/accounts
curl -X POST https://calmposts.com/api/v1/posts \
  -H "Authorization: Bearer $CALMPOSTS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"parts":[{"text":"Calm posts, scheduled."}],"targets":[{"account_id":"ACCOUNT_ID"}],"schedule":{"mode":"queue"}}'

REST API docs→

The Claude Desktop docs this page follows

• Claude Help Center: Get started with custom connectors using remote MCP
• Claude docs: Add a connector that isn't in the directory
• Claude docs: Authentication for connectors

calmposts is an independent service and is not affiliated with or endorsed by the makers of Claude Desktop. Product names belong to their owners.