Skip to main content
Glama
TweetAPI MCP

TweetAPI MCP

Official

Related Servers

Alternatives to TweetAPI MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read public X (Twitter) data without the paid official API, including tweet and user search, profiles, timelines, media, replies, retweeters, followers, lists, and trends. All tools are read-only and rotate across multiple scraping accounts with proxy and rate-limit support.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents and coding assistants with Twitter data access including tweets, user profiles, followers, and search functionality.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only access to public X (Twitter) data, including profiles, tweets, timelines, threads, followers, and search, for developers and AI agents.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      It enables AI agents to read public Twitter/X tweets, profiles, followers, lists, communities, trends and search results through TwittrAPI without an X developer account, and can optionally act on the user's own account to post, like, follow and send DMs.
      30
      125 npm
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables AI agents to search, read user profiles, timelines, media, follow threads, track trends, and manage accounts on X/Twitter via GraphQL, without browser automation or paid API keys.
      113
      721 PyPI
      12
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to search and read public X/Twitter posts without an API key, fetching single or batched posts by ID or URL, running operator-filtered keyword searches with hydrated full-text results, and retrieving public profile metadata.
      6
      MIT

    TDQS

    A4/5.0

    Scored across 52 tools

    Disambiguation3/5

    Most tools map cleanly to one X endpoint, but there are real overlap clusters: tweetapi_user_followers_v2 vs tweetapi_user_followers_list (same data, differing only in whether count is settable), and tweetapi_docs_search vs tweetapi_endpoint_lookup, which both take a keyword and return scored snippets with source URLs. The descriptions do acknowledge the alternatives and cross-reference each other, but an agent still has to read carefully to pick correctly.

    Naming Consistency4/5

    Every tool shares the tweetapi_ prefix and snake_case with a resource_then_action shape (tweetapi_user_by_ids, tweetapi_list_members, tweetapi_community_tweets), which is highly predictable. The main blemishes are the legacy suffix tweetapi_user_followers_v2/_following_v2 sitting next to _list and _ids variants, and a few names that describe the return shape rather than an action.

    Tool Count2/5

    52 tools is well past the point where an agent can hold the surface in mind, and the count is inflated by near-duplicates (profile-by-id vs -by-username vs -by-ids vs -by-usernames, followers v2/list/ids) rather than genuinely distinct operations. It mirrors a large upstream API, but as an MCP tool set it is heavy and hard to navigate.

    Completeness4/5

    Coverage is broad and coherent for a read-only X data API: users, followers/following graphs, tweets and conversations, lists, communities, Spaces, trends, search, plus docs, SDK guidance, a catalog and usage checks. Gaps are minor and mostly domain-bounded (no DMs, no notifications, no write/post actions, no Spaces discovery beyond lookup by ID), so agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues