Unbundle Openapi MCP Server

If you already use Unbundle Openapi MCP, the unbundle openapi mcp mcp server is the piece that lets your assistant work with it directly. MCP server for splitting and extracting parts of OpenAPI specifications.

What the server does

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.

Installation

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• split_openapi — The split_openapi tool exposed by this server
• extract_openapi_endpoints — The extract_openapi_endpoints tool exposed by this server

Credentials and setup notes

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

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Unbundle Openapi MCP's toolset — split_openapi, extract_openapi_endpoints — is a fair guide to whether it matches your workflow. It is maintained by auto-browse; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Unbundle Openapi MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.