OpenAPI
This MCP server implementation provides a bridge to OpenAPI-specified services, enabling AI assistants to interact with any API that follows the OpenAPI standard. Developed by Ross Masters, it dynamically generates MCP tools from an OpenAPI specification URL, allowing for seamless integration with a wide range of RESTful APIs. Built with Python and leveraging libraries like FastAPI and openapi3-parser, the server focuses on flexibility and ease of use. It supports OpenAPI 3.0 and 3.1 specifications in both JSON and YAML formats. The implementation is particularly useful for scenarios requiring interaction with multiple APIs, rapid prototyping, or integration with existing OpenAPI-documented services.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- file-system
- Source
- PulseMCP
- Repository
- github.com/rmasters/mcp-openapi
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve OpenAPI from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.