extract_openapi_endpointsLABSCO SUMMARY
Neither tool talks to an API: this is a preparation step that shrinks a specification before a client or a model ever sees it.
The two calls answer different questions — split_openapi is about structure, writing the document out under outputDir, while extract_openapi_endpoints is about scope, keeping only what endpointsToKeep names. They are pure file work, which makes them safe to run repeatedly and easy to wire into a build step. The tool definitions arrive without descriptions, so apiPath, inputApiPath, outputApiPath, outputDir and endpointsToKeep are the whole of the contract you get to work from.
What it is
A two-tool file utility for OpenAPI documents: split_openapi writes a document out under a directory, extract_openapi_endpoints writes a copy containing only the endpoints you list.
What you get
- Splitting on disk: split_openapi reads the document at
apiPathand writes the split result underoutputDir. - Endpoint-level trimming: extract_openapi_endpoints reads
inputApiPath, keeps the endpoints named inendpointsToKeep, and writes the reduced document tooutputApiPath.
Requirements
No credentials are configured. Each call names its own paths, so you need the OpenAPI document somewhere the server can read it and a writable location for what it produces — outputDir for the split, outputApiPath for the extract.
Setup effort
One command — npx -y @auto-browse/unbundle-openapi-mcp@latest
USE CASES
01
Trimming a specification down to the endpoints you actually call
Name the endpoints worth keeping and write a smaller document, instead of handing over a specification that covers an entire product.
02
Breaking an oversized OpenAPI file into a directory you can navigate
Point it at the bundled document and let it write the split result out where the rest of your tooling can pick the pieces up.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
split_openapiBEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
- npx on PATH
- Node.js
CONTEXT COST
Light Standing cost
Rated by the size of the 2 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": {
"unbundle-openapi-mcp": {
"command": "npx",
"args": [
"-y",
"@auto-browse/unbundle-openapi-mcp@latest"
]
}
}
}npx
TERMINAL
npx -y @auto-browse/unbundle-openapi-mcp@latest
