apifable and openapi-to-mcp

These two tools are complements: EvilFreelancer/openapi-to-mcp generates an MCP server from an OpenAPI spec, while ycs77/apifable helps AI agents interact with and explore such generated MCP servers.

apifable
51
Established
openapi-to-mcp
39
Emerging
Maintenance 13/25
Adoption 5/25
Maturity 20/25
Community 13/25
Maintenance 10/25
Adoption 5/25
Maturity 11/25
Community 13/25
Stars: 9
Forks: 2
Downloads: —
Commits (30d): 0
Language: TypeScript
License: MIT
Stars: 9
Forks: 2
Downloads: —
Commits (30d): 0
Language: TypeScript
License: MIT
No risk flags
No Package No Dependents

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-to-mcp

EvilFreelancer/openapi-to-mcp

Turns any OpenAPI/Swagger API into an MCP server. One MCP tool per endpoint, Streamable HTTP - for AI clients calling your REST API.

Related comparisons

apifable and openapi-mcp-generator apifable and mcp-openapi-schema-explorer apifable and openapi2mcptools apifable and sufetch apifable and openmcp apifable and openapi-directory-mcp

Scores updated daily from GitHub, PyPI, and npm data. How scores work