twitterapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_URL | No | Proxy URL for enterprise environments (optional) | |
| HTTP_PROXY | No | Alternative proxy URL (optional) | |
| TWITTERAPI_API_KEY | Yes | Your TwitterAPI.io API key |
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 |
|---|---|
| get_user_by_usernameB | Get Twitter user information by username |
| get_user_by_idA | Get Twitter user information by user ID |
| get_user_tweetsB | Get tweets from a specific user |
| search_tweetsC | Search for tweets using keywords |
| get_tweet_by_idB | Get a specific tweet by its ID |
| get_tweet_repliesB | Get replies to a specific tweet |
| get_user_followersC | Get followers of a specific user |
| get_user_followingC | Get users that a specific user is following |
| search_usersC | Search for Twitter users |
| login_userA | Login to Twitter account for write actions (requires username and password) |
| create_tweetA | Create a new tweet (requires login) |
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 11 tools
Every tool maps to a distinct resource and action: user lookup by username/ID, tweet fetching by user/ID/search/replies, follower/following lists, and auth/write. No two tools overlap in purpose.
All tools follow a consistent snake_case verb_noun pattern (get_, search_, login_, create_). The naming convention is uniform and predictable across the entire set.
With 11 tools, the set is well-scoped for a Twitter API server covering basic reads, search, and a minimal write path. Each tool has a clear purpose and the count fits comfortably in the ideal range.
The read side is well covered (user, tweets, followers, search), and create_tweet provides a write entry point. However, there are notable missing operations such as delete/update tweet, follow/unfollow, or like/retweet, leaving the write surface incomplete.