Last updated: August 2026
Can the official X MCP server schedule posts?
No. The official X MCP server at api.x.com/mcp can post, it just cannot schedule. Every call fires immediately, bills X pay-per-use including $0.20 for a post with a link, and needs your own X developer app. Scheduling means adding a scheduler on top, or using an MCP server that already has one.
One correction first, because a lot of pages get it wrong: the official X MCP server is not read-only. It publishes. The missing capability is timing, not writing.
It posts. It does not schedule.
X launched its official MCP server at api.x.com/mcp on 30 June 2026. Connect it to an MCP client and the model gets tools that read from X and tools that publish to X. If you ask your agent to post something, it posts.
What is not in the tool list is a time. There is no post-at parameter, no queue to inspect, no pending item to edit or cancel. The moment the model decides to call the publish tool, the post is live on your account. For an agent that drafts and posts in the same breath, that is fine. For anything that runs on a timetable, it is the whole problem.
No queue also means no undo
A scheduler gives you a window between deciding and publishing. With immediate-only posting there is no such window, so a model that misreads an instruction has already published by the time you see it. If an autonomous agent is drafting the text, that gap is worth having.Official X MCP vs the OpenTweet MCP
The last row matters. If your agent needs full-archive search or first-party read access, the official server is the right tool and nothing here replaces it. The cost comparison in full is at is the official X MCP server free, and the head to head is at OpenTweet vs XMCP.
Two ways to get scheduling anyway
1. Build the scheduler yourself
Store the text and the target time somewhere durable, run a process that wakes up every minute, and have it call the MCP publish tool when a row comes due. This works, and it is more work than it sounds: you own retries, you own the case where the process was down at the target minute, you own duplicate suppression when a retry fires after a call that actually succeeded, and you own the timezone handling.
You also still pay per post, including the $0.20 link surcharge, so the scheduler you built does not change the bill.
2. Connect an MCP server that already schedules
The OpenTweet MCP server exposes scheduling as a tool, so the model passes a time and the queue is somebody else's problem. It is a hosted Streamable HTTP endpoint, so there is nothing to install and no process of yours to keep alive.
{
"mcpServers": {
"opentweet": {
"type": "streamable-http",
"url": "https://mcp.opentweet.io/mcp",
"headers": { "Authorization": "Bearer ot_your_key" }
}
}
}After that, the agent can say a time out loud: schedule this for Tuesday at 9am, queue these five for the week, move the one at noon to 4pm. Setup for each client is in the MCP docs, and the full tool list is on the Twitter MCP server page.
You can run both
Nothing stops you connecting the official X MCP server for reads and the OpenTweet MCP server for writes and scheduling. The model sees both tool sets and picks per task. You pay X only for the reads you actually make, and none of the write surcharges.7-day free trial. Cancel anytime.
Frequently asked questions
Can the official X MCP server schedule posts?
No. The official X MCP server, launched at api.x.com/mcp on 30 June 2026, can publish to X but has no scheduling primitive. Every post it makes goes out at the moment the tool is called. There is no post-at-time parameter, no queue, and no way to cancel a post before it goes live.
Can the official X MCP server post at all?
Yes. This gets misreported constantly. The official X MCP server is not read-only: it can publish posts to your account. What it cannot do is schedule them for later. Any page telling you it only reads is wrong.
What does the official X MCP server cost?
The server has no subscription fee, but every action it takes bills X pay-per-use against your own developer project: about $0.005 per post read, about $0.015 per post published, and about $0.20 per post that contains a link. You also fund a prepaid balance, so there is no configuration in which posting through it is free.
How do I schedule posts through an MCP client then?
Two options. Run your own cron that stores the text and calls the MCP tool at the right minute, which means keeping a process alive and handling retries yourself. Or connect an MCP server that has scheduling built in. OpenTweet exposes schedule and batch schedule tools at https://mcp.opentweet.io/mcp, so the agent just names a time.
Do I need an X developer account for the official X MCP server?
Yes. You create your own X app, attach it to a project, enrol the project in billing, and complete OAuth before the server can post. If the project is not enrolled, writes come back as a 403. OpenTweet does not require a developer account because it holds the X connection for you.
When is the official X MCP server the better choice?
When you need first-party read access: full-archive search, richer post metadata, or anything where being an official X client matters. It is the wrong tool when your workload is publishing on a timetable, because you pay metered write prices and still have to build the scheduler yourself.
Keep exploring
Scheduling, threads, and analytics as MCP tools, on a flat monthly fee.
OpenTweet vs the X API
Post, schedule, and automate X without a developer account or the $200/mo minimum.
X DM outreach, human-approved
Find and qualify leads, AI-draft DMs, approve each one, and drip-send from your own account via API or MCP.
Post to X without an API
The clean, account-safe way to post to X from your code or an AI agent.
Twitter MCP Server
Give Claude, Cursor, and OpenClaw the ability to post to X. 36 tools included.
Developer docs
Quickstart, API keys, MCP setup, and the REST reference for posting to X from code or an agent.
XMCP vs OpenTweet
X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.
MCP for AI agents
Connect your AI client to X in under two minutes, no X developer account.
Developer API and keys
REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.
OpenTweet for AI agents
The posting layer for autonomous agents and automations that live on X.
Build an AI Twitter persona
Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.
Best MCP servers for social media
The 2026 ranked list. How the hosted OpenTweet MCP compares with the official X MCP and others.
Cheapest way to post to X via code
Flat fee vs pay-per-use. Why the $0.20 per-link fee flips the math past ~60 posts a month.
Give your agent a schedule tool
Paste one URL into your MCP client and your agent can queue posts for any time. Flat $11.99 a month, no developer app.
7-day free trial. Cancel anytime.