Hosted remote HTTP MCP

Twitter API MCP Server for AI Agents

Give Codex and Claude Code direct access to current TweetAPI documentation and bounded, read-only Twitter data tools. Connect once through the dashboard, then work from your agent chat.

Start free Connect MCP

New accounts include 100 free requests. No credit card required.

TweetAPI hosted MCP

OAuth-protected remote server

Server URL

https://mcp.tweetapi.com/mcp

Current TweetAPI docs inside your agent
Read-only public Twitter data tools
Dashboard authorization with a selected API key

Verified setup

Connect Codex or Claude Code

Run each command separately. Adding the server saves its configuration. The login command opens TweetAPI in your browser so you can approve access.

Codex

1. Add server

codex mcp add tweetapi --url https://mcp.tweetapi.com/mcp

2. Log in

codex mcp login tweetapi

Claude Code

1. Add server

claude mcp add --transport http --scope user tweetapi https://mcp.tweetapi.com/mcp

2. Log in

claude mcp login tweetapi

Dashboard authorization

You control which API key the agent uses

TweetAPI uses OAuth for the MCP connection. Your agent client receives access and refresh tokens after approval, while the selected TweetAPI API key remains behind the dashboard boundary.

Read the Agents and MCP guide

1
Add the hosted server
Save the remote HTTP MCP URL in your agent client.
2
Run the login command
Your browser opens the TweetAPI dashboard authorization screen.
3
Choose an API key
Select the TweetAPI key that should back this MCP connection.
4
Approve read-only access
The client receives OAuth tokens without exposing your API key to the chat.

Requirements and boundaries

Useful agent access without widening the trust boundary

Read-only live tools

Hosted MCP can search TweetAPI docs and call supported public-data tools. It does not expose posting, engagement, account-secret, or DM operations.

Normal TweetAPI quota

Each live MCP call is forwarded to TweetAPI and consumes the normal quota of the API key selected during authorization.

Secrets stay out of prompts

Authorize through the dashboard. Do not paste API keys, X account tokens, proxy credentials, or private message content into agent prompts.

Account and key required

You need a TweetAPI account, an active API key, and an agent client that supports remote HTTP MCP with OAuth.

Choose the right integration

MCP for agent work, REST or SDKs for your application

Use hosted MCP when

Your agent needs current TweetAPI docs, exact endpoint parameters, or a bounded read-only public-data lookup during a chat.

Open MCP setup docs

Use REST or an SDK when

You are building TweetAPI into an application, background job, data pipeline, or server. Keep the API key in server-side environment variables.

Browse API docs Compare TweetAPI SDKs Review pricing

Ready to connect TweetAPI MCP?

Start with 100 free requests or connect an existing dashboard API key.