Skip to main content
Glama
krishna-paulraj

X MCP Server

by krishna-paulraj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to X MCP Server

No user-submitted related servers found.

    Related Servers

    • X (Twitter) MCP Server

      Dishant27
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with X (formerly Twitter), allowing for posting tweets, searching content, managing accounts, and organizing lists.
      20 npm
      3
      MIT

    • x-mcp-server

      MindMadeLab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with X (Twitter) API v2 for posting tweets, searching, liking, retweeting, and more through natural language.
      MIT

    • X (Twitter) MCP

      arnaldo-delisio
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with X (Twitter) to post tweets, threads, and replies while retrieving tweet metrics and account information. It supports core management tasks like deleting tweets and verifying authentication through the Twitter API.
      MIT

    • TwitGhost

      arvinmoj
      A
      license
      B
      quality
      D
      maintenance
      Enables interacting with Twitter/X through natural language, including searching tweets, posting, sending DMs, and managing timelines via any MCP client.
      8
      MIT

    • Apex MCP for X Management

      xonack
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables complete management of X (Twitter) accounts through a single API key, supporting functions like getting tweets, searching, generating and posting replies.
      24 npm
      2
      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

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_user_timeline retrieves a user's recent tweets, post_tweet creates a new tweet, and search_tweets finds tweets by query. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_user_timeline, post_tweet, search_tweets) with clear, descriptive verbs. The naming is uniform and predictable across the set.

    Tool Count3/5

    With only 3 tools, the server feels slightly thin for a Twitter/X integration, as it lacks operations like deleting tweets, managing likes, or handling direct messages. However, it covers basic posting and reading, which is reasonable for a minimal scope.

    Completeness3/5

    The tools provide core read and write capabilities (get, post, search) but miss key Twitter/X features such as tweet deletion, like/unlike, retweeting, or user profile management. This leaves notable gaps that agents might need to work around for full functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources