apifable and openapi-directory-mcp
Both are MCP servers that interface with OpenAPI specifications, making them ecosystem siblings within the "openapi-mcp-generation" category.
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 openapi-directory-mcp
rawveg/openapi-directory-mcp
An MCP Server for APIs.guru remarkable Wikipedia for Web APIs. Providing tools, prompts and resources to help eliminate LLM Coding Agent hallucinations.
Exposes 3,000+ OpenAPI specifications via progressive discovery phases that reduce context usage by ~95%, enabling efficient API exploration without saturation. Built as an MCP server with 22 specialized tools, smart search ranking, and support for custom OpenAPI imports alongside the APIs.guru directory. Integrates directly with Claude Desktop, Claude Code, Cursor, and Windsurf via stdio transport, automatically exposing all prompts as slash commands.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work