x-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X_API_KEY | Yes | The Consumer Key (API Key) from the X Developer Portal. | |
| X_API_SECRET | Yes | The Secret Key (API Secret) from the X Developer Portal. | |
| X_ACCESS_TOKEN | Yes | The Access Token generated from the X Developer Portal (requires Read/Write permissions for posting). | |
| X_BEARER_TOKEN | Yes | The Bearer Token from the X Developer Portal. | |
| X_ACCESS_TOKEN_SECRET | Yes | The Access Token Secret generated from the X Developer Portal (requires Read/Write permissions for posting). |
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_tweetC | Create a new post on X (Twitter). Supports text, polls, and media attachments. |
| reply_to_tweetC | Reply to an existing post on X. Provide the tweet ID or URL to reply to. |
| quote_tweetB | Quote retweet a post on X. Adds your commentary above the quoted post. |
| delete_tweetC | Delete a post on X by its ID. |
| get_tweetA | Fetch a tweet and its metadata by ID or URL. Returns author info, metrics, and referenced tweets. |
| search_tweetsA | Search recent tweets by query. Supports keywords, hashtags, from:user, to:user, is:reply, has:media, etc. Uses the recent search endpoint (last 7 days). |
| get_userC | Look up a user profile by username or user ID. Returns bio, metrics, verification status, etc. |
| get_timelineA | Fetch a user's recent posts. Requires the user's numeric ID (use get_user first to resolve username to ID). |
| get_mentionsC | Fetch recent mentions of the authenticated user. |
| get_followersC | List followers of a user by their numeric user ID. |
| get_followingC | List who a user follows by their numeric user ID. |
| like_tweetC | Like a post on X. |
| retweetC | Retweet a post on X. |
| upload_mediaB | Upload an image or video to X. Returns a media_id that can be attached to posts. Provide the file as base64-encoded data. |
| get_metricsA | Get engagement metrics for a specific post (impressions, likes, retweets, replies, quotes, bookmarks). Requires the tweet to be authored by the authenticated user for non-public metrics. |
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 15 tools
Every tool has a clearly distinct purpose with no ambiguity; for example, get_tweet retrieves a single tweet, get_timeline fetches a user's recent posts, and search_tweets searches across tweets, all serving different functions. Actions like like_tweet, retweet, quote_tweet, and reply_to_tweet are well-separated in their specific interactions with posts, ensuring agents can easily select the correct tool.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_user, post_tweet, and delete_tweet, with no deviations in style or convention. This predictability makes the tool set easy to navigate and understand at a glance, enhancing usability for agents.
With 15 tools, the server is well-scoped for interacting with X (Twitter), covering core functionalities like posting, retrieving, and engaging with tweets and users. Each tool earns its place by addressing specific needs without redundancy, making the count ideal for the domain's complexity.
The tool surface provides complete CRUD/lifecycle coverage for X interactions, including creating (post_tweet), reading (get_tweet, get_timeline, search_tweets), updating (like_tweet, retweet, quote_tweet, reply_to_tweet), and deleting (delete_tweet), along with user management and media handling. No obvious gaps exist, supporting seamless agent workflows.