X(Twitter) MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TWITTER_API_KEY | Yes | Your X/Twitter API key | |
| TWITTER_API_SECRET | Yes | Your X/Twitter API secret | |
| TWITTER_ACCESS_TOKEN | Yes | Your X/Twitter access token | |
| TWITTER_ACCESS_TOKEN_SECRET | Yes | Your X/Twitter access token secret |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_draft_tweetC | Create a draft tweet |
| create_draft_threadC | Create a draft tweet thread |
| list_draftsB | List all draft tweets and threads |
| publish_draftC | Publish a draft tweet or thread |
| delete_draftC | Delete a draft tweet or thread |
| create_draft_replyC | Create a draft reply to an existing tweet |
| reply_to_tweetA | Reply to an existing tweet directly (without creating a draft) |
| retweetA | Retweet an existing tweet (simple retweet without comment) |
| quote_tweetB | Quote tweet with comment (retweet with your own comment) |
| create_draft_quote_tweetC | Create a draft quote tweet with comment |
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 10 tools
The tools have clear distinctions between draft creation (create_draft_tweet, create_draft_reply, create_draft_thread, create_draft_quote_tweet) and direct actions (reply_to_tweet, quote_tweet, retweet), but there is some overlap: create_draft_reply and reply_to_tweet both handle replies, differing only in draft vs. direct, which could cause confusion. Similarly, create_draft_quote_tweet and quote_tweet serve similar purposes with a draft distinction.
All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., create_draft_tweet, delete_draft, list_drafts). The naming is predictable and uniform across all tools, making it easy for agents to understand and use them without confusion.
With 10 tools, this server is well-scoped for managing tweets and drafts on X (Twitter). The count is appropriate, covering creation, deletion, listing, and publishing of drafts, as well as direct tweet actions, without being overly complex or too sparse for the domain.
The tool set provides good coverage for tweet and draft management, including CRUD-like operations (create, list, delete, publish) and direct interactions (reply, quote, retweet). A minor gap exists in updating drafts (e.g., edit_draft), but agents can work around this by deleting and recreating drafts, and the core workflows are well-supported.