de en es ja ko ru zh

Unbundle OpenAPI Specs MCP

Name: Unbundle OpenAPI Specs MCP
Author: gurvinder-dhillon

by gurvinder-dhillon

Overview Schema Related Servers Score Discussions

JavaScript

Hybrid

OpenAPI MCP 서버 번들 해제

대장간 배지

이 프로젝트는 OpenAPI 사양 파일을 여러 파일로 분할하거나 특정 엔드포인트를 새 파일로 추출하는 도구를 갖춘 모델 컨텍스트 프로토콜(MCP) 서버를 제공합니다. 이를 통해 MCP 클라이언트(예: AI 비서)가 OpenAPI 사양을 프로그래밍 방식으로 조작할 수 있습니다.

필수 조건

Node.js(LTS 버전 권장, 예: v18 또는 v20)
npm(Node.js와 함께 제공)

Related MCP server: openapi-mcp-proxy

용법

Smithery를 통해 설치

Smithery를 통해 Claude Desktop용 Unbundle OpenAPI MCP Server를 자동으로 설치하려면:

지엑스피1

이 서버를 사용하는 가장 쉬운 방법은 npx 이용하는 것입니다. 이를 통해 글로벌 설치가 필요 없이 항상 최신 버전을 사용할 수 있습니다.

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

또는 전역적으로 설치할 수 있습니다(일반적으로 권장하지는 않음):

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

서버가 시작되어 표준 입력/출력(stdio)에서 MCP 요청을 수신합니다.

클라이언트 구성

VS Code, Cline, Cursor 또는 Claude Desktop과 같은 MCP 클라이언트에서 이 서버를 사용하려면 해당 설정 파일에 구성을 추가하세요. 권장되는 방법은 npx 입니다.

VS 코드 / 클라인 / 커서

Ctrl+Shift+P > Preferences: Open User Settings (JSON) 를 통해 접근 가능한 사용자 settings.json 이나 작업 공간 루트의 .vscode/mcp.json 파일에 다음을 추가합니다.

// 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
}

클로드 데스크탑

claude_desktop_config.json 파일에 다음을 추가하세요.

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

구성을 추가한 후 변경 사항을 적용하려면 클라이언트 애플리케이션을 다시 시작하세요.

MCP 도구 제공

`split_openapi`

설명: redocly split 명령을 실행하여 OpenAPI 정의 파일을 구조에 따라 여러 개의 작은 파일로 분리합니다.

인수:

apiPath (문자열, 필수): 입력 OpenAPI 정의 파일(예: openapi.yaml )의 절대 경로입니다.
outputDir (문자열, 필수): 분할된 출력 파일을 저장할 디렉터리의 절대 경로입니다. 이 디렉터리가 없으면 자동으로 생성됩니다.

보고:

성공 시: redocly split 명령의 표준 출력을 포함한 텍스트 메시지(일반적으로 확인 메시지).
실패 시: 명령 실행 시 표준 오류 또는 예외 세부 정보가 포함된 오류 메시지로, isError: true 로 표시됩니다.

예시 사용(개념적 MCP 요청):

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

`extract_openapi_endpoints`

설명: 대용량 OpenAPI 정의 파일에서 특정 엔드포인트를 추출하여 해당 엔드포인트와 참조되는 구성 요소만 포함하는 더 작은 새 OpenAPI 파일을 생성합니다. 원본 파일을 분할하고, 지정된 경로만 유지하도록 구조를 수정한 후, 결과를 번들링하여 이를 구현합니다.

인수:

inputApiPath (문자열, 필수): 대용량 입력 OpenAPI 정의 파일의 절대 경로입니다.
endpointsToKeep (문자열 배열, 필수): 최종 출력에 포함할 정확한 엔드포인트 경로(문자열) 목록입니다(예: ["/api", "/api/projects/{id}{.format}"] ). 원본 사양에서 찾을 수 없는 경로는 무시됩니다.
outputApiPath (문자열, 필수): 최종적으로 더 작은 크기의 OpenAPI 번들 파일이 저장될 절대 경로입니다. 디렉터리가 없으면 자동으로 생성됩니다.

보고:

성공 시: 생성된 파일의 경로와 redocly bundle 명령의 표준 출력을 나타내는 텍스트 메시지입니다.
실패 시: 실패한 단계(분할, 수정, 번들)에 대한 세부 정보가 포함된 오류 메시지. isError: true 로 표시됩니다.

예시 사용(개념적 MCP 요청):

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

참고: 이 서버는 내부적으로 npx @redocly/cli@latest 사용하여 기본 split 및 bundle 명령을 실행합니다. npx @redocly/cli 가져오려면 인터넷 연결이 필요할 수 있습니다(캐시되지 않은 경우). extract_openapi_endpoints 프로세스 중에 임시 파일이 생성되고 자동으로 정리됩니다.

개발

소스에서 서버에 기여하거나 실행하려면:

복제: 이 저장소를 복제합니다.
탐색: cd unbundle_openapi_mcp
종속성 설치: npm install
빌드: npm run build (TypeScript를 dist/ 로 컴파일)
실행: npm start ( dist/ 에 있는 컴파일된 코드를 사용하여 서버를 시작합니다)

Available Tools

2 tools

extract_openapi_endpointsD

ParametersJSON Schema

Name	Required	Description
`endpointsToKeep`	Yes	List of exact endpoint paths to keep (e.g., ['/users', '/users/{id}']).
`inputApiPath`	Yes	Absolute path to the large input OpenAPI definition file.
`outputApiPath`	Yes	Absolute path where the final, smaller bundled OpenAPI file should be saved.

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

split_openapiD

ParametersJSON Schema

Name	Required	Description	Default
`apiPath`	Yes	Absolute path to the input OpenAPI definition file.
`outputDir`	Yes	Absolute path to the directory for split output files.

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesv1.0.0Aug 15, 2025
- First observedextract_openapi_endpoints
- First observedsplit_openapi

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0

Disambiguation4/5

The two tools have clearly distinct purposes: 'extract_openapi_endpoints' likely retrieves endpoints from an OpenAPI spec, while 'split_openapi' probably divides a spec into parts. There is no overlap in functionality, though the lack of descriptions leaves some room for minor uncertainty about exact differences.

Naming Consistency5/5

Both tools follow a consistent snake_case naming pattern with a verb_noun structure ('extract_endpoints', 'split_openapi'). The naming is predictable and aligned, making it easy to understand the action and target for each tool.

Tool Count2/5

With only two tools, the server feels thin for its purpose of unbundling OpenAPI specs. This limited set may not cover essential operations like validation, merging, or transformation, leaving obvious gaps in functionality for a domain that typically requires more comprehensive handling.

Completeness2/5

The tool surface is severely incomplete for unbundling OpenAPI specs. Missing are tools for tasks such as validating specs, merging split parts, converting formats, or handling errors. Agents will likely encounter dead ends when trying to perform common workflows in this domain.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Apis Guru A
io.github.pipeworx-io
APIs.guru MCP — keyless directory of 2,500+ public APIs and their OpenAPI specs.
Developer Tools Documentation Access
352
pAIchart MCP HubOAuth
app.paichart
MCP Hub: AI service discovery, per-user OAuth, and multi-service workflow orchestration
App Automation Cloud Platforms Data Platforms
22
Jsonschema A
io.github.pipeworx-io
JSON Schema validation MCP.
Developer Tools Testing & QA Tools API Testing
322
llm-orchestration-agent-2
ai.getvda
MCP-Native LLM Orchestration Agent
Agent Orchestration AI & Machine Learning
1

Related MCP Servers

OpenAPI Schema Explorer
Developer Tools
kadykov
A
license
Not graded
quality
A
maintenance
MCP server providing token-efficient access to OpenAPI/Swagger specs via MCP Resources for client-side exploration.
Updated 7 days ago (2026-08-31 21:45 UTC)
234
76
MIT
openapi-mcp-proxy
API Testing Documentation Access Developer Tools
nyudenkov
A
license
A
quality
D
maintenance
An MCP server that provides tools for exploring large OpenAPI schemas without loading entire schemas into LLM context. Perfect for discovering and analyzing endpoints, data models, and API structure efficiently.
Updated a year ago (2025-10-05 14:20 UTC)
9
14
MIT
mcpgate
Developer Tools API Testing
MicaelJarniac
A
license
Not graded
quality
C
maintenance
A stateless gateway that turns any OpenAPI spec into MCP tools on the fly.
Updated 3 months ago (2026-06-04 17:10 UTC)
1
MIT
swagger-api-mcp-server
API Testing Developer Tools
NekoTarou
A
license
A
quality
C
maintenance
Parses Swagger 2.0 and OpenAPI 3.x specifications, exposing API endpoints, schemas, and authentication through MCP tools with local caching to reduce token usage.
Updated 7 months ago (2026-02-11 01:59 UTC)
11
27
1
MIT

Appeared in Searches

TDX API MCP (Model Context Protocol) Server

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gurvinder-dhillon/unbundle_openapi_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

OpenAPI MCP 서버 번들 해제

필수 조건

용법

Smithery를 통해 설치

클라이언트 구성

VS 코드 / 클라인 / 커서

클로드 데스크탑

MCP 도구 제공

split_openapi

extract_openapi_endpoints

개발

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

OpenAPI Schema Explorer

openapi-mcp-proxy

mcpgate

swagger-api-mcp-server

Appeared in Searches

Latest Blog Posts

MCP directory API

`split_openapi`

`extract_openapi_endpoints`