Skip to main content
Glama
IvanBBaev

x-mcp-ai

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to x-mcp-ai

No user-submitted related servers found.

    Related Servers

    • x-mcp-server

      N-Graves
      A
      license
      B
      quality
      C
      maintenance
      Enables access to the X API v2 through MCP, covering 175 of 190 published operations with tools for browsing, calling, posting, searching, and managing posts.
      7
      13 npm
      MIT

    • @twitterapis/mcp

      RajGehlot28
      A
      license
      A
      quality
      C
      maintenance
      Exposes the Twitter/X API as native MCP tools, letting agents search tweets and users, pull profiles, timelines, followers, lists, communities, and trends, and read account-scoped data like bookmarks, DMs, and home timeline. It also performs write actions such as posting, liking, retweeting, following, and their reversals, using an API key with optional linked or per-call X account credentials.
      99
      984 npm
      MIT

    • x-mcp

      RobertDWhite
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-based interaction with the X (Twitter) API v2, supporting reads like timeline, mentions, and search, and writes through a two-step draft-and-confirm process that ensures human-visible previews before any public post.
      -

    • x-agent-mcp

      alarok
      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
      34 npm
      2
      MIT

    • Twitter MCP Server

      kamflowersthemacrogod
      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.
      MIT

    • xengager-mcp

      ogunbaysal
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 41 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: posts, users, lists, media, DMs, engagements, and status checks are cleanly separated. The only potentially confusable group is the three DM event listers, but their descriptions clarify scope (all, conversation, participant) well enough. Even similar read/write pairs like x_bookmarks_list vs x_bookmark_set are unambiguous.

    Naming Consistency3/5

    Most tools follow an x_<resource>_<verb> pattern, but there are irregular deviations: x_search_recent/x_search_archive place the modifier after the verb, x_user_search uses noun+noun, x_lists_owned is a state not a verb, and x_timeline_home/mentions/user use scope as the final segment. The core convention is recognizable, but the inconsistencies would slow agent pattern recognition.

    Tool Count2/5

    At 41 tools, this server is well past the 16-25 range that already feels heavy for most servers. The broad X API scope explains the count, but an agent would face a large selection surface with many near-adjacent operations that could have been consolidated (e.g., count queries, multiple timeline variants).

    Completeness4/5

    The surface covers the major X features: post CRUD, search, timelines, lists, media, DMs, social graph, engagements, and usage/status. Minor gaps exist—no read-side listing for likes, mutes, or blocks, and no list-follower enumeration—but these are workable and do not create dead ends for typical workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources