Twitter NoAuth

🚀 MCP Server - Twitter No-Auth Version

A server based on the Model Context Protocol (MCP) that provides access to the Twitter API without the need for local credential or token setup. It supports core Twitter operations such as searching for tweets, retrieving user tweets, posting tweets, and replying to tweets.

🚀 Quick Start

Demo Video

https://www.youtube.com/watch?v=LOxFqCTPedc

✨ Features

Why Choose the MCP Twitter No-Auth Server?

Core Advantages

• Headless Remote Operation: This server can run in a completely headless remote environment without the need for a browser or local file access.
• Decoupled Architecture: Supports authentication via OAuth2.0 PIN code authorization or application-only credentials.

Secondary Advantages

• Supports operations such as searching for tweets, retrieving user tweets, posting tweets, and replying to tweets.
• Provides an automatic token refresh function to avoid manual operations.

Function Overview

• Search Tweets: Supports searching for tweets by keywords, usernames, or filtering conditions (e.g., geographical location).
• Retrieve User Tweets: Can specify a user ID or screen name to retrieve a user's tweets and mentions.
• Post Tweets: Supports sending regular tweets and media files (images/GIFs/videos).
• Reply to Tweets: Can directly post comments via the tweet ID.

📦 Installation

Prerequisites

1. Register and log in to the Twitter Developer Portal.
2. Create a new project and application, and enable OAuth 2.0 authentication.
3. Configure the OAuth settings and generate a client ID and client secret.
4. Complete the OAuth process to obtain an initial access token and refresh token.

Method 1: Run the Executable File Directly

• Download the executable program for your corresponding platform (Windows/Linux/MacOS).
• Extract the file and double-click to run it.

Method 2: Compile and Run from Source Code

1. Clone the code repository.
2. Install the dependencies.
3. Configure the environment variables or modify the configuration file and fill in your Twitter API credentials.
4. Run the server program.

Docker Usage Instructions

# Pull the image
docker pull buryu/mcp-twitter-noauth

# Start the container
docker run -d --name mcp-twitter \
    -e CLIENT_ID=your_client_id \
    -e CLIENT_SECRET=your_client_secret \
    -e ACCESS_TOKEN=your_access_token \
    -e REFRESH_TOKEN=your_refresh_token \
    buryu/mcp-twitter-noauth

Configuration File Instructions

{
    "auth": {
        "client_id": "your_client_id",
        "client_secret": "your_client_secret",
        "access_token": "your_access_token",
        "refresh_token": "your_refresh_token"
    },
    "proxy": {
        "enabled": false,
        "host": "",
        "port": 0
    }
}

💻 Usage Examples

Basic Usage

Search Tweets

# Command-line call
curl -X POST http://localhost:8080/api/search \
     -H "Content-Type: application/json" \
     -d '{"query":"#加密","count":10}'

# Or call via a tool
{
    "method": "search_tweet",
    "parameters": {
        "query": "#加密",
        "count": 10
    }
}

Post Tweets

curl -X POST http://localhost:8080/api/post \
     -H "Content-Type: application/json" \
     -d '{"text":"这条推文来自 MCP 服务端"}'

🔧 Technical Details

Regular Maintenance

Token Management

1. It is recommended to regularly check the token validity period and update the refresh token in a timely manner.
2. If you find that the token has been leaked or suspect a security issue, please immediately reset the OAuth keys.

Log Monitoring

It is recommended to enable the log recording function to monitor API call status and exception information in real-time:

docker logs -f mcp-twitter

Security Tips

• Do not disclose your Twitter API credentials to untrusted third parties.
• It is recommended to use HTTPS in a production environment and configure an SSL certificate.

📄 License

Please refer to the LICENSE file for detailed information.