Skip to main content
Glama
TwitterAPIs

twitterapis

by TwitterAPIs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to twitterapis

No user-submitted related servers found.

    Related Servers

    • mcp-twikit

      arvinmoj
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for interacting with Twitter, enabling search tweets and fetching timeline via natural language.
      MIT

    • X MCP Server

      siddheshutd
      A
      license
      B
      quality
      D
      maintenance
      MCP server for interacting with the X platform (Twitter) via MCP clients like Claude, Cursor AI, and Windsurf AI.
      20
      5 npm
      6
      MIT

    • twscrape-twitter-mcp

      jsilets
      A
      license
      A
      quality
      A
      maintenance
      MCP server to read X (Twitter) posts, threads, replies, quotes, and search using your own logged-in session, no API key required.
      8
      3
      MIT

    • x-mcp-server

      lluisfont
      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
      5 npm
      -
    • X API FastMCP Server by xdevplatform

      X API FastMCP Serverofficial

      xdevplatform
      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.
      854
      -
    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.7/5.0

    Scored across 94 tools

    Disambiguation2/5

    Multiple tools have unclear boundaries: twitter_user_tweets and twitter_user_tweets_and_replies are explicitly described as returning overlapping or identical pages, twitter_user_followers/following have v2 variants with the same inputs, and the twitter_x_user_stream_* tools are redundant compat drop-ins for monitor tools. The descriptions are detailed, but an agent would frequently need to read carefully to avoid picking the wrong near-duplicate.

    Naming Consistency5/5

    Every tool follows a consistent twitter_<domain>_<action> snake_case pattern, with predictable verbs like list, create, delete, update, get, info, and search. Even the legacy compat tools and account tools fit the same naming scheme, making the naming exemplary.

    Tool Count1/5

    94 tools is far beyond the 50+ threshold for an extreme mismatch, making the surface unwieldy for an agent to navigate. The broad Twitter/X domain explains some of the size, but redundant v1/v2 pairs and legacy compat endpoints inflate the count unnecessarily.

    Completeness4/5

    The tool surface is remarkably deep: it covers tweet/retweet/favorite/bookmark/DM/action lifecycles, article CRUD, monitor and webhook management, lists, communities, spaces, media upload, trends, and authenticated account reads. Minor gaps exist, such as no list update/delete and no block/mute write actions, but agents can generally work around them.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources