# klaridian

> Generate a stateless, instrumented Model Context Protocol (MCP) server from your OpenAPI or Swagger spec — in TypeScript or Python, with OpenTelemetry and product-analytics observability and tool curation wired in.

klaridian is an MIT-licensed CLI. Point it at an OpenAPI (or Swagger 2.0) spec and it emits a stateless MCP server built on the official MCP SDK, with observability and tool curation already wired in.

## Docs

- [Getting Started](https://klaridian.dev/docs): What klaridian is, how it fits together, and where to go next.
- [Code-mode architecture](https://klaridian.dev/docs/how-to/code-mode): For large APIs—a typed client and two tools instead of one tool per operation.
- [Configuration file](https://klaridian.dev/docs/how-to/config-file): Set default flag values for klaridian generate in a file you check in.
- [Curating the tool surface](https://klaridian.dev/docs/how-to/curation): Control which OpenAPI operations become MCP tools.
- [Deploy](https://klaridian.dev/docs/how-to/deploy): Emit deploy artifacts for a generated server with klaridian deploy.
- [Onboarding wizard](https://klaridian.dev/docs/how-to/init): Use klaridian init to scaffold a klaridian.config.json before your first generate.
- [Installation](https://klaridian.dev/docs/how-to/installation): Install the klaridian CLI from npm, PyPI, or Homebrew, or download a prebuilt binary.
- [JSON output for agents](https://klaridian.dev/docs/how-to/json-output): Drive klaridian from an agent or script with --json, structured results, and stable error codes.
- [Licensing](https://klaridian.dev/docs/how-to/licensing): Every generated server ships with a real license, by default.
- [Publishing to the MCP Registry](https://klaridian.dev/docs/how-to/mcp-registry): Give your server a reverse-DNS name for the official MCP Registry.
- [OAuth 2.1](https://klaridian.dev/docs/how-to/oauth): Protect a remote server with an external identity provider.
- [Amplitude](https://klaridian.dev/docs/how-to/plugins/amplitude): See which tools agents actually use, in Amplitude.
- [Mixpanel](https://klaridian.dev/docs/how-to/plugins/mixpanel): See which tools agents actually use, in Mixpanel.
- [OpenTelemetry](https://klaridian.dev/docs/how-to/plugins/otel): Trace every tool call without writing instrumentation code.
- [PostHog](https://klaridian.dev/docs/how-to/plugins/posthog): See which tools agents actually use.
- [Running the server](https://klaridian.dev/docs/how-to/running-the-server): The fastest path to a running server, and the lifecycle behind it.
- [Target language](https://klaridian.dev/docs/how-to/target-language): Generate the server in TypeScript (default) or Python.
- [Transports](https://klaridian.dev/docs/how-to/transports): stdio vs. streamable-http, and when to use each.
- [CLI reference](https://klaridian.dev/docs/reference/cli-reference): Every flag for the klaridian CLI, generated from the real commands.

## Full text

- [Full documentation, concatenated](https://klaridian.dev/llms-full.txt): every doc page as plain text, for whole-corpus ingestion.

## Optional

- [Changelog](https://klaridian.dev/changelog): release notes, newest first.
- [Source on GitHub](https://github.com/klaridian/klaridian): MIT-licensed generator.