x-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X_MCP_MODE | No | Safety mode: 'read-only' (default) or 'read-write'. | read-only |
| X_XURL_APP | No | The xurl application name used for OAuth token management. | |
| X_MCP_ACCOUNT | No | The active X account/profile to use. For env multi-account setups, also provide X_ACCOUNT_<ACCOUNT>_USER_ACCESS_TOKEN and X_ACCOUNT_<ACCOUNT>_REF... tokens. | |
| X_API_BASE_URL | No | Base URL for the X API. | https://api.x.com |
| X_AUTH_PROVIDER | No | Authentication provider: 'xurl' (recommended) or 'env' for legacy direct tokens. | |
| X_MCP_HTTP_PATH | No | HTTP MCP path when X_MCP_TRANSPORT=http. | /mcp |
| X_MCP_HTTP_PORT | No | HTTP port when X_MCP_TRANSPORT=http. | 3001 |
| X_MCP_TRANSPORT | No | Transport mode: 'stdio' for local MCP hosts, 'http' for ChatGPT tunnel. | stdio |
| X_XURL_USERNAME | No | The X username associated with the xurl app. | |
| X_USER_ACCESS_TOKEN | No | Legacy single-account access token for X_AUTH_PROVIDER=env. |
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 |
|---|---|
| x_get_active_accountA | Get the local X account profile selected for this MCP server installation. Does not expose tokens. |
| x_get_meB | Get the authenticated X user. |
| x_get_userC | Get an X user by username. |
| x_get_postB | Get a single X post by ID. |
| x_get_user_postsC | Get recent posts authored by an X user ID. |
| x_search_postsC | Search recent X posts using the official X query syntax. |
| x_create_postB | Publish a new X post. Requires X_MCP_MODE=read-write and tweet.write scope. |
| x_reply_postA | Reply to an X post. Requires X_MCP_MODE=read-write and tweet.write scope. |
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 8 tools
Tools have largely distinct purposes: get_active_account (local config) vs get_me (authenticated API user) vs get_user (by username) are differentiated by descriptions, and get_post vs get_user_posts vs search_posts are clearly separated. Minor potential confusion among the three user-retrieval tools, but descriptions resolve it adequately.
All tools follow a consistent snake_case pattern with an x_ prefix and verb_noun structure (e.g., x_get_user, x_create_post, x_reply_post). No deviations in style or convention.
Eight tools is well-scoped for a focused X API server covering basic read and write operations. Each tool earns its place, with no redundant or excessive entries.
The surface covers reading posts/users and creating posts/replies, but notable gaps exist: no delete or edit post, no like/retweet, and no follow/unfollow. These missing operations limit common agent workflows.