over MCP

Connect your AI agent to Klyaksa

Klyaksa has its own MCP server. Connect it to Claude, ChatGPT, Grok, Cursor, VS Code, Codex or another agent — and the agent creates canvases and draws diagrams for you from a description, while you and your team edit them together in the browser.

The Klyaksa MCP address — the same for every way of connecting:

https://mcp.klyaksa.app/mcp

Transport — Streamable HTTP. Paste the address as is, with no trailing slash.

Klyaksa is free^* ^* For large teams, separate plans may appear in the future.

What the agent can do

the agent works on your behalf — with your access rights

Find its way around

Who you are, your workspaces, projects, folders and canvases, members and tags.

Draw

A whole diagram in one call: shapes, text, arrows bound to shapes. Elements from the built-in library and images.

Read the canvas

Find elements by text or by area, describe the scene, count elements, take a screenshot of the canvas, check the layout.

Edit

Move, resize, rotate and flip, align and distribute, group, lock, duplicate, change the layer order, use frames, delete.

Versions

Save a version, list and open versions, roll back to one of them.

Organise

Create, rename and move projects, folders and canvases; archive and restore projects and canvases; manage workspaces and tags.

Team

Invite people by email, add members, change roles, manage invitations.

Sharing

Create, change and revoke share links, see link stats and visitors.

The server deletes a project, canvas or workspace only when the agent explicitly confirms the deletion. API keys, password and email, ownership transfer and leaving a workspace or project are not available to agents — only in the Klyaksa interface.

Two ways to connect

Sign-in (OAuth) — the default

For apps and sites: Claude (the app and claude.ai), ChatGPT (the app and Codex), ChatGPT Classic, Grok (grok.com) and any other app that speaks MCP.

No key is needed: the app opens the Klyaksa sign-in itself, you allow access — and the agent is connected.

A connected app is listed in Klyaksa under AI Agents → Apps and sites → Connected applications; you can revoke it there.

Apps and sites →

API key — for CLI and editors

For agents with a config file — Claude Code, Codex, Cursor, Cline, VS Code, Kimi, Grok CLI. The key goes into the file and stays on your machine.

The agent sends the key in the X-Api-Key header.

Where to get it: in Klyaksa, the AI Agents button in the top bar → the CLI and editors tab.

CLI and editors →

Apps and sites: step by step

the steps are the same as in the AI Agents window of the app

Pick your app and we will show the steps. No key is needed — the app opens the Klyaksa sign-in itself.

Claude — the app and claude.ai

Settings → Connectors → Add custom connector.
Name it Klyaksa, address — the one above, with no trailing slash.
Scroll the form down and press Add.
Press Connect — a browser opens.
In the browser — Continue connecting.
Allow access on the Klyaksa screen.
Tick the checkbox, then let the browser open the Claude app — the dialog closes as soon as you press the button.
Done — the app says it is connected.
Open Settings → Capabilities → Allow network egress and set the domain list to All domains. Without it the agent cannot download images or renders: files are served from a separate domain, and the MCP address alone is not enough. Would rather not open everything — add the storage domain from the file links the agent receives.
Check it in a chat: “draw a trolleybus in Klyaksa”.

The connection is kept in your Claude account — the same connector shows up on claude.ai as well. You can disconnect it from either place.

ChatGPT — the app and Codex

Settings → Plugins, the gear icon.
The MCPs tab → Add server.
Name, the address above, transport — Streamable HTTP.
Press Authenticate.
Allow access on the Klyaksa screen.
The Authenticate button is gone — the connection went through.
Type /mcp in the chat — Klyaksa should be on the list.
Allow actions without asking every time, or the agent asks at every step.
Confirm full access.
Ask it to draw something.

This list is shared with the Codex CLI and the editor extension — connecting here connects them too.

ChatGPT Classic — the old app and chatgpt.com

Check that yours is Classic: it says so at the top of the window. We recommend moving to the new app.
Open the settings.
Turn on Developer mode.
Open Plugins and press “+”.
Fill in the form, sign-in method — OAuth.
Press Sign in with klyaksa.
Allow access on the Klyaksa screen.
Check the connection card.
Ask something in a chat.

The connection is kept in your account and shows up on chatgpt.com. This is a DIFFERENT place from the MCP list in the new app: a server added there does not appear in ordinary chats, and a connector from the chats does not appear in Codex.

Grok — the grok.com site

Open Plugins — at the bottom of the left menu.
Press New Connector.
Pick Custom — the first item on the list.
Fill in the name and the address above.
Allow access on the Klyaksa screen.
Done — the connector is on the list.
Check it in a chat.

The connection is kept in your Grok account, not on your computer — it is disconnected in the same place, under Plugins.

Another app

Find the Connectors, Plugins or MCP section in the app.
Add a server and paste the address shown above.
If it asks for a connection type — pick Streamable HTTP.
If it asks how to sign in — pick OAuth or “sign in”. No key is needed.
The app opens the Klyaksa sign-in — sign in and allow access.
Go back to the app and ask it something about your projects.

The app then appears in Klyaksa under AI Agents → Apps and sites → Connected applications, under the name it gave itself. If it is not there — the sign-in did not finish, try again.

CLI and editors: step by step

Get a key and a ready config

Open Klyaksa and press AI Agents in the top bar.
Go to the CLI and editors tab.
Enter a key label (for example, cursor) and press CREATE KEY.
Copy your new key now — it won’t be shown again.
Under Configuration, pick your agent in the list and press COPY: the config already contains the address and your new key.
Paste it into the agent’s config file (the paths are below) and restart the agent if it does not pick up the change by itself.

Lost the key? Create a new one and revoke the old one with the REVOKE button — agents using the old key will lose access.

Below the key is shown as <YOUR_API_KEY> — the app inserts your real key into the config it copies.

Claude Code

File: .mcp.json

{
  "mcpServers": {
    "klyaksa": {
      "type": "http",
      "url": "https://mcp.klyaksa.app/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Codex

File: ~/.codex/config.toml

[mcp_servers.klyaksa]
url = "https://mcp.klyaksa.app/mcp"

[mcp_servers.klyaksa.http_headers]
X-Api-Key = "<YOUR_API_KEY>"

Codex also shares its server list with the ChatGPT app: if you connected Klyaksa in ChatGPT by signing in, Codex already has it (see ChatGPT).

Cursor

File: ~/.cursor/mcp.json

{
  "mcpServers": {
    "klyaksa": {
      "url": "https://mcp.klyaksa.app/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Cline

File: ~/.cline/mcp.json

{
  "mcpServers": {
    "klyaksa": {
      "type": "streamableHttp",
      "url": "https://mcp.klyaksa.app/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

VS Code (Copilot)

File: .vscode/mcp.json

{
  "servers": {
    "klyaksa": {
      "type": "http",
      "url": "https://mcp.klyaksa.app/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Kimi Code CLI

File: ~/.kimi-code/mcp.json

{
  "mcpServers": {
    "klyaksa": {
      "transport": "http",
      "url": "https://mcp.klyaksa.app/mcp",
      "headers": {
        "X-Api-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Grok Build CLI

File: ~/.grok/config.toml

[mcp_servers.klyaksa]
url = "https://mcp.klyaksa.app/mcp"
enabled = true

[mcp_servers.klyaksa.headers]
X-Api-Key = "<YOUR_API_KEY>"

Generic (mcp-remote)

File: mcp.json

{
  "mcpServers": {
    "klyaksa": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.klyaksa.app/mcp",
        "--header",
        "X-Api-Key: <YOUR_API_KEY>"
      ]
    }
  }
}

For clients that support only local (stdio) servers — the npx mcp-remote bridge. The named agents above support the remote MCP natively.

Questions

Is Klyaksa free?

Yes, Klyaksa is free — connecting agents included. For large teams, separate plans may appear in the future. See also the Terms of Use.

Where is my data stored?

Data is processed on servers in Europe. All of your content remains yours. Details are in the Privacy Policy.

Can I undo what the agent did?

Yes, with versions. Before a big task, save a version — in the editor or by asking the agent to do it — and roll back to it in one click if you don’t like the result. Before a rollback the current state is saved automatically, so the rollback can be undone too. The agent’s edits do not save versions by themselves.

What can the agent see?

Exactly what you can: it works on your behalf, sees the workspaces and projects available to you and can do what your role allows. Account settings and API keys are not available to it.

How do I disconnect an agent?

An app connected by sign-in: AI Agents → Apps and sites → Connected applications → REVOKE. It will not be able to renew access; a token it already has keeps working for up to 15 more minutes. An agent with a key: revoke the key on the CLI and editors tab. In Claude and Grok the connector can also be removed in their own settings.

Which agents are supported?

Any MCP client that can connect to a remote server. This page has step-by-step instructions for the ones the Klyaksa app has instructions for; for anything else, see Another app or Generic (mcp-remote).

leave your own blot

Open your own board — no sign-up.

Open a board →

No email, no password. If you have been here before, your own board opens.