Skip to main content
Glama

Related Servers

Alternatives to @twitterapis/mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to interact with X (Twitter) through its private GraphQL API using session cookies, supporting tweets, replies, likes, retweets, searches, direct messages, and more. Provides 24 MCP tools for full account automation.
      24
      33 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables interacting with Twitter/X through natural language, including searching tweets, posting, sending DMs, and managing timelines via any MCP client.
      8
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to access Twitter/X data including user profiles, tweets, search, and follower events via a set of MCP tools.
      1
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      MCP server for the official X API, enabling agents to read and publish posts, look up users, and search posts with safe read-only default and explicit write mode.
      8
      5 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides programmatic X (Twitter) engagement via MCP, offering 24 tools for search, timelines, notifications, bookmarks, profiles, and tweet actions through a headless browser.
      MIT

    TDQS

    A3.9/5.0

    Scored across 99 tools

    Disambiguation3/5

    Many tools have genuinely overlapping purposes: twitter_user_tweets vs twitter_user_tweets_and_replies (descriptions admit they return 'overlapping or identical pages'), twitter_user_tweets vs twitter_user_tweets_complete, twitter_user_followers/following vs their _v2 twins, and the twitter_x_user_stream_* compat drop-ins duplicating twitter_monitor_* operations. The descriptions are unusually thorough at drawing the boundaries and warning about pitfalls, which prevents outright misselection, but the sheer number of near-duplicate surfaces keeps this from being clean.

    Naming Consistency5/5

    Tool names use a strict namespace_topic_action snake_case pattern throughout (twitter_user_info, twitter_tweet_replies, twitter_list_members, twitter_monitor_webhook_create). Verb/noun ordering is predictable within each family, and even the few outliers (twitter_grok_chat, twitter_account_me, twitter_trends) read consistently with the surrounding convention.

    Tool Count1/5

    99 tools is far beyond what any agent can reliably navigate in one context; the surface spans tweets, users, lists, communities, Spaces, DMs, bookmarks, articles, webhooks, monitors, sessions and feedback. Many of the 99 are redundant versions (v1/v2 pairs, compat shims) that inflate the count without adding capability.

    Completeness5/5

    The surface is exceptionally complete: full read/write CRUD across tweets, articles, lists, monitors and webhooks, plus session lifecycle, media upload/status, DMs, bookmarks, communities, Spaces and feedback. Both read and write paths have their create/update/delete counterparts and lifecycle edge cases are explicitly covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues