Skip to content

Conversation

@baryhuang
Copy link
Contributor

Description

Implementation of a new MCP server providing Twitter API access without local credential setup. This server enables headless Twitter operations in remote environments through a decoupled architecture.

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

Server Details

  • Server: twitter-noauth
  • Changes to: tools

Motivation and Context

This server allows for completely headless Twitter API operations in remote environments with no browser access. It creates a separation between credential storage and implementation by allowing any client to complete the OAuth flow independently, then pass credentials as context parameters. This enables Twitter API operations (search, post, reply) through MCP without local token setup.

How Has This Been Tested?

Tested with Claude Desktop client using Docker configuration. Testing scenarios included searching tweets, retrieving user tweets, posting tweets.

Breaking Changes

N/A

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

@baryhuang baryhuang closed this Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant