Libraries
Three pieces of tooling ship with the platform today, and they serve different people.
Who can use it: the Python SDK and the Katonic MCP Server need an API key, like the REST API, and does what the key's scopes allow. The Katonic CLI is for the team that runs the cluster and needs access to it, not a product role.
Katonic MCP Server
The Katonic MCP Server exposes platform capabilities as tools over the Model Context Protocol, so that an MCP client such as a desktop assistant, a coding agent or an agent you write can search knowledge, run agents, start evaluations and read analytics on your behalf. It runs inside your tenant and authenticates with the same kapi_ key as the REST API; a tool may do what the key's scopes allow. Start with Katonic MCP Server.
The Katonic CLI
The katonic-admin command verifies and applies air-gap bundles and carries catalog, pricing and telemetry updates for a self-hosted installation. It is for the team that runs the cluster, not for calling the public API. See The Katonic CLI.
The Python SDK
katonic-sdk is the platform's Python client: KatonicClient wraps the public API with one async method per call, and the package ships the katonic command. Install it with pip install "katonic-sdk>=7" on Python 3.11 or newer; this site documents the version published on PyPI, 7.0.18. Start with The Python SDK, then SDK methods and the katonic command and Use the SDK in a workspace.
For the OpenAI-compatible routes you can also point an OpenAI client library at https://<your tenant host>/public/v1; Use an OpenAI client library shows how.