Your OpenAPI spec, a real MCP server you can trust.
Point klaridian at an OpenAPI or Swagger spec and it writes a stateless Model Context Protocol server, with OpenTelemetry, analytics, and tool curation already in place. The output is plain code you can read before it touches a single credential.
Curation, not a tool dump
Filter by tag, path, or operationId so the agent sees the handful of tools it needs instead of your entire API. Tool bloat is the thing people complain about most with generated MCP servers, and this is the fix.
Observability comes wired
OpenTelemetry tracing and product-analytics events are written into the server at generation time, as readable source you own rather than a black-box dependency.
TypeScript or Python
One spec, either runtime. Same tools, same annotations, same traces. Pick whichever you'd rather deploy.
You can read every line
Plain output on the official MCP SDK. Before you hand it production credentials, you can see exactly what each tool call does.
Handles huge specs
Code-mode collapses hundreds of operations into a typed client and two tools, so a giant API doesn't blow up the agent's context window.
Ships where you deploy
Get a Dockerfile, a Cloudflare Worker, or a Fly.io app. klaridian writes the config and the platform's own CLI takes it from there.
No black-box generator in the middle
klaridian parses and maps your OpenAPI spec itself, built on the standard swagger-parser library. The mapping is checked against real specs from Stripe, GitHub, and Kubernetes, so what comes out of your spec is predictable.
Install
One CLI, available on npm, PyPI, and Homebrew. The PyPI and Homebrew builds are prebuilt native binaries for macOS, Linux, and Windows, so you don't need Node.js installed.
$ npx klaridian generate --spec ./api.yaml --out ./server # Node.js · run once, nothing installed — recommended