Twitter NoAuth

What it is

A Twitter server designed to hold no credentials of its own. Every call carries the tokens it needs as arguments, so the process can run headless in a container with no browser, no local files and nothing to leak if the host is shared.

What you get

• Search tweets by query, with max_results to bound the response
• Recent tweets by a given user_id, and recent replies by that user
• Post a new tweet from text
• Reply to an existing tweet by tweet_id
• twitter_refresh_token exchanges a refresh token for a new access token and its expiry
• Refreshing works with just the refresh token, client ID and client secret once the access token has expired

Requirements

Python 3.10 or higher, or the published Docker image. Twitter API credentials from the Twitter Developer Portal — client ID, client secret, access token and refresh token — obtained by completing the OAuth flow yourself. Those values are passed as tool arguments rather than environment variables, which is the whole point of the design: the client keeps the credentials, the server never stores them.

Setup effort

One command plus credentials — docker run -i --rm buryhuang/mcp-twitter-noauth:latest, then supply credentials

Tools you get

1 tool named in the project's documentation. The README describes searching tweets, reading a user's tweets and replies, posting and replying, but names only twitter_refresh_token.

Requires

• docker on PATH
• Python 3.10 or later

Where it runs

The documented client runs the server on your machine.