Bir OpenAPI dokümanını, yapay zeka ajanlarının uzak bir backend üzerindeki API operasyonlarını keşfetmesi ve çalıştırması için arama odaklı bir araç kataloğu olarak sunar.
Ayrıca bilinen adı sezzlee/mcp, openapi, @sezzlee/openapi-mcp
- Yıldızlar
- 1
- Araçlar
- —
- İndirmeler, 30 gün
- —
- En son sürüm
- 1.0.0
- Son commit
- 13 Kas 2026
- Lisans
- MIT
Sezzlee OpenAPI MCP nedir?
Sezzlee OpenAPI bir MCP sunucusudur. Bir OpenAPI dokümanını, yapay zeka ajanlarının uzak bir backend üzerindeki API operasyonlarını keşfetmesi ve çalıştırması için arama odaklı bir araç kataloğu olarak sunar.
Özet, projenin README dosyasından oluşturuldu
Sezzlee OpenAPI MCP sunucusu hakkında
Sezzlee OpenAPI, mevcut bir OpenAPI dokümanını yapay zeka ajanları için aranabilir bir araç kataloğuna dönüştüren bir köprü görevi görür. Backend sürecine doğrudan gömülü bir SDK entegre etmeden, uzak backend operasyonlarını bir yapay zeka istemcisine açmak isteyen geliştiriciler için tasarlanmıştır. Sunucu, mevcut uç noktaları keşfetmek için yerel bir dosya yolundan veya uzak bir URL'den Swagger 2.0 veya OpenAPI 3.0–3.2 spesifikasyonlarını okur.
Kullanıcılar sunucuyla search_tools, load_tool, invoke_tool ve read_result gibi özel araçlar aracılığıyla etkileşime girer. Sunucu, stdio taşıma yöntemiyle veya streamable HTTP üzerinden çalışabilir. Uzak kurulumlar için, kimlik doğrulamayı yönetmek amacıyla OAuth korumalı kaynak tanımlayıcılarını ve RFC 8693 token exchange protokolünü destekler. Yapılandırma, SEZZLEE_OPENAPI_CONFIG ortam değişkeni ile belirtilen bir JSON dosyası üzerinden yönetilir; bu da araç isimleri, arama terimleri ve operasyon seçimi üzerinde hassas kontrol sağlar.
Neler yapabilirsiniz
- 1Uzak API'leri yapay zeka ajanlarına açınEntegre bir SDK'sı bulunmayan bir backend servisine, OpenAPI dokümanını kullanarak bir yapay zeka istemcisi bağlayın.
- 2Araç görünürlüğünü ve isimlendirmeyi yönetinHangi belirli API rotalarının ajana açılacağını yapılandırın ve varsayılan isimlerini geçersiz kılın.
- 3API dokümantasyon güncellemelerini otomatize edinBackend'deki değişiklikleri yansıtması için sunucunun OpenAPI kaynağını periyodik olarak yeniden okumasını sağlayın.
Projenin README dosyasından alınmıştır. Her kullanım durumu, oradaki bir alıntı ile kontrol edilir.
Sezzlee OpenAPI MCP nasıl yüklenir
Biçimler 10 Kas 2026 tarihinde doğrulandıCursor'a ekleGoose'a ekleSezzlee OpenAPI MCP'yi Claude Code içine yükleyin
$ claude mcp add --env 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' openapi -- npx -y @sezzlee/openapi-mcpSezzlee OpenAPI MCP'yi Cursor içine yükleyin
~/.cursor/mcp.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Sezzlee OpenAPI MCP'yi VS Code içine yükleyin
.vscode/mcp.json
{
"servers": {
"openapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Sezzlee OpenAPI MCP'yi VS Code CLI içine yükleyin
$ code --add-mcp '{"name":"openapi","type":"stdio","command":"npx","args":["-y","@sezzlee/openapi-mcp"],"env":{"SEZZLEE_OPENAPI_CONFIG":"<SEZZLEE_OPENAPI_CONFIG>"}}'Sezzlee OpenAPI MCP'yi Claude Desktop içine yükleyin
claude_desktop_config.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Sezzlee OpenAPI MCP'yi Codex içine yükleyin
$ codex mcp add openapi --env 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' -- npx -y @sezzlee/openapi-mcpSezzlee OpenAPI MCP'yi Codex config.toml içine yükleyin
~/.codex/config.toml
[mcp_servers.openapi] command = "npx" args = ["-y", "@sezzlee/openapi-mcp"] [mcp_servers.openapi.env] SEZZLEE_OPENAPI_CONFIG = "<SEZZLEE_OPENAPI_CONFIG>"
Sezzlee OpenAPI MCP'yi Gemini CLI içine yükleyin
$ gemini mcp add -s user -e 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' openapi npx -- -y @sezzlee/openapi-mcpSezzlee OpenAPI MCP'yi Gemini settings.json içine yükleyin
~/.gemini/settings.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Yapılandırma
SEZZLEE_OPENAPI_CONFIGGerekliPath to the server config file
| Ad | Açıklama | Sunucu |
|---|---|---|
| SEZZLEE_OPENAPI_CONFIG | Path to the server config file | Gerekli |
Otomatik kontroller
Çalıştırıldı 14 Kas 2026Tam rapor →Otomatik kontrollerimizden geçti. Bu bir güvenlik denetimi değildir: kodu okuyun ve sunucuya ihtiyaç duyduğu en dar erişimi verin. Kontroller nasıl çalışır
- Kaynak deposu bağlantılı ve erişilebilirsezzlee/mcp is public and reachablegithub.com/sezzlee/mcp ↗Geçti
- Paket, bu depoyu kaynağı olarak gösteriyor@sezzlee/openapi-mcp names sezzlee/mcp as sourcenpmjs.com/package/@sezzlee/openapi-mcp ↗Geçti
- Derleme kökeni (Sigstore onayı)Sigstore attestation for @sezzlee/openapi-mcpnpmjs.com/package/@sezzlee/openapi-mcp/v/1.0.0#provenance ↗Geçti
- Açık kaynak lisansı (OSI)MITspdx.org/licenses/MIT.html ↗Geçti
- Son bir yıl içinde commit veya sürüm mevcutLast commit or release 2026-11-09github.com/sezzlee/mcp ↗Geçti
- OpenSSF ScorecardKontrol edilmedi
- Paket adı popüler bir pakete yakın değilNo popular package one edit away from @sezzlee/openapi-mcpGeçti
- Pakette veya bağımlılıklarında kritik uyarı yok10 resolved dependencies checked; no critical advisoryosv.dev ↗Geçti
- Modele yönelik gizli talimat yok0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersGeçti
- Yıkıcı araçlar etiketlenmişKontrol edilmedi
- Uzak uç nokta MCP el sıkışmasına yanıt veriyorKontrol edilmedi
@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 soruları
Sezzlee OpenAPI MCP'yi Claude Code'a nasıl eklerim?
Terminalinizde claude mcp add --env 'SEZZLEE_OPENAPI_CONFIG=<SEZZLEE_OPENAPI_CONFIG>' openapi -- npx -y @sezzlee/openapi-mcp komutunu çalıştırın. Her projede kullanılabilir olması için --scope user ekleyin.
Sezzlee OpenAPI MCP'yi Cursor'a nasıl eklerim?
~/.cursor/mcp.json dosyasını açın ve yukarıdaki yükleme bölümünde gösterilen Cursor yapılandırmasını kullanarak sunucuyu mcpServers altına ekleyin.
Hangi taşıma yöntemleri destekleniyor?
Sunucu hem stdio hem de streamable HTTP taşıma yöntemlerini destekler.
Kaynak olarak yerel bir OpenAPI dosyası kullanabilir miyim?
Evet, kaynak ya yapılandırma dosyasına göre göreceli bir yerel dosya yolu ya da bir HTTP(S) URL'si olabilir.