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

Connect Continue to Intraface

Create .continue/mcpServers/intraface.yaml with type streamable-http and the url https://app.intraface.cc/mcp. Switch the chat to agent mode, sign in on app.intraface.cc when your browser opens, and click Allow. For headless runs such as the cn CLI in CI, add an apiKey holding an Intraface token instead.

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

Set it up

  1. Create .continue/mcpServers/intraface.yaml at the top level of your workspace.

    name: Intraface
    version: 0.0.1
    schema: v1
    mcpServers:
      - name: intraface
        type: streamable-http
        url: https://app.intraface.cc/mcp
  2. Switch the chat to agent mode. Your browser opens on app.intraface.cc.

  3. Sign in and click Allow.

  4. Give Continue 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.

Overview

Continue only talks to MCP servers in agent mode. Whichever option you pick, switch the chat to agent mode before you look for the Intraface tools.

Option A: the MCP server with a browser sign-in

Give Intraface its own block file. Create .continue/mcpServers/ at the top level of your workspace and add intraface.yaml:

name: Intraface
version: 0.0.1
schema: v1
mcpServers:
  - name: intraface
    type: streamable-http
    url: https://app.intraface.cc/mcp

The same mcpServers entry also works inside your main Continue config. When Continue first connects, your browser opens on app.intraface.cc. Sign in and click Allow.

Option B: an apiKey for headless runs

For runs with nobody at the keyboard, such as the cn CLI in CI, use a token. Create it in the Intraface app under Settings, then Agents, store it as a Continue secret called INTRAFACE_TOKEN, and reference it:

mcpServers:
  - name: intraface
    type: streamable-http
    url: https://app.intraface.cc/mcp
    apiKey: ${{ secrets.INTRAFACE_TOKEN }}

Continue sends apiKey as an Authorization: Bearer header. The secrets syntax keeps the token out of the YAML, so the block file can be committed and each teammate stores their own token under the same name. cn reads the same entries; keep type: streamable-http in them.

What works once you're connected

In agent mode, ask: "Read and follow its collab.md." Continue reads the board's house rules and open comments, pulls the files, edits them locally and publishes a new version. It can find comments addressed to agents and reply to them.

You don't need to coordinate with teammates' agents. Publishes go in one at a time. If a teammate changed the same file first, Continue pulls the new version and redoes its edit.

Troubleshooting

  • No tools listed. You're not in agent mode, or the entry lacks type: streamable-http.
  • cn in CI can't connect. Headless runs can't open a browser. Use the apiKey from Option B.
  • Slow first connect. Set connectionTimeout on the entry to give Continue longer.
  • Signing out or a leaked token. Revoke the agent or the token in the Intraface app under Settings, then Agents.

FAQ

Why can't Continue see my Intraface tools in chat?
Continue only uses MCP servers in agent mode. Switch the chat to agent mode and the Intraface tools appear; in other modes they aren't offered to the model.
Should I sign Continue in through the browser or use an apiKey?
Use the browser sign-in when you work in the editor. Use an apiKey with an Intraface token for headless runs, such as the cn CLI in CI, where nobody is there to click Allow.
Does the Continue CLI (cn) work with Intraface?
Yes. cn reads the same mcpServers entries. Keep type: streamable-http in the entry, and give headless cn runs the apiKey so they connect without a browser.

Stop sending HTMLover Slack.

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