craaft

Craaft MCP Server

Model Context Protocol server for Craaft - lets AI assistants read and write your Kanban boards.

Deployed as an HTTP service. Each request authenticates via the caller's Authorization: Bearer header - either a cra_* personal access token (same ones used by the Craaft REST API) or a cro_* OAuth access token minted by signing in through the connector flow below.

Two-factor sign-in on a craaft account doesn't affect either kind of token. Account security settings (password, two-factor, API keys) are browser-only on the platform, so no tool changes them.

Deploy

cd mcp

gcloud run deploy craaft-mcp \ --source . \ --region us-central1 \ --allow-unauthenticated \ --set-env-vars CRAAFT_BASE_URL=https://craaft.io,MCP_PUBLIC_URL=https://ai.craaft.io/mcp

The PORT env var is set automatically by Cloud Run.

Connect from Claude (OAuth)

With MCP_PUBLIC_URL set, the server is an OAuth 2.1 protected resource: no token needs to be copied by hand.

craaft is in the Claude directory: connect it from there and skip to step 3. Or add it as a custom connector:

1. In Claude Desktop or claude.ai, go to Settings > Connectors > Add custom connector.
2. Paste https://ai.craaft.io/mcp.
3. Sign in to craaft, choose Read and write or Read only, and approve the connection.

With read-only access, tools that only read (list_projects, get_board, search_cards and the like) work, and every tool that changes something fails with this token is read-only; this request needs a token with read and write access. The same goes for a cra_ key created as read only.

You can also connect it to Chosen boards only. Tools then see just those boards: other boards are not found, and list_projects and search_cards leave them out. create_project, import_board, list_members, list_invitations and the other member tools fail with this token is limited to some boards; this request needs a token for all boards. To change an app's access or boards, connect it again and choose again.

To revoke access later, go to Craaft Settings > Connected apps.

Configure (Claude Desktop, cra_ token)

1. Sign in to Craaft → Settings → API keys → create a token
2. Add to ~/.config/claude/claude_desktop_config.json:

{

"mcpServers": { "craaft": { "url": "https://craaft-mcp-xxxxx.a.run.app/mcp", "headers": { "Authorization": "Bearer cra_your_token_here" } } } }

MCP registry

craaft is listed in the official MCP registry as io.craaft/mcp, described by server.json. craaft.io proves it owns the io.craaft namespace by serving a public key at https://craaft.io/.well-known/mcp-registry-auth (platform repo, internal/server/mcpregistry.go). The matching private key is not in this repo.

To publish a change, raise version in server.json (a published version can't be changed or republished), then:

PRIVATE_KEY="$(openssl pkey -in ~/.config/craaft/mcp-registry-key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"

mcp-publisher login http --domain craaft.io --private-key "$PRIVATE_KEY" mcp-publisher publish

Install mcp-publisher from the registry's releases.

Tools

The three bulk_* tools are all-or-nothing: one bad item rolls the whole batch back and the error names the offending index, so a failed call never leaves a partially applied board. They send no notification emails (activity events and realtime updates still fire), and each call spends one rate-limit token against a 60-burst budget - which is why they should be preferred over looping the single-card tools.

Endpoints

Env vars

Attachments

This server runs remotely, so it cannot read the caller's filesystem: upload_attachment takes the contents inline (content_text for text, content_base64 for binary), not a path.

download_attachment returns text-ish content types as readable text and everything else base64-encoded. Attachments can be up to 25 MiB, which no conversation wants inline, so it refuses anything over max_bytes (default 256 KiB) and reports the real size instead. Text is truncated rather than refused, since truncated text is still readable; truncated base64 is not, so binary over the limit is skipped entirely.

Attachments are a paid feature. On a Free workspace the upload returns 402 and the error names the current plan. Check canUploadAttachments on the project first - it reflects the board's workspace plan, not the caller's.

Import

preview_import and import_board take the same arguments: filename, the file inline (content_text or content_base64), and optionally source (trello, jira, asana, csv or craaft; detected when l