Kaiten MCP server: intent-level tools over the Kaiten API for AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"kaitencloud-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Kaiten MCP Server An [MCP](https://modelcontextprotocol.io) server that lets an AI agent (Claude, Cursor, Copilot, any MCP client) run Kaiten: onboard customers, provision instances, shape Licenses and entitlements, meter usage, target feature flags and ship releases — in Kaiten's own vocabulary, not in HTTP verbs. ```text "Which customers are close to a limit?" → kaiten_get_usage(min_percent=80) "Move Ninja Osaka to Premium and renew it for a → kaiten_update_instance(instance="ninja-osaka-prod", year" plan="premium", extend_license_days=365) "Give Starter 20 more menu items, without → kaiten_save_license(new_version_of="starter", touching existing customers" grants={"menu-items": 25}) "Why doesn't Sakura see the analytics dashboard?" → kaiten_evaluate_flags(instance="sakura-tokyo-prod") ``` ## Design The previous server turned every OpenAPI operation into a tool: 105 tools, one per endpoint, each asking the agent for UUIDs and full replacement bodies. This one exposes **31 tools**, each an intent, built on the rules in Kaiten's product vision for agent-readiness: - **Tools express an intent, not a CRUD mirror.** `kaiten_provision_instance` resolves a License family to its current version, finds the zone, creates the customer if asked and sets the license term; the agent never handles an id. `kaiten_get_customer` answers "how is this customer doing" in one call. - **Reads return slices, never the whole catalog.** Resources are projected onto the fields that carry meaning, named by slug, with usage already set against its limit (`used`, `limit`, `percent`, `state`). - **Writes merge, and report truthfully.** Only what an agent passes changes. Every write answers with a `status` — `created`, `updated`, `unchanged`, `recorded`, `rejected`, `preview` or `deleted` — and the exact `changes`, computed from what Kaiten holds afterwards. A call that changes no…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.