Connect Kilo Code to Intraface
Add a remote server named intraface with the URL https://app.intraface.cc/mcp under the mcp key in kilo.jsonc. When Kilo Code connects, it opens your browser, or shows a notification you click. Sign in to Intraface and click Allow. Then Kilo Code can pull a shared board, edit the files and publish a new version.
Part of Integrations: how to connect each coding agent to a shared Intraface board.
Add Intraface under the mcp key in ~/.config/kilo/kilo.jsonc, or in a project's kilo.jsonc for one repository.
{ "mcp": { "intraface": { "type": "remote", "url": "https://app.intraface.cc/mcp" } } }Sign in and click Allow when Kilo Code opens your browser. If it shows a notification instead, click it first.
Give Kilo 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: a remote MCP server in kilo.jsonc
Kilo Code reads MCP servers from kilo.jsonc. Put this in ~/.config/kilo/kilo.jsonc to reach your boards from every project, or in a project's kilo.jsonc or .kilo/kilo.jsonc for one repository. Project settings win over global ones.
{
"mcp": {
"intraface": {
"type": "remote",
"url": "https://app.intraface.cc/mcp"
}
}
}
No key and no header. When Kilo Code connects it opens your browser on app.intraface.cc. If it doesn't, the server shows needs_auth and the VS Code extension shows a notification; click it. Sign in, check what the agent may do (read boards, write boards, comment) and click Allow.
Option B: a token in a header
Use this in a project kilo.jsonc that goes into git, so each teammate brings their own token. Create one in the Intraface app under Settings, then Agents, copy it when it's shown, and export it as INTRAFACE_TOKEN. Kilo's {env:...} syntax reads it from your environment:
{
"mcp": {
"intraface": {
"type": "remote",
"url": "https://app.intraface.cc/mcp",
"oauth": false,
"headers": {
"Authorization": "Bearer {env:INTRAFACE_TOKEN}"
}
}
}
}
"oauth": false tells Kilo to skip the browser sign-in for this entry.
What works once you're connected
Ask Kilo Code to "Read intraface_<tool>, next to Kilo's own tools. It can answer comments on the page too.
Publishes go in one at a time, so nobody's work is overwritten. If a teammate changed the same file first, Kilo Code pulls the new version and redoes its edit.
Troubleshooting
- Too many approval prompts. Choose Approve Always on a tool, or add allow rules under
permissioninkilo.jsonc, per tool (intraface_pull_board) or for all of them (intraface_*). - Slow boards time out. Set
timeouton the entry, in milliseconds. - Signed out after a long break. An unused sign-in expires after 90 days. Reconnect and approve it in the browser again.
FAQ
- Which kilo.jsonc should hold the Intraface server?
- The global ~/.config/kilo/kilo.jsonc if you want your boards in every project. A project kilo.jsonc overrides it, which suits a repository that works on one board. Don't put a token there if the file is committed.
- Why does Kilo Code show Intraface as needs_auth?
- Kilo Code reached the server but hasn't signed in yet. Click the notification in the VS Code extension to open the browser, then click Allow on app.intraface.cc.
- Can Kilo Code publish to Intraface without asking me each time?
- Yes. Choose Approve Always on the publish prompt, or add an allow rule for intraface_publish (or intraface_* for every tool) to the permission settings in kilo.jsonc.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.