Connect Amp to Intraface
Run amp mcp add intraface https://app.intraface.cc/mcp, then start Amp. Your browser opens on app.intraface.cc; sign in and click Allow. From then on Amp can pull a shared board, edit it in your workspace and publish a new version. Inside an Orb, give Amp an Intraface token in a header instead.
Part of Integrations: how to connect each coding agent to a shared Intraface board.
Add Intraface to Amp. It goes into ~/.config/amp/settings.json.
amp mcp add intraface https://app.intraface.cc/mcpStart Amp. The first time it reaches Intraface, your browser opens on app.intraface.cc; sign in and click Allow.
Give Amp 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: amp mcp add, then sign in
amp mcp add intraface https://app.intraface.cc/mcp
Start Amp. The first time it reaches Intraface, your browser opens on app.intraface.cc. Sign in and click Allow. Amp keeps that sign-in, so you never paste a key.
If you'd rather edit the file, the same server in ~/.config/amp/settings.json looks like this:
{
"amp.mcpServers": {
"intraface": { "url": "https://app.intraface.cc/mcp" }
}
}
Keep it in your own settings unless the whole team should get it. An entry in the project's .amp/settings.json is a workspace server, and each person runs amp mcp approve intraface before Amp will start it.
Option B: a token header for Orbs
An Orb runs on another machine, can't open a browser and doesn't read your local settings. Create a token in the Intraface app under Settings, then Agents, set it as INTRAFACE_TOKEN in the Orb's environment, and add the header to the workspace's .amp/settings.json:
{
"amp.mcpServers": {
"intraface": {
"url": "https://app.intraface.cc/mcp",
"headers": { "Authorization": "Bearer ${INTRAFACE_TOKEN}" }
}
}
}
Amp fills in ${INTRAFACE_TOKEN} from the environment, so the file names the variable and never holds the token. That makes it safe to commit.
What works once you're connected
Hand Amp a board link: "Read
Several people's agents can share a board. Publishes go in one at a time, so nobody's work is overwritten. If a teammate changed the same file first, Amp pulls the new version and redoes its edit.
Troubleshooting
- "Awaiting approval". The server lives in
.amp/settings.json. Runamp mcp approve intraface, or move it to your user settings. - The connection looks broken. Run
amp mcp doctorto see each server's state. - Signing out.
amp mcp oauth logout intrafaceclears the stored sign-in; the next session asks again. - You want a say before each publish. In Amp's MCP settings, set the
publishtool to Ask First.
FAQ
- Why does Amp say my Intraface server is awaiting approval?
- You added it to .amp/settings.json in the project, which makes it a workspace server. Amp won't start workspace servers until you run amp mcp approve intraface. Servers in your own ~/.config/amp/settings.json skip that step.
- How do I sign Amp out of Intraface?
- Run amp mcp oauth logout intraface, and the next session asks you to sign in again. To cut access everywhere, revoke the agent in the Intraface app under Settings, then Agents.
- Can Amp in an Orb publish to an Intraface board?
- Yes, with a token. Put a header entry in the workspace .amp/settings.json that reads the token from INTRAFACE_TOKEN, and set that variable in the Orb's environment.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.