MCP server
by auto-browse
Split OpenAPI specification files into focused, manageable parts while preserving references for better documentation an
Breaks down large OpenAPI specification files into smaller, focused files or extracts specific endpoints while maintaining all necessary component references.
OpenAPI Unbundler is a community-built MCP server published by auto-browse that provides AI assistants with tools and capabilities via the Model Context Protocol. Split OpenAPI specification files into focused, manageable parts while preserving references for better documentation an It is categorized under developer tools. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
You can install OpenAPI Unbundler in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
Apache-2.0
OpenAPI Unbundler is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We evaluated OpenAPI Unbundler against two servers with overlapping tools; this profile had the clearer scope statement.
Strong directory entry: OpenAPI Unbundler surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend OpenAPI Unbundler for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We evaluated OpenAPI Unbundler against two servers with overlapping tools; this profile had the clearer scope statement.
OpenAPI Unbundler has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
OpenAPI Unbundler is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, OpenAPI Unbundler benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
We wired OpenAPI Unbundler into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We evaluated OpenAPI Unbundler against two servers with overlapping tools; this profile had the clearer scope statement.
OpenAPI Unbundler is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 33
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.
To install Unbundle OpenAPI MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @auto-browse/unbundle_openapi_mcp --client claude
The easiest way to use this server is via npx, which ensures you are always using the latest version without needing a global installation.
npx @auto-browse/unbundle-openapi-mcp@latest
Alternatively, you can install it globally (not generally recommended):
npm install -g @auto-browse/unbundle-openapi-mcp
# Then run using: unbundle-openapi-mcp
The server will start and listen for MCP requests on standard input/output (stdio).
To use this server with MCP clients like VS Code, Cline, Cursor, or Claude Desktop, add its configuration to the respective settings file. The recommended approach uses npx.
Add the following to your User settings.json (accessible via Ctrl+Shift+P > Preferences: Open User Settings (JSON)) or to a .vscode/mcp.json file in your workspace root.
// 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 your claude_desktop_config.json file.
{
"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.
split_openapiDescription: Executes the redocly split command to unbundle an OpenAPI definition file into multiple smaller files based on its structure.
Arguments:
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.Returns:
redocly split command (usually a confirmation message).isError: true.Example Usage (Conceptual MCP Request):
{
"tool_name": "split_openapi",
"arguments": {
"apiPath": "/path/to/your/openapi.yaml",
"outputDir": "/path/to/output/directory"
}
}
extract_openapi_endpointsDescription: 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.
Arguments:
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.Returns:
redocly bundle command.isError: true.Example Usage (Conceptual MCP Request):
{
"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 uses npx @redocly/cli@latest internally to execute the underlying split and bundle commands. An internet connection might be required for npx to fetch @redocly/cli if it's not cached. Temporary files are created during the extract_openapi_endpoints process and automatically cleaned up.
If you want to contribute or run the server from source :
cd unbundle_openapi_mcpnpm installnpm run build (compiles TypeScript to dist/)npm start (starts the server using the compiled code in dist/)Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.