Twitter Api45 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Optional host configuration (listed as not applicable for stdio). | |
| PORT | No | Optional port configuration (listed as not applicable for stdio). | |
| API_KEY | Yes | Twitter Api45 API key required for authentication. |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| user_liveB | Checks if user is broadcasting something right now or not. |
| about_profileC | Returns the information about the profile's registration and usage |
| community_membersC | Gets the list of community members. |
| jobs_searchC | Search for the jobs on x.com/jobs |
| communities_posts_search_latestC | Search for the Latest posts in communities |
| communities_posts_search_topC | Search for the posts in communities post order top. |
| communities_searchC | Search for the communities on the X |
| followersC | Get latest user's followers list |
| user_infoC | Using this method you can get information about user by the screenname. |
| users_mediaC | Helps to get a user's media |
| profiles_by_restidsB | Returns an array of users by their rest_ids. |
| user_timelineC | This endpoint gets lates user's tweets by it's screenname. |
| comunity_postsC | Returns the posts from the community. |
| list_followersC | Get the followers of the list on Twitter / X |
| list_membersC | Get the members of the list on Twitter / X |
| list_timelineC | With this endpoint you can get the timeline of the lists. |
| user_repliesD | Gets user's replies of the user. |
| spaces_infoC | Give you the basic information about the spaces. |
| searchC | WARNING: The Search endpoint is rate limited for new customers to 60 requests/minute. Please contact me if you need a higher limit. Email: alexander.xbx@gmail.com |
| latest_repliesC | Gets the latest replies of the tweet. |
| check_followB | This endpoint get latest subscriptins of the user and latest followers for the target account. And checks if user follows the needed account. WARNING: might not be suitable for big accounts or old subscriptions. |
| tweet_infoC | With this endpoint you can get tweet info by it's id. |
| tweet_threadC | Gets the basic tweet info and the replies to it. |
| check_retweetB | This endpoint get latest tweets of the user and checks if there is a retweet of the needed tweet. WARNING: might not be suitable for old retweets. |
| trendsD | Please let me know if you need other countries in the list. |
| affilatesC | Give you the list of affilates for the corporate account. |
| retweetsC | Get the list of of users who retweeted the tweet. |
| followingC | Get the list of accounts user is following. |
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 28 tools
Most tools have distinct purposes targeting different Twitter/X resources (e.g., user_info vs. tweet_info vs. communities_search), but there is some functional overlap that could cause confusion. For example, 'followers' and 'list_followers' both retrieve follower lists but for different entities, while 'check_follow' and 'check_retweet' have similar verification logic but for different actions, potentially leading to misselection if not carefully read.
The naming is inconsistent with mixed conventions: some use snake_case (e.g., 'user_info', 'tweet_info'), others use camelCase (e.g., 'profiles_by_restids'), and some are verbose or unclear (e.g., 'comunity_posts' with a typo, 'communities_posts_search_latest'). There is no predictable pattern like verb_noun throughout, making it harder to navigate and understand the tool set at a glance.
With 28 tools, the count is too high for a typical MCP server, leading to potential bloat and complexity. While Twitter/X is a broad domain, many tools could be consolidated (e.g., multiple search and retrieval functions) or omitted to streamline the interface, making it feel heavy and less user-friendly for agents.
The tool set covers a wide range of Twitter/X functionalities, including user profiles, tweets, communities, lists, searches, and media, with good CRUD-like coverage for retrieval and verification. However, there are minor gaps, such as lack of tools for creating or modifying content (e.g., posting tweets, managing lists), which limits full lifecycle operations but still supports most read and search workflows effectively.