Twitter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Twitter API key from the Twitter Developer Portal | |
| ACCESS_TOKEN | Yes | Your Twitter access token from the Twitter Developer Portal | |
| API_SECRET_KEY | Yes | Your Twitter API secret key from the Twitter Developer Portal | |
| ACCESS_TOKEN_SECRET | Yes | Your Twitter access token secret from the Twitter Developer Portal |
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 |
|---|---|
| post_tweetB | Post a new tweet to Twitter |
| search_tweetsC | Search for tweets on 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 2 tools
The two tools have clearly distinct purposes: one for posting tweets and one for searching tweets. There is no overlap in functionality.
Both tool names follow the verb_noun pattern: 'post_tweet' and 'search_tweets'. The naming is consistent and predictable.
With only 2 tools, the server feels thin for a Twitter API. It is borderline acceptable but lacks the breadth typically expected from a Twitter server.
The tool surface is severely incomplete. Missing fundamental operations like deleting tweets, liking, retweeting, or managing user interactions, which will cause agent failures.