Skip to main content
Glama
BK927

X Research MCP

by BK927

Related Servers

Alternatives to X Research MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to X (Twitter) data — posts, threads, profiles, timelines, followers, media, and trends — through twelve tools, with no login or API key required.
      2
      12
      MIT
    • F
      license
      Not graded
      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.
      -
    • 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
      B
      maintenance
      Enables reading public X (Twitter) content like profiles, tweets, and search results via a stealth browser, without official API costs.
      11
      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
      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
      194 npm
      197
      MIT

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct data surface: search, post, user, collection, trends, saved-result analysis, raw saved-result retrieval, and server status. x_analyze and x_result_get both operate on saved results, but one computes aggregates while the other returns raw stored chunks, so an agent should not confuse them.

    Naming Consistency4/5

    Most tools follow an x_<resource>_get pattern: x_post_get, x_user_get, x_collection_get, x_trends_get, and x_result_get. The exceptions are x_search, x_analyze, and x_status, which break that resource-get convention, but the shared x_ prefix and lowercase snake_case keep the naming mostly predictable.

    Tool Count5/5

    Eight tools is well-scoped for a read-only X research server. Each tool serves a distinct need, and none feel redundant or excessive for the stated purpose.

    Completeness4/5

    The tool surface covers search, post/user/collection/trends reads, saved-result access, and aggregation, which supports the research workflow well. Minor gaps such as no explicit saved-result listing/deletion or batch operations can be worked around by repeated calls or using existing saved-result access.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues