twitterapi.mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TWITTERAPI_IO_CT0 | No | ct0 cookie from the same session (required for write actions) | |
| TWITTERAPI_IO_KEY | No | twitterapi.io API key (required for all tools) | |
| TWITTERAPI_IO_PROXY | No | Residential proxy, http://user:pass@ip:port (required for write actions) | |
| TWITTERAPI_IO_AUTH_TOKEN | No | auth_token cookie from a logged-in X session (required for write actions) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_mentionsA | Fetch tweets mentioning a specific X/Twitter user. Makes a single request per call. The caller handles pagination by passing |
| get_tweet_thread_contextA | Fetch one page of the conversation thread around a tweet (to find links in context). Returns the original tweet, intermediate replies up the chain, the tweet itself, and its direct replies; each tweet includes |
| create_tweetA | Create or reply to a tweet via the v2 endpoint. Uses |
| delete_tweetA | Delete a tweet by ID (must be owned by the logged-in account). Uses |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: fetching mentions, retrieving thread context, creating tweets, and deleting tweets. No overlap in purpose.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_user_mentions, create_tweet), making them predictable.
4 tools is slightly minimal for a Twitter API server but reasonable for a focused subset. Each tool serves a clear purpose without redundancy.
The tool set covers core CRUD for tweets (create, delete) and some read operations (mentions, thread context), but lacks common features like timeline retrieval, search, or interactions (like, retweet).