Skip to main content
Glama

Related Servers

Alternatives to x-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that provides AI agents with full access to the X (Twitter) API for posting, searching, and managing engagement through natural language. It supports comprehensive tools for tweet management, media uploads, and account analytics across multiple MCP-compatible clients.
      15
      54
      -
    • F
      license
      Not graded
      quality
      F
      maintenance
      A local MCP server that exposes the X API (formerly Twitter API) as tools, enabling operations like posting, searching, user management, and more via natural language commands.
      860
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to automate actions on X (Twitter) through a real browser session, including posting, engaging, and reading via over 40 tools. It supports self-hosting and provides a panel for API key management.
      0
      7
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      MCP server for the official X API, enabling agents to read and publish posts, look up users, and search posts with safe read-only default and explicit write mode.
      8
      9 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with the Twitter/X API v2, enabling AI assistants to retrieve tweets, post content, reply, quote, and more programmatically.
      1,734 npm
      13
      MIT

    TDQS

    B3.3/5.0

    Scored across 23 tools

    Disambiguation2/5

    Several tools have overlapping purposes: `account_pulse` and `post_performance` both report on post metrics, `inbox` and `conversation` both list mentions/replies, `scout` and `search` both query posts, and `handoff` bundles multiple sub-actions (list, draft, approve) that overlap with `approvals` and `draft_check`. The descriptions help, but an agent would need to read carefully to pick the right tool.

    Naming Consistency2/5

    Naming is a mix of nouns (doctor, scout, handoff), verbs (publish, delete_post, schedule), and composites (account_pulse, draft_check, suggest_follows). No consistent pattern like verb_noun throughout. Some names are opaque (doctor, scout) while others are descriptive, making the set feel ad hoc.

    Tool Count3/5

    23 tools is on the heavy side, but the server covers a wide domain: reading/writing posts, DMs, analytics, contacts, approvals, and account health. Several tools bundle multiple operations (handoff, people, schedule) which inflates the count, but the scope justifies a larger surface. Still, some consolidation—merging account_pulse with report, or inbox with conversation—would tighten the set.

    Completeness3/5

    The toolset covers the main lifecycle: create/read/delete posts, read/reply to conversations, manage people, schedule, and monitor spend/rate limits. However, key gaps exist: no update/edit post, no like/unlike or follow/unfollow (only handoff for human-doable actions), and no explicit tool for managing drafts beyond scheduling. This means some user intents will dead-end.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues