apifable and openmcp
These are complements: apifable helps developers explore and understand OpenAPI specs to determine which endpoints they need, while openmcp then automatically generates an MCP server exposing only those selected tools.
About apifable
ycs77/apifable
MCP server that helps AI agents explore OpenAPI specs, search endpoints, and generate TypeScript types.
Implements MCP tools for structured API exploration—`list_endpoints_by_tag`, `search_endpoints`, and `get_endpoint`—with fuzzy search fallback and automatic schema reference resolution. Supports both local OpenAPI files and remote URLs with header-based authentication, using a config-driven approach where specs can be fetched and refreshed independently from git-tracked configuration. Generates self-contained TypeScript types from schemas or endpoint request/response structures for direct use in frontend integration code.
About openmcp
getdatanaut/openmcp
Turn any openapi file into an mcp server, with just the tools you need.
Supports both OpenAPI-to-MCP conversion and stdio-based MCP server composition, allowing selective tool exposure through an `openmcp.json` config file. Implements stdio and SSE transports with direct integration into major chat clients (Cursor, Claude) via automated client configuration. Handles authentication management across multiple servers and enables mixing heterogeneous MCP sources—OpenAPI specs, stdio servers, and others—into a single unified MCP endpoint.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work