A Model Context Protocol server that exposes OpenAPI schema information to Large Language Models
Most AI and media services work still happens through a UI a human drives. MCP Openapi Schema MCP server moves it into the conversation instead. A Model Context Protocol server that exposes OpenAPI schema information to Large Language Models.
A Model Context Protocol (MCP) server that exposes OpenAPI schema information to Large Language Models (LLMs) like Claude. This server allows an LLM to explore and understand OpenAPI specifications through a set of specialized tools.
The server publishes 10 tools. What each one is for:
list-endpoints — Lists all API paths and their HTTP methods with summaries in a nested object structureget-endpoint — Gets detailed information about a specific endpoint including parameters and responsesget-request-body — Gets the request body schema for a specific endpoint and methodget-response-schema — Gets the response schema for a specific endpoint, method, and status codeget-path-parameters — Gets the parameters for a specific pathlist-components — Lists all schema components (schemas, responses, parameters, etc.)get-component — Gets detailed definition for a specific componentlist-security-schemes — Lists all available security schemesget-examples — Gets examples for a specific component or endpointsearch-schema — Searches across paths, operations, and schemasThe server ships on npm as mcp-openapi-schema, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Openapi Schema's toolset — list-endpoints, get-endpoint, get-request-body and 7 more — is a fair guide to whether it matches your workflow. It is maintained by hannesj; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list-endpoints | Lists all API paths and their HTTP methods with summaries in a nested object structure |
| get-endpoint | Gets detailed information about a specific endpoint including parameters and responses |
| get-request-body | Gets the request body schema for a specific endpoint and method |
| get-response-schema | Gets the response schema for a specific endpoint, method, and status code |
| get-path-parameters | Gets the parameters for a specific path |
| list-components | Lists all schema components (schemas, responses, parameters, etc.) |
| get-component | Gets detailed definition for a specific component |
| list-security-schemes | Lists all available security schemes |
| get-examples | Gets examples for a specific component or endpoint |
| search-schema | Searches across paths, operations, and schemas |
{
"mcpServers": {
"openapi-schema": {
"command": "npx",
"args": ["-y", "mcp-openapi-schema"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.