MCP X Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACCESS_TOKEN | Yes | Twitter API access token | |
| CONSUMER_KEY | Yes | Twitter API consumer key | |
| ACCESS_SECRET | Yes | Twitter API access secret | |
| CONSUMER_SECRET | Yes | Twitter API consumer secret | |
| DEEPSEEK_API_KEY | Yes | DeepSeek API key for AI features |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_tweetC | Create a tweet |
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 ambiguity or confusion with other tools.
The single tool name 'create_tweet' follows a clear verb_noun pattern, consistent with itself.
A single tool for a Twitter-oriented server is insufficient; typical interacton with tweets requires multiple operations (read, delete, etc.), making this feel thin.
Only creation is covered; essential operations like reading, deleting, or listing tweets are missing, leaving significant gaps for an agent.