Twitter NoAuth

Twitter NoAuth is an MCP server that provides access to the Twitter API without storing credentials or environment variables on the local host. It connects Model Context Protocol clients directly to Twitter endpoints for both read and write operations. Developers, automation builders, and social media researchers who operate in headless, remote, or containerized environments use this server to interact with Twitter programmatically. Because the architecture decouples credential storage from server execution, client applications complete the OAuth flow independently and supply tokens directly during tool calls. This allows users to search tweets, retrieve recent tweets or replies from target user profiles, publish new posts, and reply to existing threads without maintaining local configuration files. The server also includes tools to handle token refreshes, allowing agents to renew expired access tokens using OAuth client identifiers and refresh tokens. By accepting authentication parameters dynamically, Twitter NoAuth supports multiple user contexts and eliminates the need to configure fixed API keys during deployment.

Category: Communication & Messaging

Tags: microblogging, social-media, twitter, x

Visit Twitter NoAuth

How to install and configure Twitter NoAuth

1. Clone the repository and navigate into the project folder: bash git clone https://github.com/yourusername/mcp-twitter-noauth.git cd mcp-twitter-noauth 2. Install dependencies locally with pip install -e . or build the container image using docker build -t mcp-twitter-noauth .. 3. To run with Claude Desktop, add the Docker runner to your Claude configuration file: json { "mcpServers": { "twitter": { "command": "docker", "args": [ "run", "-i", "--rm", "buryhuang/mcp-twitter-noauth:latest" ] } } } 4. Alternatively, start the server locally with mcp-server-twitter-noauth. 5. Pass required credentials like twitter_access_token and twitter_refresh_token directly in each tool call.

What you can do with Twitter NoAuth

• Querying recent tweets matching specific keywords and retrieval limits to monitor live conversations without embedding persistent developer keys in the environment. - Fetching the recent posts or replies of a designated user identifier to track public responses or compile activity summaries. - Publishing new status updates to an account by supplying an active OAuth access token directly in the prompt or tool argument. - Replying to specific tweet IDs programmatically during automated customer service workflows or AI-driven discussion threads. - Refreshing expired Twitter access tokens using client credentials and refresh tokens to ensure uninterrupted session continuity across headless tasks.

Key facts

• https://github.com/baryhuang/mcp-twitter-noauth
• Communication & Messaging, Web Search & Research
• microblogging, social-media, twitter, x

Part of MCP Servers

How do I install Twitter NoAuth?

You can install Twitter NoAuth locally by cloning its repository and running pip install -e ., or by building the provided Dockerfile. Alternatively, you can pull and run the prebuilt Docker image buryhuang/mcp-twitter-noauth:latest directly inside your MCP client configuration without local Python setup.

What can Twitter NoAuth do?

The server provides tools to search Twitter posts using queries, fetch recent tweets and replies by user ID, publish new tweets, and reply to specific tweet IDs. It also includes dedicated tools to refresh OAuth access tokens dynamically when they expire.

Which MCP clients work with Twitter NoAuth?

Twitter NoAuth works with any Model Context Protocol compliant client, including Claude Desktop. Because it supports standard input and output communication via Docker or local command execution, any agent framework that supports MCP tool calling can integrate with it.

How does authentication work in Twitter NoAuth?

Rather than storing Twitter API keys in environment variables or configuration files, Twitter NoAuth requires access tokens to be passed at runtime during tool execution. When tokens expire, users can call the refresh token tool with their client credentials to generate new access tokens dynamically.