mcp-openapi and openapi-to-mcp

One tool generates an MCP server from an OpenAPI specification, while the other is an OpenAPI specification for an MCP server, suggesting they are complementary tools in the MCP ecosystem, potentially with one creating a server that conforms to the other's specification.

mcp-openapi
42
Emerging
openapi-to-mcp
39
Emerging
Maintenance 0/25
Adoption 9/25
Maturity 16/25
Community 17/25
Maintenance 10/25
Adoption 5/25
Maturity 11/25
Community 13/25
Stars: 81
Forks: 15
Downloads:
Commits (30d): 0
Language: TypeScript
License: MIT
Stars: 9
Forks: 2
Downloads:
Commits (30d): 0
Language: TypeScript
License: MIT
Stale 6m No Package No Dependents
No Package No Dependents

About mcp-openapi

ReAPI-com/mcp-openapi

OpenAPI specification MCP server.

This project helps software developers integrate their existing OpenAPI specifications directly into LLM-powered IDEs like Cursor. It takes multiple OpenAPI files (JSON or YAML) as input and makes all your API operations and schemas understandable by AI code assistants, allowing for intelligent code completion and API integration. It's for developers working with large language model tools in their daily coding tasks.

API development software development developer tools IDE integration LLM-assisted coding

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.

This project helps developers integrate their existing REST APIs with AI clients that use the Model Context Protocol (MCP). It takes an OpenAPI/Swagger specification as input and automatically generates a dedicated MCP tool for each API operation. The output is an MCP server that translates AI client requests into standard HTTP calls to your backend API, making your API accessible to AI agents without manual integration.

API-integration AI-tools developer-workflow backend-development

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