Krafa
Dashboard
Dashboard
Getting Started
QuickstartHow it works
The Canvas
Canvas overviewPasting and node typesOrganizing a boardCommand menuKeyboard shortcuts
Design Taste
Taste memoriesExtractionConflictsCurating your profile
Using with Agents
Connecting an agentMCP server referenceClaude CodeCursorCodexKiroAntigravity
Imports
Imports overviewXPinterestDribbble
Reference
Plans and billingHTTP APISelf-hostingFAQ
KrafaAll systems operational
Using with Agents

Kiro

Connect Krafa to Kiro so its agent builds against your curated design taste.

Kiro supports remote MCP servers natively and reloads them on save, so setup is a file edit with no restart.

Setup

Get your token

Press ⌘K → Connect AI Agent in the board you want to use, and export the token:

export KRAFA_TOKEN="krafa_YOUR_TOKEN"

Add the server

Open the command palette with ⇧⌘P and run Kiro: Open user MCP config (JSON), or Kiro: Open workspace MCP config (JSON) to scope it to one project.

~/.kiro/settings/mcp.json
{
  "mcpServers": {
    "krafa-taste": {
      "url": "https://app.krafa.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer ${KRAFA_TOKEN}"
      },
      "disabled": false,
      "autoApprove": ["get_taste_profile", "list_memories", "get_exemplars"]
    }
  }
}

url is the only required key; Kiro infers the transport from it. User and workspace configs are merged, with the workspace winning on a name collision.

Tip

All three Krafa tools are read-only, so auto-approving them is safe and saves you a confirmation prompt on every design question. "autoApprove": ["*"] does the same thing more broadly.

Verify

Save the file. Kiro reconnects automatically, with no restart. The Kiro panel shows krafa-taste with its three tools.

Make it automatic

Add a steering rule so the agent consults the profile on its own:

.kiro/steering/design-taste.md
Before writing or modifying any UI, call `get_taste_profile` from the
krafa-taste MCP server and follow it. For visual work, also call
`get_exemplars`. The profile is the design spec for this project.

A worked session

Kiro's spec-driven flow benefits from the profile early. Ask for a spec first:

Write a spec for the notifications panel, and include the design constraints from my taste profile.

The design constraints land in the spec document, which means every task generated from it inherits them, rather than each implementation step re-deciding what the UI should look like.

Troubleshooting

SymptomCause
Server doesn't appearCheck the JSON parses; Kiro skips malformed configs
invalid tokenKRAFA_TOKEN isn't set in Kiro's environment, or the token was rotated
A tool prompt on every callAdd the tool names to autoApprove
Empty profileThe board has no memories yet

On this page

SetupGet your tokenAdd the serverVerifyMake it automaticA worked sessionTroubleshooting