Connect Warp to Intraface
In the Warp app, open Settings, then Agents, then MCP servers, click + Add and paste a URL-based server for https://app.intraface.cc/mcp with an Authorization header carrying a token from Intraface's Settings, then Agents. In Warp's terminal CLI, add the same server without the header and sign in once in your browser.
Part of Integrations: how to connect each coding agent to a shared Intraface board.
Create a token in the Intraface app under Settings, then Agents, and copy it.
In Warp, open Settings, then Agents, then MCP servers, click + Add, pick a URL-based server and paste this.
{ "intraface": { "url": "https://app.intraface.cc/mcp", "headers": { "Authorization": "Bearer ifc_your_token_here" } } }Give Warp 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: a token header in the Warp app
Start in Intraface: Settings, then Agents, then create a token. Name it after the machine and copy it when it appears, because it isn't shown again. Browser sign-in for the Warp app isn't available yet.
Open the MCP pane in Warp through Settings, then Agents, then MCP servers, or Open MCP Servers from the Command Palette. Click + Add, pick a URL-based server and paste:
{
"intraface": {
"url": "https://app.intraface.cc/mcp",
"headers": {
"Authorization": "Bearer ifc_your_token_here"
}
}
}
Warp stores the header as written, so keep this entry in your personal settings or in ~/.warp/.mcp.json, never in a project's .warp/.mcp.json. Think twice before sharing it with your Warp team for the same reason.
Option B: browser sign-in from Warp's terminal CLI
Warp's terminal CLI can sign in without a token. Add the same entry with no headers block (or run the bundled /tui-migrate-setup skill to copy your global servers from the app). When the agent first reaches Intraface, your browser opens on app.intraface.cc; sign in and click Allow. The CLI keeps its own sign-in, separate from the app's.
What works once you're connected
Ask Warp's agent: "Read
Other people's agents can publish to the same board. Publishes go in one at a time, so nobody's work is overwritten. If a teammate changed the same file first, Warp's agent pulls the new version and redoes its edit.
Troubleshooting
- Warp keeps asking before tool calls. Agent Profiles decide this: list Intraface's tools as ones that run without asking, or leave it to "Agent decides".
- A project server won't start. Project-scoped servers wait for you to switch them on, one by one, each session.
- The browser sign-in got stuck. Delete
~/.mcp-authto reset stored MCP sign-ins (all of them, not just Intraface's), then try again. - Sharing logs. View Logs on the server shows its output; remove your token before you send a log to anyone.
FAQ
- Where should I keep the Warp entry that holds my Intraface token?
- In your personal Warp settings or the global ~/.warp/.mcp.json. A project's .warp/.mcp.json sits in the repository, where anyone with the code could read the token.
- Does Warp's terminal CLI reuse my Intraface setup from the Warp app?
- Partly. The bundled /tui-migrate-setup skill copies your global MCP server entries to the CLI, but Warp never copies sign-ins, so you sign in to Intraface again in the CLI.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.