Skip to main content
Glama
afikrim

x-mcp-server

by afikrim

Related Servers

Alternatives to x-mcp-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      B
      maintenance
      Enables browser-based Twitter/X research and account workflows through a signed-in browser, supporting search, timeline/profile reads, saved searches, snapshot exports, and prepared account actions without requiring an X developer API key.
      25
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read public X (Twitter) data without the paid official API, including tweet and user search, profiles, timelines, media, replies, retweeters, followers, lists, and trends. All tools are read-only and rotate across multiple scraping accounts with proxy and rate-limit support.
      MIT
    • A
      license
      C
      quality
      B
      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
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables reading public X/Twitter posts by URL or numeric ID and returning original structured data, including articles, quoted posts, and media fields, without requiring an X API key.
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search X posts and read user timelines without API costs, using cookie authentication.
      2
      MIT

    TDQS

    A3.8/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct action (check auth, follow, get profile, get tweet, get user tweets, like, login, login with credentials, post, reply, search). Even the two login tools are clearly differentiated by method (interactive vs automated). There is no ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_auth, get_profile, like_tweet, search_tweets). The only deviation is login_with_credentials, which is still a verb phrase and fits the pattern. No mixing of styles.

    Tool Count5/5

    With 11 tools, the server covers the essential operations for interacting with X (authentication, profile viewing, tweeting, searching, following, liking, replying). The count is well-scoped for this domain, neither too few nor too many.

    Completeness4/5

    The tool set covers core X workflows: authentication, profile and tweet retrieval, posting, replying, liking, following, and searching. However, notable gaps exist, such as no retweet, quote tweet, delete tweet, unfollow, or direct message support. These are common actions that agents may need, but the set is still functional for basic interactions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues