How to Give Any MCP Agent
a Twitter Tool

Sign up for OpenTweet (free 7-day trial on all plans) and open the developer page to generate an API key. Every key starts with the ot_ prefix and is scoped to your account, so the agent posts on your behalf. You can revoke or rotate it anytime.

Grab a key at opentweet.io/developer, then verify it works with a quick call to GET /me.

curl https://opentweet.io/api/v1/me \
  -H "Authorization: Bearer ot_your_key"

The fastest path is the hosted MCP server. There is nothing to install. Add the endpoint to your MCP client config with the streamable-http transport and an Authorization Bearer header carrying your ot_ key. This is the recommended setup for most agents.

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

Prefer to run the server yourself? Point your client at the npx command instead. It downloads and starts the same server on your machine, reading your key from the OPENTWEET_API_KEY environment variable. Use this when your client only supports stdio-based local servers.

{
  "mcpServers": {
    "opentweet": {
      "command": "npx",
      "args": ["-y", "@opentweet/mcp-server"],
      "env": {
        "OPENTWEET_API_KEY": "ot_your_key"
      }
    }
  }
}

Restart your MCP client so it loads the new server. Your agent should now list 36 OpenTweet tools. If you do not see them, double check the endpoint URL, that the header uses your real ot_ key, and that the client fully reloaded.

The tool set spans posting, scheduling, media, analytics, evergreen, and articles. A few you will use most:

opentweet_create_tweet
opentweet_create_thread
opentweet_schedule_tweet
opentweet_batch_schedule
opentweet_get_analytics
opentweet_add_to_evergreen

That is it. Talk to your agent the way you already do. Ask it to post now, schedule for a specific time, or plan a whole week. The agent maps your request to the right tool, so you never write JSON by hand.

You: post "Shipped the new MCP integration today. Agents can now tweet."

You: schedule a tweet about the launch for 2026-07-10 at 9am

You: draft a 3-tweet thread explaining how the auth flow works

Under the hood the agent calls the REST API for you. A publish-now request is POST /posts with { "text": "...", "publish_now": true }, and scheduling swaps in scheduled_date (ISO 8601). You never touch it directly.