# Sezzlee OpenAPI

> Sezzlee OpenAPI is an open-source MCP server for developer tools. Expose any OpenAPI document to agents as a search-first tool catalogue. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, self-hosted
- **Website:** https://docs.sezzlee.app/docs/http-catalog/quickstart
- **Repository:** https://github.com/sezzlee/mcp/tree/HEAD/packages/servers/openapi-mcp
- **MCP Registry name:** io.github.sezzlee/openapi
- **Categories:** developer tools
- **Listing updated:** 2026-11-15

## About

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.

## Features

- **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

## Install

### Claude Code (Terminal)

```sh
claude mcp add openapi --env SEZZLEE_OPENAPI_CONFIG='<SEZZLEE_OPENAPI_CONFIG>' -- npx -y @sezzlee/openapi-mcp
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "openapi": {
      "command": "npx",
      "args": [
        "-y",
        "@sezzlee/openapi-mcp"
      ],
      "env": {
        "SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
      }
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "openapi": {
      "command": "npx",
      "args": [
        "-y",
        "@sezzlee/openapi-mcp"
      ],
      "env": {
        "SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
      }
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "openapi": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sezzlee/openapi-mcp"
      ],
      "env": {
        "SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
      }
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "openapi": {
      "command": "npx",
      "args": [
        "-y",
        "@sezzlee/openapi-mcp"
      ],
      "env": {
        "SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
      }
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "openapi": {
      "command": "npx",
      "args": [
        "-y",
        "@sezzlee/openapi-mcp"
      ],
      "env": {
        "SEZZLEE_OPENAPI_CONFIG": "<SEZZLEE_OPENAPI_CONFIG>"
      }
    }
  }
}
```

## Tools

- `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

## 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

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.
- [Claude Code Ultimate Guide](https://ai-powered.com/mcp/claude-code-ultimate-guide): Claude Code Ultimate Guide is an open-source MCP server for ai models and llm tooling.
- [Concord MCP](https://ai-powered.com/mcp/concord-mcp): Concord MCP is a freemium MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/sezzlee-openapi
