twitter-mcp
Twitter/X MCP server for the API v2, enabling users to manage profiles, posts, likes, retweets, and follows through natural language using a stateless Streamable HTTP transport with OAuth user access token authentication.
README
Twitter MCP Server
TypeScript Model Context Protocol server for the Twitter/X API v2.
- Transport: Streamable HTTP (stateless)
- Auth: OAuth user access token via the
access-tokenheader — required only for tool calls, not for list/initialize - Runtime: Node.js 20+, Express,
@modelcontextprotocol/sdk - Docker: multi-stage production image included
This server does not run the OAuth dance itself. Obtain a user access token from your OAuth 2.0 (or OAuth 1.0a user-context) flow and send it when invoking tools.
Endpoints
| Method | Path | Description |
|---|---|---|
POST |
/mcp |
MCP Streamable HTTP endpoint (tools) |
GET |
/health |
Liveness probe |
GET |
/mcp |
405 — not used in stateless mode |
DELETE |
/mcp |
405 — no sessions to delete |
Authentication
access-token is not required for protocol/list methods (initialize, tools/list, ping, etc.). It is required when calling a tool that hits the Twitter API.
POST /mcp HTTP/1.1
Host: localhost:3000
Content-Type: application/json
Accept: application/json, text/event-stream
access-token: <OAUTH_USER_ACCESS_TOKEN>
Fallback (also accepted):
Authorization: Bearer <OAUTH_USER_ACCESS_TOKEN>
If a tool is called without a token, the tool returns an error:
Missing access token. Tool calls require an OAuth user access token via the `access-token` header …
Suggested OAuth 2.0 scopes for full tool coverage:
tweet.read tweet.write users.read follows.read follows.write media.write offline.access
Media / video posting requires
media.writein addition totweet.write. Re-authorize users after adding the scope so tokens include it.
Tools
| Tool | Description |
|---|---|
get_me |
Authenticated user profile |
get_user_by_username |
User lookup by handle |
get_user_by_id |
User lookup by ID |
get_tweet |
Single tweet by ID |
get_user_timeline |
User's recent posts |
get_user_mentions |
Mentions timeline |
search_recent_tweets |
Recent search (last 7 days) |
upload_media |
Upload image / GIF / video (returns media_id) |
post_tweet |
Create a post (optional reply / quote / media) |
delete_tweet |
Delete own post |
like_tweet / unlike_tweet |
Like management |
retweet / undo_retweet |
Retweet management |
follow_user / unfollow_user |
Follow management |
Posting video
- Call
upload_mediawith one of:media_url— HTTP(S) URL (preferred for large files)media_path— path on the server hostmedia_base64— base64 payload (JSON body limit 64 MB; prefer URL for big videos)
- Optionally set
media_typetovideo/mp4orvideo/quicktimeif it cannot be inferred. - Wait for the tool to return
{ "media_id": "..." }(videos are processed server-side before return). - Call
post_tweetwithmedia_ids: ["<media_id>"]and optionaltext.
Limits: 1 video or 1 GIF, or up to 4 images per post. Max file size loaded in-process: 512 MB.
Local development
npm install
npm run dev
# → http://0.0.0.0:3000/mcp
Build & run production:
npm run build
npm start
Environment variables:
| Variable | Default | Description |
|---|---|---|
PORT |
3000 |
HTTP port |
HOST |
0.0.0.0 |
Bind address |
Docker
# Build
docker build -t twitter-mcp .
# Run
docker run --rm -p 3000:3000 twitter-mcp
# Health check
curl http://localhost:3000/health
Example MCP initialize (curl)
No token needed for initialize / tools/list:
curl -sS http://localhost:3000/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-03-26",
"capabilities": {},
"clientInfo": { "name": "curl", "version": "1.0.0" }
}
}'
Tool calls need the token:
curl -sS http://localhost:3000/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H 'access-token: YOUR_TOKEN' \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": { "name": "get_me", "arguments": {} }
}'
Architecture notes
- Stateless Streamable HTTP — each
POST /mcpcreates a newMcpServer+StreamableHTTPServerTransportwithsessionIdGenerator: undefined, then tears them down when the response finishes. Safe for horizontal scaling and containers. - Per-request token isolation —
AsyncLocalStorageholds the optional access token for the duration of the request so concurrent calls never mix credentials. Missing tokens only fail when tools callgetAccessToken(). - Twitter client —
twitter-api-v2is constructed with the user access token and used as OAuth 2.0 user-context (Bearer).
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。