Last updated: August 31, 2026
Post to X from Kilo Code
Add the hosted OpenTweet MCP server at mcp.opentweet.io/mcp and Kilo Code can publish, schedule, and thread on X from the editor. One URL, one bearer key, 36 tools. No X developer account and no OAuth code to write.
If you landed here mid-migration off Roo Code, which announced shutdown on April 21, 2026 and archived on May 15, 2026, this is the one server on your list that pays for itself the next time you ship something.
7-day free trial. No X developer account needed.
Coming from Roo Code
Kilo Code went generally available on April 2, 2026, is rebuilt on the OpenCode server, and is the official destination for Roo Code users. Your .roorules become AGENTS.md, and your MCP configuration carries over rather than being rewritten.
The part nobody warns you about is the inventory. Config carries over, but the reasoning behind it does not, and a server list you built over six months takes an afternoon to reconstruct from memory. The posting tool is the one that goes missing quietly: nothing errors, you just stop announcing releases.
Rebuild the list in the marketplace, then add the hosted ones by URL
The Kilo Code MCP Server Marketplace covers the packaged servers. Anything hosted, OpenTweet included, is faster to add by pasting a URL and an Authorization header. Thirty seconds, no npm install, nothing to keep updated.What Kilo Code can do on X
One server, the whole surface. No tool wrappers.
Post now
opentweet_create_tweet publishes straight from the editor.
Schedule
opentweet_schedule_tweet and opentweet_batch_schedule fill the queue.
Threads
opentweet_create_thread turns a long explanation into a connected thread.
36 tools
Posts, threads, articles, evergreen, media, analytics. One server.
Analytics
The agent can read results and adjust what it writes next.
No X API
No developer account, no OAuth code, no per-post billing.
Setup
Connect your X account to OpenTweet, copy the ot_ key, then add the server from the MCP Servers panel or paste the entry into your project MCP config.
Hosted server, recommended
{
"mcpServers": {
"opentweet": {
"type": "streamable-http",
"url": "https://mcp.opentweet.io/mcp",
"headers": {
"Authorization": "Bearer ot_your_key"
}
}
}
}Local stdio
{
"mcpServers": {
"opentweet": {
"command": "npx",
"args": ["-y", "@opentweet/mcp-server"],
"env": {
"OPENTWEET_API_KEY": "ot_your_key"
}
}
}
}Both give the agent the same tools. Names and arguments are in the MCP docs. If you are also running Kilo Code alongside another editor, the same config works in Cline and Cursor.
The REST fallback
For anything outside an editor session, a script, a hook, or CI, skip MCP and use the key directly.
curl -X POST https://opentweet.io/api/v1/posts \
-H "Authorization: Bearer ot_your_key" \
-H "Content-Type: application/json" \
-d '{"text":"Migrated the whole extension config in an afternoon.","publish_now":true}'
# Schedule instead of posting now:
# {"text":"...","scheduled_date":"2026-09-02T09:00:00Z"}The route is /api/v1/posts. Everything it accepts is in the API docs.
Good fits
Roo Code migrants rebuilding a server list
Add the posting tool once and stop losing announcements to a config migration.
Extension-heavy VS Code setups
OpenTweet sits next to your other MCP servers and needs no local process if you use the hosted URL.
Teams with several X accounts
Every posting tool takes an x_account_id, so one key can drive a product account and a personal one.
Release-note automation
The agent reads the diff, writes the note, and schedules it for a time people are awake.
Also available in OpenCode, goose, and Claude Code.
Frequently asked questions
How do I add an MCP server to Kilo Code?
Open the MCP Servers panel and add a remote server, or write the entry into your project mcp config. For OpenTweet, point at https://mcp.opentweet.io/mcp with an Authorization header carrying your ot_ key. The 36 posting, scheduling, thread, article, and analytics tools appear to the agent immediately.
What happened to Roo Code?
Roo Code announced its shutdown on April 21, 2026 and archived the repository on May 15, 2026. Kilo Code, which went generally available on April 2, 2026 and is rebuilt on the OpenCode server, is the migration target. Your .roorules become AGENTS.md and your MCP configuration carries over.
Does my Roo Code MCP config carry over to Kilo Code?
The MCP configuration carries over, which is the whole point of the migration path. What usually does not survive is the memory of which servers you had and why. If you are rebuilding the list by hand, the posting server is the one people forget until the next release goes out unannounced.
What is the Kilo Code MCP Server Marketplace?
A browsable catalogue inside the extension for installing MCP servers without hand-editing JSON. It is the fastest way to rebuild a server list after a migration. For a hosted server like OpenTweet you can also paste the URL and header directly, which takes about thirty seconds.
Do I need an X developer account?
No. OpenTweet holds the X connection, OAuth, and token refresh. Kilo Code authenticates to OpenTweet with a single ot_ bearer key. You never create an X developer app and you never pay X pay-per-use rates.
Can the agent schedule posts rather than publishing immediately?
Yes. opentweet_schedule_tweet queues a single post and opentweet_batch_schedule queues many. The queue lives on OpenTweet servers, so it fires whether or not your editor is open. Scheduling is something the X API does not offer at any price.
What does it cost?
Pro is $11.99/month with the API included, and there is a 7-day free trial. The X API charges $0.015 per post and $0.20 per post containing a link, so a flat plan wins past roughly 60 link posts a month.
Wire any agent to X
One hosted MCP server, every client that speaks the protocol.
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.
Add the posting server once, keep it forever
Hosted URL, one bearer key. It survives your next editor migration too.
$11.99/month, API included. Cancel anytime.