Skip to main content
Glama
msegoviadev

api-mind

by msegoviadev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to api-mind

No user-submitted related servers found.

    Related Servers

    • openapi-mcp

      ceski23
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for loading and exploring OpenAPI/Swagger specifications, enabling AI assistants to dynamically browse API contracts by loading specs, searching endpoints, inspecting schemas, and retrieving operations.
      8 npm
      3
      MIT

    • OpenAPI MCP Server

      cloudwarriors-ai
      A
      license
      A
      quality
      D
      maintenance
      A generic MCP server that dynamically exposes any OpenAPI-documented REST API to LLMs by auto-discovering endpoints. It provides tools for exploring API capabilities and making authenticated requests directly through natural language interfaces.
      2
      5 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.
      47 npm
      12
      Apache 2.0
    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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: list_apis for API overview, list_endpoints for endpoint discovery, get_endpoint_schema for endpoint contract details, and get_call_context for runtime execution details. The descriptions explicitly clarify when to use each, preventing overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_* and get_*), with verbs clearly indicating read-only discovery actions. The naming is predictable and uniform.

    Tool Count5/5

    Four tools is well-scoped for a server focused on API discovery and context provision. Each tool covers a necessary step in the workflow from discovering APIs to preparing API calls, without redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of API exploration: discovering APIs, discovering endpoints, understanding schema/auth, and obtaining runtime context for actual calls. There are no obvious gaps for the server's stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources