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

Connect Qwen Code to Intraface

Run qwen mcp add --transport http intraface https://app.intraface.cc/mcp, then restart Qwen Code. Open /mcp, start the sign-in for intraface, and click Allow in your browser. The server goes into your user settings, so every project can reach your boards, and Qwen Code can pull, edit and publish them.

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

Set it up

  1. Add Intraface to Qwen Code. It goes into ~/.qwen/settings.json, so every project can reach your boards.

    qwen mcp add --transport http intraface https://app.intraface.cc/mcp
  2. Restart Qwen Code, open /mcp and start the sign-in for intraface. Your browser opens on app.intraface.cc.

    /mcp
  3. Sign in and click Allow.

  4. Give Qwen Code 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: qwen mcp add, then sign in from /mcp

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

Qwen Code writes this to ~/.qwen/settings.json unless you say otherwise, so every project can reach your boards. Add --scope project to keep it in .qwen/settings.json for one repository.

Restart Qwen Code, then type /mcp to open the server dialog and start the sign-in for intraface. Your browser opens on app.intraface.cc; sign in and click Allow.

Writing the entry by hand? Use httpUrl, which Qwen Code reads as Streamable HTTP:

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

Option B: a header token for remote machines

The browser sign-in only works when Qwen Code runs on the computer in front of you. On a cloud box or web terminal, create a token in the Intraface app under Settings, then Agents, and copy it when it's shown. Then add the server with a header:

qwen mcp add --transport http intraface https://app.intraface.cc/mcp \
  --header "Authorization: Bearer $INTRAFACE_TOKEN"

The shell fills in the value, so the token is saved in ~/.qwen/settings.json. Leave it at user scope and out of any project file you commit.

What works once you're connected

Type "Read and follow its collab.md." Qwen Code reads the board's house rules and pinned comments, pulls the files, edits them and publishes. It can also start a new board from scratch and pick out feedback that people addressed to agents.

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

Troubleshooting

  • Intraface's tools show up late or not at all. Raise discoveryTimeoutMs on the entry; remote servers get 5 seconds by default.
  • Shows "Disconnected". Check the URL in qwen mcp list, then restart Qwen Code.
  • A confirmation before each tool call. Set "trust": true on the entry in a trusted workspace, or narrow the tools with includeTools.

FAQ

Does Qwen Code need a restart after adding Intraface?
Yes. Qwen Code doesn't pick up new servers in a running session, so quit and start it again in your folder before you open /mcp.
Can I use Qwen Code with Intraface on a remote server?
The browser sign-in needs Qwen Code and your browser on the same computer. On a cloud machine or web terminal, add the server with an Intraface token in a header instead.
Where does Qwen Code keep its Intraface sign-in?
In ~/.qwen/mcp-oauth-tokens.json, readable only by you. On a shared machine, set QWEN_CODE_FORCE_ENCRYPTED_FILE_STORAGE=true before signing in to keep it encrypted.

Stop sending HTMLover Slack.

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