Live on Product Hunt Intraface launched today. Less steering, more vacations. See the launch
Start for free

Connect Kiro to Intraface

Add an intraface entry with the url https://app.intraface.cc/mcp to ~/.kiro/settings/mcp.json for every workspace, or .kiro/settings/mcp.json for one. Save, and Kiro opens your browser; sign in on app.intraface.cc and click Allow. The Kiro IDE and the Kiro CLI both read the same file.

Part of Integrations: how to connect each coding agent to a shared Intraface board.

Set it up

  1. Add Intraface to ~/.kiro/settings/mcp.json, or .kiro/settings/mcp.json for one workspace. Save it.

    {
      "mcpServers": {
        "intraface": {
          "url": "https://app.intraface.cc/mcp"
        }
      }
    }

    The Kiro IDE and the Kiro CLI read the same file.

  2. Sign in and click Allow when your browser opens. The server appears in Kiro’s MCP panel.

  3. Give Kiro a board link and let it work.

    Read <board link> and follow its collab.md.

    It pulls the board, edits it on your machine and publishes a new version.

Option A: the MCP server in mcp.json

Kiro reads MCP servers from two files. ~/.kiro/settings/mcp.json applies to every workspace, and .kiro/settings/mcp.json applies to the folder you have open. When both name the same server, the workspace file wins. The Kiro IDE and the Kiro CLI share these files, so one entry covers both.

{
  "mcpServers": {
    "intraface": {
      "url": "https://app.intraface.cc/mcp"
    }
  }
}

Save it and Kiro connects. Your browser opens on app.intraface.cc; sign in, check the three permissions (read boards, write boards, write comments) and click Allow. The server then appears in Kiro's MCP panel with its tools listed.

Which file to pick: the user file if you move between projects, the workspace file if one repository works on one board. A workspace entry holds no secret, so it can go into git and every teammate signs in as themselves.

What works once you're connected

Point Kiro at a board: "Read and follow its collab.md." That file holds the board's house rules and design language. Kiro pulls the files, edits them in your project and publishes against the version it pulled. It can list the comments people pinned to the page, answer them and mark them resolved.

Several agents can publish to one board without stepping on each other. Publishes go in one at a time. If a teammate changed the same file first, Kiro pulls the new version and redoes its edit.

Troubleshooting

  • A prompt before every tool. List read tools in autoApprove, for example ["list_boards", "get_board", "pull_board"], and keep publish prompting. disabledTools hides tools you never want Kiro to call.
  • The workspace entry seems ignored, or the user one does. Both files merge and the workspace wins. Give each entry the same name only if you want the override.
  • Kiro asks you to sign in again after a long break. Click Re-authenticate next to the server in Kiro's MCP panel, then Allow once more.
  • Signing out. Revoke the agent in the Intraface app under Settings, then Agents.

FAQ

Should Intraface go in the user or workspace mcp.json in Kiro?
Use ~/.kiro/settings/mcp.json if you work on boards from many projects. Use .kiro/settings/mcp.json when one repository works on one board; it overrides a user entry with the same name.
Does the Kiro CLI sign in to Intraface the same way as the IDE?
Yes. Both read the same mcp.json files and both open your browser for the sign-in. Sign in on app.intraface.cc, click Allow, and you're connected.

Stop sending HTMLover Slack.

Create an account in a minute, connect your coding agent, and make your first board.