Skip to main content
Glama
BACH-AI-Tools

Twitter241 MCP Server

Related Servers

Alternatives to Twitter241 MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents and coding assistants with Twitter data access including tweets, user profiles, followers, and search functionality.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Allows AI assistants to query Twitter data including user info, tweets, trends, and more via twitterapi.io API.
      12
      6
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Twitter/X data to retrieve user profiles, search tweets, and track engagement metrics. It provides advanced capabilities for monitoring follower events, KOL activity, and accessing deleted tweets.
      12
      1,450
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to search, read user profiles, timelines, media, follow threads, track trends, and manage accounts on X/Twitter via GraphQL, without browser automation or paid API keys.
      100
      10
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Real-time X (Twitter) data platform with 2 MCP tools covering 120+ REST API endpoints. Search tweets, look up users, get timelines, extract followers/likes/retweets in bulk, monitor accounts, run giveaway draws, and perform write actions (tweet, like, retweet, follow, DM). OAuth 2.1 authentication with PKCE.
      2
      417
      193
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to access FxTwitter/FxEmbed read-only APIs, exposing tools for retrieving posts, threads, conversations, user profiles, media, followers, search results, and trends.
      MIT

    TDQS

    C2.1/5.0

    Scored across 47 tools

    Disambiguation1/5

    Multiple tools appear to do the same thing (e.g., get_tweet_details and get_tweet_details_v2, get_users_by_ids and get_users_by_ids_v2, search_twitter and search_twitter_v2), with no clear distinction between versions. The naming of get_list vs get_list_details vs get_list_timeline also adds confusion, making it difficult for an agent to reliably select the correct tool.

    Naming Consistency2/5

    Most tools follow a get_verb_noun pattern, but there are notable exceptions like autocomplete, job_details, space_details, and fetch_popular_community. The use of v2 suffixes is inconsistent, and some names are vague (e.g., get_about_account, get_list), so the pattern is not predictable across the set.

    Tool Count2/5

    With 47 tools, the server is heavily bloated, especially given the redundant v2 pairs. This exceeds the threshold for a well-scoped tool set, and many tools could be consolidated or removed without losing functionality.

    Completeness3/5

    The server covers a broad range of read-only operations for Twitter data (users, tweets, communities, lists, trends, jobs, spaces), which is fairly complete for a retrieval-focused API. However, there are no write operations (create, update, delete) and some obvious gaps like user mentions or tweet posting, but these may be out of scope for the intended use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues