Unbundle Openapi Specs

What is Unbundle Openapi Specs?

Unbundle Openapi Specs is a Model Context Protocol (MCP) server that provides tools to split OpenAPI specification files into multiple files or extract specific endpoints into a new file. It is designed for developers or AI assistants who need to manipulate OpenAPI definitions programmatically.

How to use Unbundle Openapi Specs?

The server can be launched via npx without installation: npx @auto-browse/unbundle-openapi-mcp@latest. It communicates over stdio. To use it with an MCP client (e.g., VS Code, Cline, Cursor, Claude Desktop), add the configuration to the client’s settings file (e.g., settings.json or claude_desktop_config.json), using npx as the command and the package as the argument.

Key features of Unbundle Openapi Specs

• Splits an OpenAPI definition into multiple files using redocly split.
• Extracts specific endpoints and creates a smaller OpenAPI file.
• Automatically cleans up temporary files created during extraction.
• Runs via npx for easy, up‑to‑date usage.
• Integrates with MCP clients through standard configuration.

Use cases of Unbundle Openapi Specs

• Splitting a monolithic OpenAPI spec into per‑path or per‑component files.
• Creating a minimal OpenAPI file from a large spec, keeping only needed endpoints.
• Automating API documentation or code generation workflows that require partial specs.
• Enabling AI assistants to programmatically restructure OpenAPI definitions.

FAQ from Unbundle Openapi Specs

What dependencies does Unbundle Openapi Specs require?

It requires Node.js (LTS v18 or v20 recommended) and npm. It uses npx @redocly/cli@latest internally, so an internet connection may be needed to fetch the CLI if not cached.

How do I configure Unbundle Openapi Specs with an MCP client?

Add a server entry to your client’s settings (e.g., mcp.servers in VS Code’s settings.json) with command npx and arguments ["@auto-browse/unbundle-openapi-mcp@latest"].

What tools does the server provide?

Two tools: split_openapi (splits a file into multiple files) and extract_openapi_endpoints (extracts specified endpoints into a new file).

Does the server store any data or require authentication?

No. The server works with local file paths provided at runtime; it does not persist data or require authentication.

What transport does the server use?

It communicates over standard input/output (stdio).