Connecting AI clients (MCP)

Cardscape exposes an MCP (Model Context Protocol) server, so you can let an external AI client — such as Claude — work on your real canvases. Through it a connected client can draw on canvases, read and place cards, and read and write documents and comments. It always acts as you and is limited to exactly what you can access.

What it is

The MCP server offers the same toolset the built-in canvas agent uses — see AI agent tools — made available to any MCP client you connect. Instead of chatting with the built-in agent inside the app, you point your own AI client at Cardscape and it operates on your canvases directly.

Create a personal token

You authenticate your client with a personal token created in the web app:

1. In the sidebar header, click the plug button to open the MCP tokens dialog.
2. Choose create a token.
3. The dialog shows the plaintext token (prefixed csmcp_) and a ready-to-paste connect snippet — exactly once. Copy them now.
4. Later, reopen the same dialog to list your tokens or revoke any you no longer need.

Keep your token secret

The token is shown only once and is never displayed again. Copy it before closing the dialog, store it somewhere safe, and treat it like a password. If you lose it, revoke it and create a new one.

Connect a client

Paste the snippet the app showed you into your AI client. It is typically a claude mcp add … command that points at the Cardscape MCP endpoint and includes your token.

The exact endpoint URL and command come from the snippet the app generates for you — copy it as shown rather than typing one by hand. Once added, your client discovers the Cardscape tools and can start working on your canvases.

Security

• The token acts as you and is scoped to your own access — a client can only reach the workspaces, boards, and canvases you can.
• Treat the token like a password: don't share it, commit it, or paste it anywhere public.
• If a token leaks, revoke it from the MCP tokens dialog and create a fresh one.