What this is

Klai Studio exposes a Model Context Protocol (MCP) server so MCP-capable developer tools (Cursor, Claude Desktop, etc.) can create and edit Klai Studio pages from outside the Klai Studio app.

The key unlock is that this can be combined with domain-native tools (for example the Gene AI FileMaker Plugin) to enable near agentic, full-stack workflows, while keeping Klai as the system of record for the artifacts.

This is primarily used to let a developer stay in their IDE or assistant client while still operating directly on Klai Studio content.

Last updated: 2026-07-31

High-level architecture

  1. MCP client (Cursor, Claude Desktop, other MCP-capable tool)
  2. Klai Studio MCP server
  3. Klai Studio backend

Operational overview

Developer setup (Cursor + Claude Desktop)

This section documents how to wire MCP clients to the Klai Studio MCP server locally.

<aside> 🔐

Secrets and environment scoping

Klai Studio MCP settings showing the MCP client selector and Fetch MCP configuration button

Klai Studio MCP settings showing the MCP client selector and Fetch MCP configuration button

In Klai Studio, open the environment’s MCP settings, select your MCP client, then click Fetch MCP configuration.

Exact server configs may be sensitive. For current config values, see internal references and request access from Charles.

Cursor