list-endpointsLABSCO SUMMARY
One spec per server, ten ways to ask about it.
The split is finer than most: request body, response schema, path parameters and security schemes are separate calls, so a model answering "what does this POST need" pulls a few hundred lines rather than the file. Each instance is bound to the schema on its command line, which keeps answers unambiguous and means adding an API means adding a server.
What it is
A Node server that loads a single OpenAPI schema — JSON or YAML — named on the command line, and answers questions about it in YAML, which is easier for a model to read than raw JSON schema.
What you get
- list-endpoints for the paths and operations, get-endpoint for one of them
- get-request-body and get-response-schema for a single operation's shapes
- get-path-parameters for what a path expects
- list-components and get-component for the reusable definitions
- get-examples for the examples carried in the spec
- list-security-schemes for how the API authenticates
- search-schema across the whole specification
Requirements
Node. Run with npx -y mcp-openapi-schema and the path to the schema file as its argument; with no argument it uses openapi.yaml in the current directory. One server instance per API, so several APIs means several entries in your client config.
Setup effort
One command — npx -y mcp-openapi-schema
USE CASES
01
Working out what a call expects before writing it
Read the request body and the path parameters for that one operation.
02
Parsing a response you have never seen
Fetch the response schema and the examples the spec ships alongside it.
03
Finding the endpoint that does what you need
List the endpoints, or search the whole specification when you only know a word from the description.
04
Getting authentication right the first time
Read the security schemes rather than inferring them from a sample request.
05
Chasing a $ref you keep hitting
List the components and pull the definition the operation points at.
10 tools
Listed in project docs. Your client may show a different list.
get-endpointget-request-bodyget-response-schemaget-path-parameterslist-componentsget-componentlist-security-schemesget-examplessearch-schemaBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
npx on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-openapi-schemaMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"OpenAPI Schema": {
"command": "npx",
"args": [
"-y",
"mcp-openapi-schema",
"<YOUR_PATH_TO_OPENAPI>"
]
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add openapi-schema npx -y mcp-openapi-schema
