MCP Twitter NoAuth

Example Use Cases

• 1

  Search Twitter and retrieve recent tweets without storing OAuth credentials on the server itself.

• 2

  Post tweets or reply to tweets programmatically while delegating credential management to the client.

• 3

  Automatic access-token refresh and a headless, Docker-ready Twitter integration for remote deployments.

Description

This server implements the Model Context Protocol (MCP) to provide Twitter functionality (search, user tweets/replies, post tweets, reply to tweets) while keeping credentials decoupled from the server. Clients supply OAuth tokens or perform the OAuth flow independently, and the server supports automatic and manual refresh of access tokens. It is Docker-ready and intended for headless, remote environments where local browser or file access is not available.