Unbundle Openapi Specs

A server for splitting and extracting parts of OpenAPI specifications using Redocly CLI.

This project provides a Model Context Protocol (MCP) server with tools to split OpenAPI specification files into multiple files or extract specific endpoints into a new file. It allows an MCP client (like an AI assistant) to manipulate OpenAPI specifications programmatically.

- Node.js (LTS version recommended, e.g., v18 or v20)
- npm (comes with Node.js)

To install Unbundle OpenAPI MCP Server for Claude Desktop automatically viaSmithery:

npx -y @smithery/cli install @auto-browse/unbundle_openapi_mcp --client claude

npx @auto-browse/unbundle-openapi-mcp@latest

npm install -g @auto-browse/unbundle-openapi-mcp # Then run using: unbundle-openapi-mcp

// In settings.json: "mcp.servers": { "unbundle_openapi": { // You can choose any key name "command": "npx", "args": [ "@auto-browse/unbundle-openapi-mcp@latest" ] } // ... other servers can be added here }, // Or in .vscode/mcp.json (omit the top-level "mcp.servers"): { "unbundle_openapi": { // You can choose any key name "command": "npx", "args": [ "@auto-browse/unbundle-openapi-mcp@latest" ] } // ... other servers can be added here }

Add the following to yourclaude_desktop_config.jsonfile.

{ "mcpServers": { "unbundle_openapi": { // You can choose any key name "command": "npx", "args": ["@auto-browse/unbundle-openapi-mcp@latest"] } // ... other servers can be added here } }

After adding the configuration, restart your client application for the changes to take effect.

Description:Executes theredocly splitcommand to unbundle an OpenAPI definition file into multiple smaller files based on its structure.

- apiPath(string, required): The absolute path to the input OpenAPI definition file (e.g.,openapi.yaml).
- outputDir(string, required): The absolute path to the directory where the split output files should be saved. This directory will be created if it doesn't exist.

- On success: A text message containing the standard output from theredocly splitcommand (usually a confirmation message).
- On failure: An error message containing the standard error or exception details from the command execution, marked withisError: true.

{ "tool_name": "split_openapi", "arguments": { "apiPath": "/path/to/your/openapi.yaml", "outputDir": "/path/to/output/directory" } }

Description:Extracts specific endpoints from a large OpenAPI definition file and creates a new, smaller OpenAPI file containing only those endpoints and their referenced components. It achieves this by splitting the original file, modifying the structure to keep only specified paths, and then bundling the result.

- inputApiPath(string, required): The absolute path to the large input OpenAPI definition file.
- endpointsToKeep(array of strings, required): A list of the exact endpoint paths (strings) to include in the final output (e.g.,["/api", "/api/projects/{id}{.format}"]). Paths not found in the original spec will be ignored.
- outputApiPath(string, required): The absolute path where the final, smaller bundled OpenAPI file should be saved. The directory will be created if it doesn't exist.

- On success: A text message indicating the path of the created file and the standard output from theredocly bundlecommand.
- On failure: An error message containing details about the step that failed (split, modify, bundle), marked withisError: true.

{ "tool_name": "extract_openapi_endpoints", "arguments": { "inputApiPath": "/path/to/large-openapi.yaml", "endpointsToKeep": ["/users", "/users/{userId}/profile"], "outputApiPath": "/path/to/extracted-openapi.yaml" } }

Note:This server usesnpx @redocly/cli@latestinternally to execute the underlyingsplitandbundlecommands. An internet connection might be required fornpxto fetch@redocly/cliif it's not cached. Temporary files are created during theextract_openapi_endpointsprocess and automatically cleaned up.

If you want to contribute or run the server from source :
- Clone:Clone this repository.
- Navigate:cd unbundle_openapi_mcp
- Install Dependencies:npm install
- Build:npm run build(compiles TypeScript todist/)
- Run:npm start(starts the server using the compiled code indist/)

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Converts OpenAPI/Swagger specifications to Model Context Protocol (MCP) format, providing a modern Web UI and a backend service.

Explore and analyze OpenAPI specifications from local files or remote URLs.

A server that converts OpenAPI specifications into the Model Context Protocol (MCP).

Serves multiple OpenAPI specifications to enable LLM-powered IDE integrations.

MCP server for API documentation, supporting GraphQL, OpenAPI/Swagger, and gRPC from local files or remote URLs

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.

The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.

A server that dynamically creates MCP endpoints from any OpenAPI specification URL.

A TypeScript MCP server to access Apifox API data via Stdio.

Provides API documentation from Apifox projects as a data source for AI programming tools that support MCP.