Skip to main content
Glama
x-api-mcp

x-api-mcp

by fatwang2

Related Servers

Alternatives to x-api-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants and local operators to publish approved posts, linear threads, replies, and Community posts to X through a Playwright-driven authenticated browser session, without X API credits. Also exposes read-only tools to check session status and list Communities available to the account, via stdio or bearer-protected Streamable HTTP.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients such as Claude and Cursor to read timelines, search statuses, and look up users or conversations, plus optionally post, delete, favorite, and follow with explicit confirmation. It supports both local stdio launches and remote HTTP hosting with per-user authorization.
      15
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables interaction with the X (Twitter) API through MCP tools for managing users, posts, bookmarks, likes, and lists. Supports markdown or JSON output and uses OAuth 2.0 PKCE authentication.
      22
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search and read X (Twitter) posts, publish posts and threads, upload media, and track account activity through budget-guarded tools that require a dry-run confirmation before anything is published and log estimated spend locally.
      MIT
    • 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.
      -

    TDQS

    A3.5/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools target distinct resource+action combinations, and the auth cluster (add_account, auth_status, complete_authorization) is well-differentiated by description. Minor overlap exists between get_posts, get_timeline, and search for retrieving posts, but descriptions clarify the boundaries.

    Naming Consistency4/5

    The large majority follow a clear verb_noun pattern (get_posts, create_post, delete_post, get_users, set_default_account). Deviations are the noun_action bundles (list_action, post_action, user_action), the bare 'search', and 'auth_status', but these remain readable and the *_action group is internally consistent.

    Tool Count4/5

    24 tools is slightly heavy but justified by the broad X API surface spanning auth, posting, media, timelines, search, lists, users, and relations. Each tool maps to a meaningful capability with little redundancy.

    Completeness4/5

    Core workflows are well covered: OAuth account lifecycle, posting/threads/deletes, engagement actions, media upload, timelines, search, lists, and user relations. Gaps like direct messages, profile editing, and pinned-post management exist but are outside the stated posting/reading focus.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues