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

Connect Gemini CLI to Intraface

Run gemini mcp add --transport http intraface https://app.intraface.cc/mcp, trust the folder when Gemini CLI asks, then type /mcp auth intraface and click Allow in your browser. From then on Gemini CLI can pull a shared board, edit it on your machine and publish a new version your team sees.

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

Set it up

  1. Add Intraface to Gemini CLI. The entry lands in .gemini/settings.json in the current folder.

    gemini mcp add --transport http intraface https://app.intraface.cc/mcp

    Add --scope user to reach your boards from every project.

  2. Start gemini in that folder and trust it when asked.

  3. Sign in from inside Gemini CLI. Your browser opens on app.intraface.cc; sign in and click Allow.

    /mcp auth intraface
  4. Give Gemini CLI 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: gemini mcp add, then /mcp auth

Add the server with Gemini's own command:

gemini mcp add --transport http intraface https://app.intraface.cc/mcp

Keep --transport http: without it Gemini treats the URL as a local command to start. The entry lands in .gemini/settings.json in the current folder. Add --scope user to put it in ~/.gemini/settings.json and reach your boards from every project.

Start gemini in that folder, trust it when asked, and sign in:

/mcp auth intraface

Your browser opens on app.intraface.cc. Sign in and click Allow.

If you'd rather edit settings.json yourself, use httpUrl, the key Gemini reads as Streamable HTTP:

{ "mcpServers": { "intraface": { "httpUrl": "https://app.intraface.cc/mcp" } } }

Option B: a token in a header

Over SSH or in a container there's no browser to sign in with, so use an Intraface token. Create it in the Intraface app under Settings, then Agents, and copy it when it's shown.

gemini mcp add --scope user --transport http \
  -H "Authorization: Bearer $INTRAFACE_TOKEN" \
  intraface https://app.intraface.cc/mcp

Your shell fills in the token before Gemini saves it, so keep this at user scope, out of any project file you commit.

What works once you're connected

Ask Gemini to "Read and follow its collab.md." It reads the board's house rules and comments, pulls the files, edits them in your folder and publishes a new version. It can also answer the comments people pinned to the page.

Publishes go in one at a time, so nobody's work is overwritten. If a teammate changed the same file first, Gemini CLI pulls the new version and redoes its edit.

Troubleshooting

  • Intraface shows as Disabled. Trust the folder (accept the dialog, or run /permissions trust), then check gemini mcp list again.
  • A confirmation before every tool call. "trust": true on the entry skips them all, publishing included, so set it only if you're happy with that.
  • Signed out. Run /mcp auth intraface again.

FAQ

Should Gemini CLI's settings.json use url or httpUrl for Intraface?
httpUrl, if you write the entry yourself. Gemini CLI reads a bare url as an SSE server, and Intraface speaks Streamable HTTP. Letting gemini mcp add write the entry also works, because it adds type http next to url.
Why is Intraface Disabled in gemini mcp list?
The folder isn't trusted yet, so Gemini CLI won't start project servers there. Accept the trust dialog when Gemini starts in that folder, or run /permissions trust inside Gemini.
Can Gemini CLI connect to Intraface over SSH?
Not with the browser sign-in, which needs a browser on the same machine. Over SSH or in a container, add the server with an Intraface token in a header instead.

Stop sending HTMLover Slack.

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