apifable and openapi2mcptools
One project is an MCP server that helps AI agents interact with OpenAPI specs, while the other provides tools for converting OpenAPI specifications into the MCP format, suggesting a complementary relationship where the latter prepares data for the former.
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 openapi2mcptools
2013xile/openapi2mcptools
OpenAPI specifications => MCP (Model Context Protocol) tools
This project helps developers quickly integrate existing OpenAPI specifications into MCP (Model Context Protocol) servers. It takes an OpenAPI specification as input and outputs a list of tools and a tool caller function, which can then be used to define and execute these tools within an MCP server. This is designed for software developers building applications that need to communicate with or expose services via the Model Context Protocol.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work