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

Connect GitHub Copilot CLI to Intraface

Create a token in the Intraface app under Settings, then Agents. Run copilot mcp add with the URL https://app.intraface.cc/mcp and an Authorization: Bearer header holding the token. Copilot CLI saves it in ~/.copilot/mcp-config.json, outside your repository, and can then pull, edit and publish shared boards.

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

Set it up

  1. Create a token in the Intraface app under Settings, then Agents, and copy it.

  2. Add Intraface to Copilot CLI with your token in place.

    copilot mcp add --transport http \
      --header "Authorization: Bearer ifc_your_token" \
      intraface https://app.intraface.cc/mcp
  3. Give Copilot 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: copilot mcp add with a token

Start in the Intraface app: Settings, then Agents, then create a token. Name it copilot so its publishes are easy to spot, and copy it straight away; it's only shown once. Browser sign-in for Copilot CLI isn't available yet.

Add the server from your terminal:

copilot mcp add --transport http \
  --header "Authorization: Bearer ifc_your_token" \
  intraface https://app.intraface.cc/mcp

Copilot CLI writes it to ~/.copilot/mcp-config.json in this shape:

{
  "mcpServers": {
    "intraface": {
      "type": "http",
      "url": "https://app.intraface.cc/mcp",
      "headers": { "Authorization": "Bearer ifc_your_token" },
      "tools": ["*"]
    }
  }
}

That file sits in your home folder, which is the right place for a token. Don't copy the entry into a project .mcp.json that gets committed. Run copilot mcp list to see it under your user servers.

What works once you're connected

Inside a session, /mcp show intraface shows the server's status and its tools. Then hand Copilot a board: "Read and follow its collab.md." It reads the house rules, pulls the files into your current folder, edits them and publishes a new version. It can also list the comments people pinned to the page, reply and resolve them.

Publishes go in one at a time, so Copilot and a teammate's agent never overwrite each other. If a teammate changed the same file first, Copilot pulls the new version and redoes its edit.

Troubleshooting

  • The server is missing from the list. Project servers load only after you trust the folder. For copilot -p in an untrusted folder, set GITHUB_COPILOT_PROMPT_MODE_WORKSPACE_MCP=true.
  • Two entries named intraface. A project file wins over ~/.copilot/mcp-config.json when names clash, so rename one of them.
  • Slow connections. copilot mcp add --timeout MS sets a longer timeout.
  • The token expired. Unused tokens lapse after 90 days. Make a new one, then edit the header in mcp-config.json.

FAQ

Why doesn't Intraface show up in copilot mcp list?
If the server is in .mcp.json or .github/mcp.json, the folder probably isn't trusted. Copilot CLI skips project servers in untrusted folders. Trust the folder when you launch, or move the entry to ~/.copilot/mcp-config.json.
Can GitHub Copilot CLI read Intraface boards without publishing?
Yes. Narrow the tools field of the intraface entry to list_boards, get_board, pull_board, read_file and list_comments, and Copilot can read but not publish.
How do I pause Intraface in Copilot CLI without deleting it?
Run /mcp disable intraface in a session. The entry stays in your config and stops loading until you run /mcp enable intraface.

Stop sending HTMLover Slack.

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