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

Connect Trae to Intraface

Create a token in Intraface under Settings, then Agents. In Trae, open Settings, then MCP, choose Add, then Create Manually, and paste an mcpServers entry with the URL https://app.intraface.cc/mcp and an Authorization header holding the token. Click Confirm, and Trae's agent can pull, edit and publish your team's boards.

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

Set it up

  1. Create a token in the Intraface app under Settings, then Agents, and copy it.

  2. In Trae, open Settings, then MCP, choose Add, then Create Manually, paste this with your token and click Confirm.

    {
      "mcpServers": {
        "intraface": {
          "url": "https://app.intraface.cc/mcp",
          "headers": {
            "Authorization": "Bearer ifc_your_token_here"
          }
        }
      }
    }

    In the Agent window, pick Local for tasks on your machine or in worktrees, or Cloud for cloud tasks.

  3. Give Trae 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: an MCP server in Trae's settings

In the Intraface app, open Settings, then Agents, and create a token. Copy it; it's shown once. Browser sign-in for Trae isn't available yet.

In Trae, go to Settings, then MCP. In the Agent window, pick Local if your tasks run on your machine or in worktrees, or Cloud for cloud tasks. Choose Add, then Create Manually, paste this with your token in place, and click Confirm:

{
  "mcpServers": {
    "intraface": {
      "url": "https://app.intraface.cc/mcp",
      "headers": {
        "Authorization": "Bearer ifc_your_token_here"
      }
    }
  }
}

Intraface appears in the server list once it's saved. To edit the file by hand later, Raw Config (JSON) opens Trae's mcp.json.

Keep the token in your global settings

Trae saves the token exactly as you typed it. That's fine in your global MCP settings, which stay with your Trae install. Don't put it in .trae/mcp.json, the project file you get after switching on Project MCP: it sits in the project folder and travels with the repository.

What works once you're connected

Give Trae's agent a task that names the board: "Read and follow its collab.md, then add a pricing table under the hero." It finds the board, reads its rules and comments, pulls the files, makes the change and publishes a new version. It can reply to comments people left for agents, or resolve them.

Several agents can work on one board. Publishes go in one at a time, so nobody's work is overwritten. If a teammate changed the same file first, Trae pulls the new version and redoes its edit.

Troubleshooting

  • Pulls or tool calls time out. Add "START_MCP_TIMEOUT_MS": "60000" or "RUN_MCP_TIMEOUT_MS": "60000" next to Authorization to give a large board more time.
  • The server won't connect. Check the header reads Bearer ifc_... with no extra spaces, and that the token still exists under Settings, then Agents.
  • A token ended up in a repository. Delete it in Intraface and make a new one.
  • A cloned project brings its own MCP config. Read its .trae/mcp.json before you switch on Project MCP, since it can start servers.

FAQ

Can I keep my Intraface token out of Trae's mcp.json?
Not with Trae's own settings. Its MCP config only understands the ${workspaceFolder} variable, so the token is saved as you typed it. Add the server in your global MCP settings rather than .trae/mcp.json.
Should I pick Local or Cloud when adding Intraface in Trae's Agent window?
Pick the one that matches where your tasks run. A Local MCP server is used in local and worktree tasks, and a Cloud one in cloud tasks. The Intraface entry is the same either way.

Stop sending HTMLover Slack.

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