Liquid vs Openapi Mcp Gateway

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
L
Liquid
ertad-family
🔗 Aggregators
O
🔗 Aggregators
SummaryConnect your agent to any HTTP API on the fly — discovers + maps any REST API once, then fetches typed data deterministically (no per-call LLM). Self-hosted MCP server (uvx --from 'liquid-api[mcp]' liquid-mcp); works with OpenAI/Gemini/Anthropic/local or any provider via LiteLLM. Open source (AGPL).Mount many OpenAPI specs (or your existing FastAPI app) as MCP servers in one process. Auto-promotes eligible GETs to MCP resources, exposes huge specs via three list/get/call meta-tools instead of N tool schemas, and ships per-user OAuth2 token relay with audience-bound tokens.
Quality signal25/100 (Emerging)23/100 (Emerging)
Install pathuvx · highnpx · low
Engagement 2 0 0 2 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView LiquidView Openapi Mcp Gateway
More alternatives to LiquidMore alternatives to Openapi Mcp GatewayAggregators category

Other servers like Liquid