Klai Studio exposes a Model Context Protocol (MCP) server so MCP-capable developer tools (Cursor, Claude, Codex, and others) can work on Klai Studio from outside the app.
There are two ways to connectV2 is the intended way to connect and is currently in beta. V1 (API key) stays available during the transition, and V2 will be the only way to connect once beta ends. Today there are two options:
| V2 (beta) | V1 (transitional) | |
|---|---|---|
| Credential | Your Klai sign-in | App API key in the config |
| Scope | Your account: orgs, apps, environments, servers | One app, one environment |
| Page and component edits | The app you connected | The app and environment you connected |
| Status | Intended default, will be the only way after beta | Available until beta ends |
The key unlock is that either connection can be combined with domain-native tools (for example the Genie FileMaker Plugin) to enable near agentic, full-stack workflows, while keeping Klai as the system of record for the artifacts.
Last updated: 2026-10-11
<aside> ✨
Beta. The sign-in connection is in beta. App API key connections keep working exactly as they do today.
</aside>
Copy it from Account → AI Integrations. Pick Generic, Cursor, Claude, or Codex, then Copy configuration. Paste that snippet into the agent’s MCP settings. When the agent asks, sign in on that host and approve the connection. It shows up in the agent’s list as Klai Studio.
Sign out of Klai Studio to disconnect agents that are already connected. Each one has to be approved again.