home / mcp / unbundle openapi mcp server
MCP to unbundle Large OpenAPI Spec
Configuration
View docs{
"mcpServers": {
"auto-browse-unbundle_openapi_mcp": {
"command": "npx",
"args": [
"@auto-browse/unbundle-openapi-mcp@latest"
]
}
}
}You run an MCP server that can split and extract endpoints from OpenAPI specifications, enabling you to manipulate API definitions programmatically from your MCP clients. This makes it easy to manage large OpenAPI files by unbundling them into smaller pieces or pulling only the endpoints you need into a new file for focused workflows.
You communicate with the server from an MCP client by starting the local stdio-driven MCP process and issuing tool commands that the server executes. The server is designed to listen on standard input/output, so you don’t need a network connection for MCP requests. You can use this server to split an OpenAPI document into multiple files or to extract specific endpoints into a new bundled OpenAPI file.
Prerequisites you need before installation:
- Node.js (LTS version recommended, such as v18 or v20)
- npm (comes with Node.js)
Install locally for the latest version and run via the CLI. The simplest approach uses a temporary execution with npx so you always get the most up-to-date release.
npx -y @smithery/cli install @auto-browse/unbundle_openapi_mcp --client claudeRun the MCP server with the latest packaged CLI. This starts the server in stdio mode so your MCP client can send requests over standard input/output.
npx @auto-browse/unbundle-openapi-mcp@latestIf you prefer a global installation (not generally recommended), you can install and run the CLI directly.
npm install -g @auto-browse/unbundle-openapi-mcp
"""Then run using: unbundle-openapi-mcp"""Set up the MCP client to reference the stdio-based server so the client can send tool requests. The server runs via a local CLI invocation and accepts tool calls such as split_openapi and extract_openapi_endpoints.
split_openapi: Unbundles an OpenAPI definition into multiple files based on its structure. Then you can work with smaller pieces of the API definition.
extract_openapi_endpoints: Extracts specific endpoints from a large OpenAPI file and creates a new bundled OpenAPI file containing only those endpoints and their referenced components.
Executes a command to unbundle an OpenAPI file into multiple smaller files based on its structure.
Extracts selected endpoints from a large OpenAPI file and bundles a smaller, focused OpenAPI document containing those endpoints and their components.