Sezzlee OpenAPI
Expose any OpenAPI document to agents as a search-first tool catalogue
- Pricing
- Open source
- Platforms
- CLI, self-hosted
- Runs
- Locally
- Version
- 1.0.0
- Listing updated
- 2 days ago
About Sezzlee OpenAPI
Sezzlee OpenAPI is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.
Instead of publishing one tool per endpoint, this server gives an agent four generic tools: search_tools, load_tool, invoke_tool and read_result. The agent searches the catalogue, loads the schema of the operation it wants, then invokes it. It works from a Swagger 2.0 or OpenAPI 3.0 to 3.2 document and calls your remote backend with fetch, attaching a credential it resolves itself.
It is the standalone sibling of Sezzlee's NestJS SDK, which runs inside your backend and replays calls through your existing auth pipeline. Because this server cannot see inside the backend, a host that cannot edit its spec can declare tool names, selection, families and argument curation in the config. Endpoints that funnel many capabilities through one route can be split into separate tools.
A JSON config file named by SEZZLEE_OPENAPI_CONFIG is required, and misconfiguration stops the process with exit code 2. Version 1.0.0 runs over stdio, with a streamable HTTP option in the config.
Install
Run in a terminal
claude mcp add openapi --env SEZZLEE_OPENAPI_CONFIG='<SEZZLEE_OPENAPI_CONFIG>' -- npx -y @sezzlee/openapi-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"openapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@sezzlee/openapi-mcp"
],
"env": {
"SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
}
}
}
}Configuration
SEZZLEE_OPENAPI_CONFIGPath to the server config fileRequired
Tools this server provides (4)
Taken from the project documentation; the running server may differ.
- search_tools
- Search the operation catalogue
- load_tool
- Load an operation's schema
- invoke_tool
- Call an operation on the backend
- read_result
- Read a stored result
What it does
- Search-first catalogue
- Agents search and load operations instead of seeing every tool at once.
- OpenAPI ingestion
- Reads Swagger 2.0 and OpenAPI 3.0 to 3.2 documents.
- Operation selection
- Opt operations in or out through config.
- Curated tools
- Rename tools and curate arguments with x-sezzlee extensions.
- Family splitting
- Split one multiplexed endpoint into separate tools.
- Validated config
- A zod schema rejects unknown keys and stops on errors.
Good for
- Give an agent access to an existing REST API without writing tools
- Limit which API operations an agent can call
- Wrap a legacy dispatch endpoint as named tools
- Test an OpenAPI spec as an agent-facing catalogue
Pricing
Open source
Open source npm package; licence not published
Prices change. Check docs.sezzlee.app before you buy.
Sezzlee OpenAPI FAQ
How is it run?
With npx -y @sezzlee/openapi-mcp and a config file path in SEZZLEE_OPENAPI_CONFIG.
Which spec versions work?
Swagger 2.0 and OpenAPI 3.0 to 3.2.
How does it differ from the NestJS SDK?
The SDK runs inside your backend and reuses its auth; this server calls the backend over the network.
What tools does it expose?
search_tools, load_tool, invoke_tool and read_result.
Is Sezzlee OpenAPI free?
Yes. Sezzlee OpenAPI is open source, so you can use and self-host it for free.
How do I add Sezzlee OpenAPI to Claude Code?
Run this command in your terminal: claude mcp add openapi --env SEZZLEE_OPENAPI_CONFIG='<SEZZLEE_OPENAPI_CONFIG>' -- npx -y @sezzlee/openapi-mcp
What are the best alternatives to Sezzlee OpenAPI?
The closest alternatives to Sezzlee OpenAPI are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to Sezzlee OpenAPI

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Ouroboros
MCP serverSpec-first layer that pins requirements and verifies results of AI coding agent work
Runs locally- Open source
- 6.4K GitHub stars
- Developer tools