MCP Twitter/X Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TWITTER_API_KEY | Yes | Your Twitter API Key | |
| TWITTER_API_SECRET | Yes | Your Twitter API Secret | |
| TWITTER_ACCESS_TOKEN | Yes | Your Twitter Access Token | |
| TWITTER_BEARER_TOKEN | Yes | Your Twitter Bearer Token | |
| TWITTER_ACCESS_TOKEN_SECRET | Yes | Your 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_postsB | Fetch the latest posts from a specified Twitter/X user |
| create_postB | Create a new post on Twitter/X |
| get_postA | Get a specific tweet by ID |
| search_postsC | Search for tweets matching a query |
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 4 tools
Each tool has a clearly distinct purpose: fetching a user's timeline, creating a post, retrieving a specific post by ID, and searching by query. There is no meaningful overlap between any pair of tools.
All names follow a verb_noun pattern (read_posts, create_post, get_post, search_posts), but pluralization is inconsistent (posts vs post) and 'read' vs 'get' are semantically similar yet used for different operations. Minor deviations from perfect consistency.
With only 4 tools, the server is well-scoped for a minimal Twitter/X client. Each tool covers a core action without unnecessary duplication or overwhelming the agent.
The surface covers reading (individual and timeline), creating, and searching posts, but notably lacks a delete operation, leaving a dead end after creation. No user profile or account-related tools, which is a notable gap for the domain.