x-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X_API_KEY | No | X/Twitter API Key (Consumer Key) | |
| X_API_SECRET | No | X/Twitter API Secret (Consumer Secret) | |
| X_ACCESS_TOKEN | No | X/Twitter Access Token | |
| X_ACCESS_TOKEN_SECRET | No | 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
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 |
|---|---|
| post_tweetB | Post a tweet to X/Twitter |
| search_tweetsB | Search recent tweets on X/Twitter (last 7 days) |
| get_user_infoB | Get profile information for one or more X/Twitter users by username |
| get_timelineB | Get the authenticated user's home timeline (reverse chronological) |
| like_tweetB | Like a tweet by its ID |
| retweetA | Retweet (repost) a tweet by its ID |
| delete_tweetA | Delete a tweet by its ID (must be owned by the authenticated user) |
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 7 tools
Each tool targets a distinct action (post, search, get user info, timeline, like, retweet, delete) with no overlap. An agent can easily distinguish them.
All tools follow a consistent verb_noun pattern in snake_case (e.g., post_tweet, search_tweets, get_user_info). No deviations or mixed conventions.
Seven tools cover the core Twitter operations without being excessive. The scope is well-balanced for a dedicated social media server.
The set covers posting, timeline, search, user info, likes, retweets, and deletion. However, fetching a specific tweet by ID is missing, which is a minor gap for workflows that need to retrieve a single tweet after a search.