Twitter NoAuth

- Headless & Remote Operation: This server can run completely headless in remote environments with no browser and no local file access.
- Decoupled Architecture: Any client can complete the OAuth flow independently, then pass credentials as context to this MCP server, creating a complete separation between credential storage and server implementation.

- Focused Functionality: Provides core Twitter operations like searching tweets, getting user tweets, posting tweets, and replying to tweets.
- Docker-Ready: Designed with containerization in mind for a well-isolated, environment-independent, one-click setup.
- Reliable Dependencies: Built on standard Python requests library for Twitter API integration.

- Search tweets using Twitter API
- Get recent tweets by a specific user
- Get recent replies by a specific user
- Post new tweets
- Reply to existing tweets
- Refresh access tokens separately
- Automatic refresh token handling

- Python 3.10 or higher
- Twitter API credentials (client ID, client secret, access token, and refresh token)

# Clone the repository git clone https://github.com/yourusername/mcp-twitter-noauth.git cd mcp-twitter-noauth # Install dependencies pip install -e .

# Build the Docker image docker build -t mcp-twitter-noauth .

You can configure Claude Desktop to use the Docker image by adding the following to your Claude configuration:

To publish the Docker image for multiple platforms, you can use thedocker buildxcommand. Follow these steps:
-

Create a new builder instance(if you haven't already):

Build and push the image for multiple platforms:

docker buildx build --platform linux/amd64,linux/arm64,linux/arm/v7 -t buryhuang/mcp-twitter-noauth:latest --push .

Verify the image is available for the specified platforms:

docker buildx imagetools inspect buryhuang/mcp-twitter-noauth:latest

The server provides Twitter functionality through MCP tools. Authentication handling is simplified with a dedicated token refresh tool.

When using an MCP client like Claude, you have two main ways to handle authentication:

Refreshing Tokens (First Step or When Tokens Expire)

If you have both access and refresh tokens:

{ "twitter_access_token": "your_access_token", "twitter_refresh_token": "your_refresh_token", "twitter_client_id": "your_client_id", "twitter_client_secret": "your_client_secret" }

If your access token has expired, you can refresh with just the refresh token:

{ "twitter_refresh_token": "your_refresh_token", "twitter_client_id": "your_client_id", "twitter_client_secret": "your_client_secret" }

This will return a new access token and its expiration time, which you can use for subsequent calls.

Search for tweets using the Twitter API:

{ "twitter_access_token": "your_access_token", "query": "your search query", "max_results": 10 }

Response includes tweet data including text, creation time, and author information.

{ "twitter_access_token": "your_access_token", "user_id": "twitter_user_id", "max_results": 10 }

{ "twitter_access_token": "your_access_token", "user_id": "twitter_user_id", "max_results": 10 }

{ "twitter_access_token": "your_access_token", "text": "This is a test tweet from the MCP Twitter server" }

{ "twitter_access_token": "your_access_token", "tweet_id": "id_of_tweet_to_reply_to", "text": "This is a reply to the original tweet" }

- Start by calling thetwitter_refresh_tokentool with either:

- Your full credentials (access token, refresh token, client ID, and client secret), or
- Just your refresh token, client ID, and client secret if the access token has expired

This approach simplifies most API calls by not requiring client credentials for every operation, while still enabling token refresh when needed.

This server implements automatic token refreshing. When your access token expires, the server will use the refresh token, client ID, and client secret to obtain a new access token without requiring user intervention.

This server requires direct access to your Twitter API credentials. Always keep your tokens and credentials secure and never share them with untrusted parties.

Manage your X (Twitter) account using the Apex social media infrastructure. Requires an Apex API Key.

MCP server for posting to X (Twitter) with multi-account support

Twitter/X tools for AI agents — read timelines, post tweets, search, and engage

Interact with Twitter to post and search for tweets.

A server for interacting with Twitter, allowing you to post tweets, read timelines, and manage your account through the MCP standard.

An MCP server for interacting with the X (Twitter) API, requiring developer credentials.

Integrate with the X (Twitter) API for workflow automation, enhanced error handling, and real-time documentation.

Official MCP server for twitterapis.com: Twitter/X search, users, followers, tweets, threads, lists, likes, bookmarks, DMs, plus post/like/retweet/follow actions as native Claude/Cursor tools.

Schedule and queue text, image, and video posts to many social networks, including LinkedIn, X, Bluesky, Instagram, Facebook, Threads, Tiktok.