Skip to main content
Glama
kinhunt

twitterapi-mcp

by kinhunt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to twitterapi-mcp

No user-submitted related servers found.

    Related Servers

    • Twitter MCP Server

      aali-1
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol server that enables programmatic interaction with Twitter API, allowing users to post tweets, search for content, and retrieve user timelines through standardized MCP tools.
      17 npm
      MIT

    • TwitterAPI MCP Server

      Jing-yilin
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides access to Twitter data and write actions through TwitterAPI.io, bypassing the need for a standard Twitter developer account. It enables users to search tweets, retrieve profiles, and post content with support for pagination and enterprise proxy configurations.
      11 npm
      MIT

    • X (Twitter) MCP Server -

      mbelinky
      A
      license
      Not graded
      quality
      F
      maintenance
      An enhanced Model Context Protocol server that enables Claude to interact with Twitter/X, supporting tweet posting, searching, and deletion with both OAuth 1.0a and OAuth 2.0 authentication methods.
      93 npm
      24
      MIT

    • Twitter MCP Server

      EnesCinr
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that enables Claude to interact with Twitter, allowing for posting tweets and searching Twitter content.
      2
      331 npm
      409
      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

    A3.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool maps to a distinct resource and action: user lookup by username/ID, tweet fetching by user/ID/search/replies, follower/following lists, and auth/write. No two tools overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get_, search_, login_, create_). The naming convention is uniform and predictable across the entire set.

    Tool Count5/5

    With 11 tools, the set is well-scoped for a Twitter API server covering basic reads, search, and a minimal write path. Each tool has a clear purpose and the count fits comfortably in the ideal range.

    Completeness3/5

    The read side is well covered (user, tweets, followers, search), and create_tweet provides a write entry point. However, there are notable missing operations such as delete/update tweet, follow/unfollow, or like/retweet, leaving the write surface incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources