Skip to main content
Glama

Related Servers

Alternatives to liquid-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to connect to any API by loading OpenAPI, GraphQL, gRPC, or SOAP specs, with a built-in catalog of 2500+ public APIs, supporting secure execution, response filtering, chaining, and parallel calls.
      36 PyPI
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      The API layer for AI agents. World's biggest API index with 22,000+ APIs and growing. Agents discover and call APIs at runtime with semantic search, structured metadata, and 18 Direct Call APIs including AI providers.
      14
      349 npm
      8
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to autonomously discover and call a marketplace of 100+ APIs, including web search, image generation, and more, with automatic payments and refunds.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to discover, search, and call any REST API described by an OpenAPI or Swagger document. Supports multiple API endpoints with authentication and parameter handling.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to fetch and digest content from 30+ platforms (Twitter, YouTube, Reddit, etc.) via a unified API. Supports multi-format output, transcription, and direct Obsidian sync.
      18
      BSD 2-Clause "Simplified"

    TDQS

    A4.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct lifecycle phase: discover previews an API, connect persists an adapter, list_adapters shows existing adapters, estimate preflights, fetch pulls records, and query filters/aggregates. The descriptions explicitly cross-reference when to use each tool, so there is minimal ambiguity between fetch/query and connect/discover.

    Naming Consistency4/5

    All tools share a consistent 'liquid_' prefix, lowercase snake_case, and action-oriented verbs. Minor inconsistency: liquid_list_adapters uses the verb_noun form while the others are bare verbs like connect, fetch, and query, but the pattern is still predictable and easy to follow.

    Tool Count5/5

    Six tools is a well-scoped size for this server. Each tool earns its place and together they cover the adapter lifecycle from discovery through connection, listing, estimation, and data access without redundant or filler tools.

    Completeness4/5

    The workflow discover → connect → list → fetch/query/estimate covers the core read-focused API integration domain thoroughly, with no dead ends. The only notable gap is adapter lifecycle management: there is no update or delete operation for modifying target_model or removing stored credentials.

    Maintenance

    ActivityInactive
    ResponsivenessSlow