Connect Factory Droid to Intraface
Create a token in the Intraface app under Settings, then Agents, and export it as IFC_TOKEN. Add an http server for https://app.intraface.cc/mcp to ~/.factory/mcp.json with the header Authorization: Bearer ${IFC_TOKEN}. Droid fills in the token when it connects, so the file never holds the secret, and Droid can then publish to shared boards.
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.
Put the token in your shell profile as IFC_TOKEN.
export IFC_TOKEN=ifc_your_tokenAdd Intraface to ~/.factory/mcp.json.
{ "mcpServers": { "intraface": { "type": "http", "url": "https://app.intraface.cc/mcp", "headers": { "Authorization": "Bearer ${IFC_TOKEN}" }, "oauth": false } } }Give Droid 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 read from ${IFC_TOKEN}
Droid fills in environment variables inside MCP headers, so your secret stays in the shell and the config file only names it. Browser sign-in for Droid isn't available yet.
In the Intraface app open Settings, then Agents, and create a token called droid. Copy it; it's shown once. Put it in your shell profile:
export IFC_TOKEN=ifc_your_token
Then add the server to ~/.factory/mcp.json, or to .factory/mcp.json if the whole project should have it:
{
"mcpServers": {
"intraface": {
"type": "http",
"url": "https://app.intraface.cc/mcp",
"headers": { "Authorization": "Bearer ${IFC_TOKEN}" },
"oauth": false
}
}
}
"oauth": false tells Droid to use the header and skip its own sign-in step. If IFC_TOKEN isn't set, Droid won't connect and names the missing variable.
Option B: add it with droid mcp add
The same entry from the command line. Single quotes keep your shell from pasting the real token into the file:
droid mcp add intraface https://app.intraface.cc/mcp --type http \
--header 'Authorization: Bearer ${IFC_TOKEN}' --no-oauth
What works once you're connected
Point Droid at a board: "Read
To keep a reviewer Droid from publishing, list only the tools it may use in enabledTools:
"enabledTools": ["list_boards", "get_board", "pull_board", "read_file", "list_comments", "reply_comment"]
Publishes go in one at a time, so nobody's work is lost. If a teammate changed the same file first, Droid pulls the new version and redoes its edit.
Troubleshooting
- It times out on connect. Raise
connectTimeoutabove the 10,000 ms default on a slow network. - Approvals reset. Approvals are tied to the server's URL, so changing it means approving again.
droid mcp permissions revoke intraface publishwithdraws one tool. - New token. Revoke the old one under Settings, then Agents, export the new value as
IFC_TOKENand restart Droid. Unused tokens lapse after 90 days.
FAQ
- Is it safe to commit .factory/mcp.json with the Intraface server in it?
- Yes, as long as the header says Bearer ${IFC_TOKEN} and not the token itself. Droid reads the variable from each person's shell, so every teammate exports their own token and publishes as themselves.
- Why does Factory Droid ask me to approve the Intraface tools again?
- Droid ties tool approvals to the server's URL. Change the URL in mcp.json, even slightly, and earlier approvals stop applying. droid mcp permissions list shows what's approved.
- How can I tell whether Factory Droid connected to Intraface?
- Run droid mcp list. It shows each server and whether it connected. Inside a session, /mcp opens the same view.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.