X MCP Server

# X (Twitter) API Authentication Settings # ====================================== # # To use this MCP server, you need to obtain API credentials from Twitter/X: # 1. Go to https://developer.twitter.com/en/portal/dashboard # 2. Create a new app or use an existing one # 3. Navigate to "Keys and tokens" tab # 4. Generate the required credentials below # ====================================== # OAuth 2.0 Credentials (Optional - for future OAuth flows) # ====================================== # These are for OAuth user authorization flows (not used by MCP server currently) TWITTER_CLIENT_ID=your_oauth_client_id_here TWITTER_CLIENT_SECRET=your_oauth_client_secret_here # ====================================== # API Keys (Required for MCP server) # ====================================== # These are the credentials your MCP server actually uses # Required: API Key (Consumer Key) X_API_KEY=your_api_key_here # Required: API Secret (Consumer Secret) X_API_SECRET=your_api_secret_here # Required: Access Token X_ACCESS_TOKEN=your_access_token_here # Required: Access Token Secret X_ACCESS_TOKEN_SECRET=your_access_token_secret_here # Optional: Bearer Token (for v2 API endpoints) # This is useful for read-only operations X_BEARER_TOKEN=your_bearer_token_here # ====================================== # Authentication Setup Instructions: # ====================================== # # 1. Create a Twitter Developer Account: # - Visit https://developer.twitter.com/en/apply # - Apply for a developer account # - Wait for approval (usually 24-48 hours) # # 2. Create an App: # - Go to https://developer.twitter.com/en/portal/dashboard # - Click "Create App" or "Create Project" # - Fill in the required information # # 3. Get Your Credentials: # - In your app dashboard, go to "Keys and tokens" # - Copy the "API Key" and "API Secret" # - Generate "Access Token and Secret" (if not already created) # - Copy the "Bearer Token" (optional) # # 4. Set Permissions: # - In your app settings, ensure you have: # * Read permissions (for timeline and search) # * Write permissions (for posting tweets) # * Direct message permissions (if needed) # # 5. Configure Environment: # - Copy this file to .env # - Replace the placeholder values with your actual credentials # - Never commit .env to version control # # ====================================== # Security Best Practices: # ====================================== # # ✅ Store credentials in environment variables # ✅ Use .env file (already in .gitignore) # ✅ Never hardcode credentials in source code # ✅ Rotate credentials regularly # ✅ Use least privilege principle # ✅ Monitor API usage and rate limits # # ====================================== # Troubleshooting: # ====================================== # # If you get authentication errors: # 1. Verify all credentials are correct # 2. Check that your app has the right permissions # 3. Ensure your developer account is approved # 4. Check if you've hit rate limits # 5. Verify your app is in the right environment (dev/prod)