Last updated: August 31, 2026

Post to X from Manus

Manus takes custom MCP servers under Settings, Integrations, Custom MCP Servers. Add one pointing at https://mcp.opentweet.io/mcp and the agent gets 36 X tools: publish, schedule, thread, article. No X developer account, flat $11.99 a month.

Manus is good at finishing a long task on its own. What it is missing on X is a durable place to put the result. A browser run ends with the task. A scheduled post does not.

7-day free trial. No X developer account needed.

What Manus can do on X

All 36 tools arrive at once. You do not write a tool wrapper for any of them.

Post now

opentweet_create_tweet publishes the moment the agent decides to.

Schedule

The queue lives on our servers, so it outlives the Manus session.

Threads

opentweet_create_thread ships a connected thread in one call.

36 tools

Posts, threads, articles, evergreen, media and analytics, no wrappers to write.

Structured results

Post ids and URLs come back as data the next step can use.

No X API

No developer account, no OAuth to build, no per-post billing.

Setup, about two minutes

Connect your X account to OpenTweet, copy the ot_ key from the dashboard, then add the server in Manus. The form asks for a name, an HTTPS URL and credentials, then tests the connection by pulling the tool list.

Manus, add custom MCP server

Settings  ->  Integrations  ->  Custom MCP Servers  ->  Add Server

Name:           OpenTweet
Server URL:     https://mcp.opentweet.io/mcp
Authorization:  Bearer ot_your_key

Then press Test. Manus retrieves the tool list and 36
OpenTweet tools become available in your prompts.

If you prefer to keep the same server definition alongside your other clients, this is the standard JSON form of the identical endpoint. Claude Desktop, Cursor and Windsurf all take this shape verbatim.

mcp.json

{
  "mcpServers": {
    "opentweet": {
      "type": "http",
      "url": "https://mcp.opentweet.io/mcp",
      "headers": {
        "Authorization": "Bearer ot_your_key"
      }
    }
  }
}

Every tool and argument is listed in the MCP docs.

The sandbox constraint, and why it favours a hosted server

Manus runs your task in its own cloud environment. The Manus documentation is explicit that a custom server has to be hosted on infrastructure you control and reachable over HTTPS, and it asks servers to answer most operations within a few seconds, with longer work moved to an asynchronous pattern.

What that rules in and out

A server on localhost is not reachable from the Manus environment, so a stdio or local-port MCP server is off the table unless you tunnel it. The hosted OpenTweet endpoint is already public HTTPS and already fast to answer, because a schedule call writes a row and returns rather than waiting on X.

This is the same reason scheduling belongs on the server rather than in the agent. opentweet_schedule_tweet returns immediately with a post id, the publish happens later on our infrastructure, and the Manus task is free to close.

The REST fallback

For anything outside an agent turn, a webhook handler, a cron job, a build step, skip MCP. Same key, one endpoint.

post.sh

curl -X POST https://opentweet.io/api/v1/posts \
  -H "Authorization: Bearer ot_your_key" \
  -H "Content-Type: application/json" \
  -d '{"text":"Finished the migration. Notes in the thread.","publish_now":true}'

# Schedule instead of publishing now:
#   {"text":"...","scheduled_date":"2026-09-02T09:00:00Z"}

The route is /api/v1/posts. Full field reference in the API docs, and the GitHub Actions guide shows the CI shape.

What people ask Manus to do with it

Research, then queue the week

Manus does what it is best at, a long research pass, and ends the task by calling opentweet_batch_schedule once with seven posts and seven times.

Turn a finished deliverable into a thread

The report Manus just wrote becomes opentweet_create_thread, in one call, without you copying anything into a composer.

Long-form on X

opentweet_create_article publishes an X Article straight from the markdown Manus produced.

Check what landed, then adapt

opentweet_get_analytics and opentweet_get_top_posts let the next task start from what actually worked rather than a guess.

The same endpoint works in Claude Desktop, Cursor, Windsurf, and ChatGPT.

Frequently asked questions

Does Manus support custom MCP servers?

Yes. The Manus documentation has a Custom MCP Servers page under Integrations. You host a server reachable over HTTPS, go to Settings, Integrations, Custom MCP Servers, click Add Server, give it a name, the HTTPS URL and its credentials, and Manus tests the connection by retrieving the tool list. The tools are then available in ordinary prompts.

How do I add OpenTweet to Manus?

Add a custom MCP server with the URL https://mcp.opentweet.io/mcp and an Authorization value of Bearer ot_your_key, using your OpenTweet API key from the dashboard. Manus reads the catalogue and 36 tools appear, including opentweet_create_tweet, opentweet_schedule_tweet and opentweet_create_thread.

Do I need an X developer account?

No. OpenTweet holds the X connection, the OAuth flow and the token refresh. Manus authenticates to OpenTweet with a single ot_ bearer key. You never create an X developer app and you never touch the pay-per-use X API.

Why use a tool instead of letting Manus post through a browser?

Because a browser run ends when the task ends. Anything you want to happen next Tuesday at 09:00 has to survive the session, and a scheduled post on OpenTweet does. A tool call also gives you a post id and a URL back as structured data instead of a screenshot, which the next step of the agent can actually use.

Can Manus reach an MCP server running on my laptop?

No. Manus runs your task in its own cloud environment, and the Manus docs require the server to be reachable over HTTPS. A localhost address is not routable from there. The hosted OpenTweet endpoint sidesteps this entirely because it is already public and already on HTTPS.

What does this cost against calling the X API from Manus directly?

OpenTweet is $11.99 a month on Pro with the API included and a 7-day free trial. The X API bills pay-per-use: $0.015 per post and $0.20 per post that contains a link. If your agent posts links, the flat fee wins past roughly 60 link posts a month.

Can Manus schedule a whole week of posts in one turn?

Yes. opentweet_batch_schedule takes many posts and their times in one call, so a single Manus task can fill a week of queue and then finish. The queue keeps running after the task is closed because it lives on OpenTweet servers, not in the sandbox.

Wire any agent to X

Manus is one client of many. The same hosted MCP server works everywhere.

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 Manus an X account it can actually use

Connect X, copy your key, add one custom MCP server.

$11.99/month, API included. Cancel anytime.