get-api-catalog
Get the API catalog, the catalog contains metadata about all openapi specifications, their operations and schemas
LABSCO SUMMARY
A large specification stops being something you paste into context.
The catalog carries the metadata, so an assistant searches for the operation it needs and loads that one alone — by operationId, or by the path and method read off a log line. When the files on disk change, refreshing the catalog is the entire update procedure.
What it is
A catalog over the OpenAPI specifications in a directory: metadata about every spec, its operations and its schemas, with search and targeted loads on top.
What you get
- A catalog holding metadata for every specification in the directory, its operations and its schemas
- Operations searched across all specifications at once, or narrowed to one by specId
- Schemas searched the same way, across specifications or within one
- A single operation loaded by operationId, or by path and method when that is what you have in front of you
- A schema loaded by name
- The catalog refreshed after the specs on disk change
Requirements
A directory of OpenAPI specification files, and npx on your PATH. No account and no key.
Setup effort
One command — npx -y @reapi/mcp-openapi@latest --dir ./specs
USE CASES
01
Writing a call against an API you do not know
Search the operations across every spec in the directory for what you are trying to do, then load that one operation in full — parameters, responses and all — instead of putting the whole document in context.
02
Working out what a request body must contain
Schemas are searchable in their own right, so the shape a payload has to take can be found and loaded by name without reading the operation that uses it.
03
Identifying the endpoint behind a path in a log
You have a method and a path from a trace or an error, not an operationId. That is the lookup this takes directly, which turns a log line into the documented operation.
04
Keeping the assistant current after a spec changes
Rebuild the catalog from the files on disk and read back what it now holds, so a regenerated specification is picked up without restarting anything.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
load-api-operation-by-operationId
Load an operation by operationId
load-api-operation-by-path-and-method
Load an operation by path and method
load-api-schema-by-schemaName
Load a schema by schemaName
refresh-api-catalog
Refresh the API catalog
search-api-operations
Search for operations across specifications
search-api-schemas
Search for schemas across specifications
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-openapi": {
"command": "npx",
"args": [
"-y",
"@reapi/mcp-openapi@latest",
"--dir",
"./specs"
]
}
}
}npx
TERMINAL
npx -y @reapi/mcp-openapi@latest --dir ./specs
