x-post-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X_CLIENT_ID | No | OAuth 2.0 client ID for auto-refresh token flow. | |
| X_BEARER_TOKEN | No | Your X API bearer token. Required if not using auto-refresh. | |
| X_CLIENT_SECRET | No | OAuth 2.0 client secret for auto-refresh token flow. | |
| X_REFRESH_TOKEN | No | OAuth 2.0 refresh token for auto-refresh token flow. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_tweetA | Post a new tweet to X (Twitter) |
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 1 tool
With only one tool, there is no possibility of confusion or overlapping purposes. The tool's purpose is clear and unique.
The single tool name 'send_tweet' follows a clear verb_noun pattern and is consistent. With only one tool, there are no inconsistencies to evaluate.
One tool is slightly below the typical well-scoped range, but it is reasonable for a narrowly focused posting service. The count feels minimal yet sufficient for the stated purpose.
The tool covers the core action of posting a tweet, which is the server's stated purpose. Minor gaps exist, such as no ability to delete or read tweets, but these are not essential for a post-only tool and can be worked around.