Skip to main content
Glama

Related Servers

Alternatives to Spectre

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to fully automate X/Twitter interactions including searching, posting, engaging, and managing multiple accounts without paid API keys.
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects AI assistants to Twitter/X using cookie-based authentication to read timelines, search tweets, and perform actions like posting and liking. It leverages Twitter's internal GraphQL API to provide full functionality without requiring a developer account.
      8 npm
      -
    • 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
      Not graded
      quality
      D
      maintenance
      Provides AI agents and coding assistants with Twitter data access including tweets, user profiles, followers, and search functionality.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with Twitter/X through Playwright browser automation without requiring an official API key. It provides tools for posting content, searching tweets, reading feeds, and managing social interactions like follows and likes.
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM agents to interact with Twitter (X) for searching tweets, posting content with images, analyzing engagement, and extracting topics using the Twitter API.
      -

    TDQS

    C2.9/5.0

    Scored across 104 tools

    Disambiguation3/5

    Most tools have distinct resource-action targets, but several pairs overlap meaningfully (list_accounts vs pool_status, get_user_tweets vs get_user_tweets_and_replies, get_muted_accounts vs get_dm_muted). The high number of choices increases misselection risk, though the descriptions usually clarify boundaries.

    Naming Consistency4/5

    The server consistently uses snake_case verb_noun names like get_tweet, post_tweet, create_list, and unlike_tweet. Minor deviations exist—remove vs delete, pool_status instead of get_pool_status, and phrase-like names such as get_followers_you_know—but the overall pattern remains predictable.

    Tool Count1/5

    104 tools is an extreme count for an MCP server and creates a heavy selection burden for agents. Even for a broad X/Twitter domain, many niche actions could be consolidated through parameters or grouped resources, so the surface is clearly oversized.

    Completeness4/5

    The surface covers nearly the full X/Twitter lifecycle: reading, posting, deleting tweets, engagement, DMs, lists, bookmarks, communities, profiles, scheduling, and drafts. Minor gaps exist—such as no way to add accounts to the pool or fetch the current authenticated profile directly—but these are workable and do not undermine core workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues