OpenAPI 문서를 검색 중심의 도구 카탈로그로 변환하여, AI agent가 원격 백엔드의 API operation을 검색하고 호출할 수 있도록 지원합니다.
다른 이름 sezzlee/mcp, openapi, @sezzlee/openapi-mcp
- 스타
- 1
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 1.0.0
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- MIT
Sezzlee OpenAPI MCP란?
Sezzlee OpenAPI은(는) MCP server입니다. OpenAPI 문서를 검색 중심의 도구 카탈로그로 변환하여, AI agent가 원격 백엔드의 API operation을 검색하고 호출할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
Sezzlee OpenAPI MCP server 정보
Sezzlee OpenAPI는 기존 OpenAPI 문서를 AI agent를 위한 검색 가능한 도구 카탈로그로 변환하는 브릿지 역할을 합니다. 백엔드 프로세스에 SDK를 직접 통합하지 않고도 원격 백엔드 operation을 AI client에 노출해야 하는 개발자를 위해 설계되었습니다. 이 server는 로컬 파일 경로 또는 원격 URL에서 Swagger 2.0 또는 OpenAPI 3.0–3.2 사양을 읽어 사용 가능한 endpoint를 탐색합니다.
사용자는 search_tools, load_tool, invoke_tool, read_result를 포함한 특정 도구를 통해 server와 상호작용합니다. server는 stdio 전송 방식 또는 streamable HTTP를 통해 실행할 수 있습니다. 원격 설정의 경우, 인증 처리를 위해 OAuth protected-resource identifier 및 RFC 8693 token exchange를 지원합니다. 설정은 SEZZLEE_OPENAPI_CONFIG 환경 변수로 지정된 JSON 파일을 통해 관리하며, 도구 이름, 검색어 및 operation 선택에 대해 세밀한 제어가 가능합니다.
활용 사례
- 1원격 API를 AI agent에 노출OpenAPI 문서를 사용하여 통합 SDK가 없는 백엔드 서비스에 AI client를 연결합니다.
- 2도구 가시성 및 이름 관리agent에 노출할 특정 API route를 구성하고 기본 이름을 재정의합니다.
- 3API 문서 업데이트 자동화백엔드의 변경 사항을 반영할 수 있도록 OpenAPI 소스를 주기적으로 다시 읽도록 server를 설정합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Sezzlee OpenAPI MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Sezzlee OpenAPI MCP 설치
$ claude mcp add --env 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' openapi -- npx -y @sezzlee/openapi-mcpCursor에 Sezzlee OpenAPI MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}VS Code에 Sezzlee OpenAPI MCP 설치
.vscode/mcp.json
{
"servers": {
"openapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}VS Code CLI에 Sezzlee OpenAPI MCP 설치
$ code --add-mcp '{"name":"openapi","type":"stdio","command":"npx","args":["-y","@sezzlee/openapi-mcp"],"env":{"SEZZLEE_OPENAPI_CONFIG":"<SEZZLEE_OPENAPI_CONFIG>"}}'Claude Desktop에 Sezzlee OpenAPI MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Codex에 Sezzlee OpenAPI MCP 설치
$ codex mcp add openapi --env 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' -- npx -y @sezzlee/openapi-mcpCodex config.toml에 Sezzlee OpenAPI MCP 설치
~/.codex/config.toml
[mcp_servers.openapi] command = "npx" args = ["-y", "@sezzlee/openapi-mcp"] [mcp_servers.openapi.env] SEZZLEE_OPENAPI_CONFIG = "<SEZZLEE_OPENAPI_CONFIG>"
Gemini CLI에 Sezzlee OpenAPI MCP 설치
$ gemini mcp add -s user -e 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' openapi npx -- -y @sezzlee/openapi-mcpGemini settings.json에 Sezzlee OpenAPI MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}구성
SEZZLEE_OPENAPI_CONFIG필수Path to the server config file
| 이름 | 설명 | 유형 |
|---|---|---|
| SEZZLEE_OPENAPI_CONFIG | Path to the server config file | 필수 |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능sezzlee/mcp is public and reachablegithub.com/sezzlee/mcp ↗통과
- 패키지가 이 저장소를 소스로 명시@sezzlee/openapi-mcp names sezzlee/mcp as sourcenpmjs.com/package/@sezzlee/openapi-mcp ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for @sezzlee/openapi-mcpnpmjs.com/package/@sezzlee/openapi-mcp/v/1.0.0#provenance ↗통과
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-09github.com/sezzlee/mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @sezzlee/openapi-mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음10 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기@sezzlee/openapi-mcp
MCP server that exposes an OpenAPI (Swagger 2.0 / OpenAPI 3.0–3.2) document as sezzlee's
search-first tool catalog — search_tools, load_tool, invoke_tool, read_result — over a remote
backend, calling it with fetch.
Status:
1.0.0, stable. Install withnpm install -g @sezzlee/openapi-mcpor run it withnpx -y @sezzlee/openapi-mcp; the binary issezzlee-openapi.
How this differs from the embedded SDK
The NestJS SDK sits inside your backend process: it discovers endpoints from your own controllers/routes and replay each MCP call through your existing pipeline, so your authentication and authorization run exactly as they do today.
openapi-mcp is a separate service. It has no access to a backend's process or pipeline — it
reads the backend's OpenAPI document to learn what operations exist (the ingestion
rules), and calls the backend over the network for every
invocation, attaching a credential it resolves itself (how a credential is chosen and
written). This is the only path for a backend that has no
embedded SDK integrated into it.
Everything an embedded SDK declares in code, a document declares in one x-sezzlee extension per
operation, and a host that cannot edit the document declares under operations in this config:
selection, tool name, prefix, behaviour hints, argument curation, variants, families, search terms
and revisions (the x-sezzlee extension).
A backend that routes many capabilities through one endpoint (POST /Rest/InvokeDynamicMethod/{methodId})
lists them in that operation's x-sezzlee.family; each member becomes its own tool, with its own
name, description and body, and the dispatch key stays hidden.
Quick start
The server reads its configuration from the file named by SEZZLEE_OPENAPI_CONFIG. Build the
package first (this repository never runs @sezzlee/core's consumers against a stale dist):
pnpm turbo run build --filter=@sezzlee/openapi-mcp
A minimal config — a local document, opt-in selection so at least one operation is exposed,
default stdio transport:
{
"source": "./openapi.json",
"selection": { "default": "include" }
}
SEZZLEE_OPENAPI_CONFIG=/absolute/path/to/config.json node packages/servers/openapi-mcp/dist/cli.js
source is either a path (resolved relative to the config file's own directory) or an
http(s):// URL. On startup the server ingests the document, builds the catalog, prints a
one-line-per-diagnostic-code summary to stderr, and then serves stdio or listens for
streamable HTTP, depending on transport.kind.
A config that fails validation, or that names an environment variable that is not set, stops the
process with a message on stderr and exit code 2. A document that ingests with a fatal
diagnostic, or a catalog with a fatal diagnostic (name_collision, invalid_name,
ambiguous_selection, …), stops it with exit code 1.
Configuration
All keys below are read from the SEZZLEE_OPENAPI_CONFIG JSON file and validated with a zod
schema (src/platform/config.ts) that rejects unknown keys.
| Key | Type | Default | Notes |
|---|---|---|---|
transport.kind |
"stdio" | "http" |
"stdio" |
— |
transport.host |
string (http only) |
"127.0.0.1" |
Must stay loopback (127.0.0.1, ::1, localhost) unless tokenExchange is configured — see below |
transport.port |
int, 0–65535 (http only) |
8787 |
— |
transport.path |
string starting with / (http only) |
"/mcp" |
— |
transport.resource |
url (http only) |
required | The OAuth protected-resource identifier advertised at /.well-known/oauth-protected-resource |
transport.authorizationServers |
array of url, min 1 (http only) |
required | — |
transport.allowedHostnames |
array of string (http only) |
[] |
Extra Host header values accepted, on top of the localhost defaults |
tokenExchange |
object | not configured | RFC 8693 token exchange; required for an http transport to authenticate a caller (see Rules) |
tokenExchange.tokenEndpoint |
url | required | — |
tokenExchange.clientId |
string | required | — |
tokenExchange.clientSecret |
{ fromEnv: string } |
required | — |
tokenExchange.clientAuth |
"basic" | "post" |
"basic" |
client_secret_basic or client_secret_post |
tokenExchange.audience |
string | not sent | — |
tokenExchange.resource |
url | not sent | — |
tokenExchange.scope |
string | not sent | — |
tokenExchange.schemes |
array of string, min 1 | required | The security scheme names the exchanged token satisfies |
source |
string, non-empty | required | A local file path (relative to the config file) or an http(s):// URL to the OpenAPI document |
reload.intervalSeconds |
integer ≥ 10 | not set | Re-reads source this often, plus up to 10% jitter. Conditional on the last ETag/Last-Modified for an http(s) source; a body identical to the served one is ignored |
reload.onSignal |
boolean | true |
SIGHUP re-reads source. Without a reload block the document is read once at startup and SIGHUP keeps its default action |
baseUrl |
url | not set | Replaces the document's root servers |
serverVariables |
record<string, string> | not set | Overrides for the document's server variable defaults |
hoistPathPrefix |
string starting with / |
not set | A leading path segment moved from every route into the base URL |
outputSchema |
"document" | "omit" |
"document" |
omit for a backend whose responses do not match its document |
requestBodyRequired |
"document" | "always" |
"document" |
always treats an undeclared requestBody.required as true |
strict |
boolean | false |
Raises openapi_document_invalid from a warning to a fatal diagnostic |
selection.default |
"include" | "exclude" |
"exclude" |
Whether an operation is exposed when no rule matches it (opt-in by default) |
selection.rules |
array of { route?, method?, decision } |
[] |
route/method are matched the same way the embedded SDKs match a controller route |
operations |
record<operation key, x-sezzlee object> |
{} |
Laid over each operation's x-sezzlee field by field; a key that names no operation is fatal. A field here may not also be set through names, searchTerms or revision.operations |
names |
record<operation key, string> | {} |
Overrides a tool's name; the value must match ^[a-z][a-z0-9_]{0,255}$ |
revision.catalog |
integer ≥ 1 | not configured | Behaviour revision of every tool; comes before the document root's x-sezzlee revision |
revision.paths |
record<document path, integer ≥ 1> | {} |
Behaviour revision of every operation under that path item; comes before the path item's x-sezzlee revision |
revision.operations |
record<operation key, integer ≥ 1> | {} |
Behaviour revision of one operation; comes before its x-sezzlee revision. The levels add up rather than replacing one another |
credentials |
record<security scheme name, credential> | {} |
Either { "value": { "fromEnv": "..." } } or { "username": { "fromEnv": "..." }, "password": { "fromEnv": "..." } }; see credentials.md |
allowHosts |
array of string | [] |
Hosts a backend operation may be served from, beyond the document's own root server |
refHosts |
array of string | [] |
Hosts an external $ref may be fetched from, beyond the document's own host. Kept apart from allowHosts, so allowing a schema host never lets calls or credentials go there |
identityCookies |
array of string | [] |
Cookie names treated as identity carriers on top of the default deny-list (compared case-insensitively); they extend it and never replace it |
limits.timeoutMs |
positive int | 30000 |
Per-invocation deadline |
limits.maxResponseBytes |
positive int | 262144 |
The largest answer that reaches the agent; a larger success is stored for read_result while results.enabled holds, and refused otherwise |
limits.maxBufferedBytes |
positive int | 16777216 |
The largest backend body read, applied while the body streams; a larger one is refused unread |
results.enabled |
boolean | true |
Keeps over-budget successes in memory and publishes read_result; see result-reading.md |
results.lifetimeMs |
int ≥ 1000 | 600000 |
How long a stored result is kept |
results.maxCallerBytes |
positive int | 16777216 |
What one caller's stored results may hold; the oldest go first. A caller is the bearer token it authenticated with, or every loopback caller when there is no token exchange |
results.maxBytes |
positive int | 67108864 |
What all stored results may hold; at least results.maxCallerBytes |
limits.maxInlineFileBytes |
positive int | 1048576 |
— |
A credentials entry is keyed by the security scheme name it satisfies; a tokenExchange.schemes
entry marks that same scheme as satisfied by the exchanged token instead. credentials values are
never inlined — only a reference to an environment variable — so a config file can be committed
and shared.
Rules
- Only
src/net/fetch.tsreaches the network. It is the one place the host allowlist, the manual redirect handling and the byte cap are applied;src/transport/http.tsmay usenode:httponly to listen, never to call out. Redirects are never followed — a followed redirect could carry a request, and its credential, to a host the allowlist never approved. - Only
src/platform/files.tstouches the filesystem. A file the document references through an external$ref, or named bysource, is checked against the directory the document was read from on its realpath, so neither a../segment nor a symbolic link can escape it. - The caller's MCP token is never forwarded to the backend. Its audience is this server, not
the backend; forwarding it would bypass the backend's own audience check. On the
httptransport withtokenExchangeconfigured, the caller's token is exchanged (RFC 8693) for a backend-scoped token at the transport's bearer gate, and only the exchanged token reachesinvoke_tool. - An
httptransport withouttokenExchangeauthenticates no caller, so it may only bind a loopback host (127.0.0.1,::1,localhost); otherwise the operator's static credentials would be reachable from the network. ConfiguringtokenExchangeon thestdiotransport is likewise refused (token_exchange_requires_http) — there is no caller token onstdioto exchange. - A reload never widens egress.
reloadre-reads only the document, never the config, and the hosts the first catalog may call are the ceiling for every later one: a document whose servers move to a host outside it, from https to plain http, or that sends a credential to a plain-http origin that did not carry it before, is refused (widens_egress). A refused document, one with a fatal diagnostic, or one that cannot be read keeps the running catalog. A committed reload advances the catalog generation stamped on every meta-tool and sendstools/list_changed. A tool loaded before a reload answersunknown_toolif it is gone andtool_changedto a call pinned to its old version. - Visibility is not enforcement: an operation's
securitysays which credential a call needs, not which caller may make it, so the catalog reports every operation's identity asunknownunless its document sayssecurity: [].
Development
pnpm turbo run build --filter=@sezzlee/openapi-mcp
pnpm turbo run lint --filter=@sezzlee/openapi-mcp
pnpm turbo run check-types --filter=@sezzlee/openapi-mcp
pnpm turbo run test --filter=@sezzlee/openapi-mcp
Run these through Turbo, not pnpm --filter @sezzlee/openapi-mcp <task> — the bare filter skips
dependsOn: ["build"] and the test task would run against a stale dist.
test/ holds unit suites that need no environment variables, plus one gated suite:
acceptance.spec.ts— skipped unlessSEZZLEE_OPENAPI_ACCEPTANCE_DOCnames a path to a real backend's OpenAPI document. The document itself never enters the repository; the suite ingests it, builds a catalog, asserts there is no fatal diagnostic, and prints the diagnostic summary instead of pinning a snapshot that would copy that backend's surface into the tree.SEZZLEE_OPENAPI_ACCEPTANCE_DOCis declared in this package'sturbo.jsontesttask so Turbo passes it through.
Sezzlee OpenAPI MCP 질문
Sezzlee OpenAPI MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' openapi -- npx -y @sezzlee/openapi-mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Sezzlee OpenAPI MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
지원하는 전송 방식은 무엇인가요?
stdio 및 streamable HTTP 전송 방식을 모두 지원합니다.
로컬 OpenAPI 파일을 소스로 사용할 수 있나요?
네, 설정 파일 기준의 로컬 파일 경로 또는 HTTP(S) URL을 소스로 사용할 수 있습니다.