agent-twitter-client-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the MCP server (default 3000) | |
| NODE_ENV | No | Environment: development, production | |
| LOG_LEVEL | No | Logging level: error, warn, info, debug | |
| AUTH_METHOD | No | Authentication method: cookies, credentials, or api | |
| TWITTER_EMAIL | No | Optional email for credential authentication | |
| TWITTER_API_KEY | No | Twitter API key for API authentication | |
| TWITTER_COOKIES | No | JSON array of cookie strings for cookie authentication | |
| TWITTER_PASSWORD | No | Twitter password for credential authentication | |
| TWITTER_USERNAME | No | Twitter username for credential authentication | |
| TWITTER_2FA_SECRET | No | Optional 2FA secret for credential authentication | |
| TWITTER_ACCESS_TOKEN | No | Twitter access token for API authentication | |
| TWITTER_API_SECRET_KEY | No | Twitter API secret key for API authentication | |
| TWITTER_ACCESS_TOKEN_SECRET | No | Twitter access token secret for API 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_tweetsB | Fetch tweets from a specific user |
| get_tweet_by_idB | Fetch a specific tweet by ID |
| search_tweetsC | Search for tweets by keyword |
| send_tweetC | Post a new tweet |
| send_tweet_with_pollC | Post a tweet with a poll |
| like_tweetC | Like a tweet |
| retweetB | Retweet a tweet |
| quote_tweetC | Quote a tweet |
| get_user_profileC | Get a user's profile information |
| follow_userC | Follow a Twitter user |
| get_followersC | Get a user's followers |
| get_followingC | Get users a user is following |
| grok_chatB | Chat with Grok via Twitter |
| health_checkA | Check the health of the Twitter MCP server |
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 14 tools
Each tool targets a distinct action or resource: user relationships, tweet retrieval, tweet actions, chat, and health check. There is no obvious overlap between tools.
All tools use a consistent verb_noun pattern in snake_case (e.g., follow_user, get_tweet_by_id, send_tweet_with_poll). The naming is predictable and clear.
14 tools cover core Twitter operations (tweets, users, search, likes, retweets, polls) plus a health check and chat. The scope is well-balanced for a Twitter client.
The tool set covers essential read and write operations but lacks common actions like delete tweet, unlike, unfollow, or direct messaging. These gaps could hinder some workflows.