Skip to main content
Glama
LesterAJohn

x-mcp

by LesterAJohn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to x-mcp

No user-submitted related servers found.

    Related Servers

    • openapi-to-mcp

      AudienceLabV3
      A
      license
      Not graded
      quality
      D
      maintenance
      Auto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.
      19 npm
      MIT

    • OpenAPI MCP

      pvliesdonk
      A
      license
      Not graded
      quality
      B
      maintenance
      A generic MCP server that builds its tools at runtime from any OpenAPI specification, enabling interaction with any REST API through natural language.
      MIT

    • Public API MCP Server

      ampeco
      A
      license
      Not graded
      quality
      D
      maintenance
      Transforms OpenAPI specs into an MCP server, enabling dynamic API interaction through natural language with automatic authentication and endpoint discovery.
      131 npm
      MIT

    • ClawQL

      danielsmithdevelopment
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for API discovery and execution with a token-efficient search -> execute workflow over OpenAPI, Google Discovery, and optional native GraphQL and gRPC sources.
      60 npm
      12
      Apache 2.0

    • odata-mcp-proxy

      lemaiwo
      A
      license
      Not graded
      quality
      D
      maintenance
      A config-driven MCP server that exposes OData and REST APIs as MCP tools, enabling AI assistants to query, manage, and monitor SAP backends through natural language.
      59 npm
      29
      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.4/5.0

    Scored across 179 tools

    Disambiguation3/5

    Most x_api_* tools target distinct resource actions, but overlapping families exist (e.g., account_activity_subscription vs activity_subscription, get_users_timeline vs get_users_posts, reposted_by vs reposts) that could cause misselection. Descriptions help differentiate, but the sheer volume of similarly named tools makes boundaries less clear.

    Naming Consistency4/5

    The dominant pattern is x_api_<verb>_<resource> and is applied consistently across the huge endpoint set. Minor deviations exist: 'remove' vs 'delete', 'add' vs 'create', and unofficial core tools use x_config_*/x_auth_* prefixes, but the pattern is still readable and predictable.

    Tool Count1/5

    With 179 tools, this is an extreme count far beyond the calibration guidance for well-scoped servers. The server appears to be a raw auto-generated wrapper around the entire X API, which overwhelms agents and makes discovery and selection impractical.

    Completeness5/5

    The tool surface is remarkably comprehensive, covering CRUD and lifecycle operations for posts, users, lists, DMs, media, spaces, trends, compliance, webhooks, activities, articles, community notes, and insights. Core auth/config utilities plus a generic x_api_request fallback ensure no obvious dead ends exist.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources