Connect Visual Studio to Intraface
You need Visual Studio 2026, or Visual Studio 2022 version 17.14 or later. Add an intraface server with the URL https://app.intraface.cc/mcp to %USERPROFILE%\.mcp.json, select Authentication Required in the CodeLens and sign in in your browser, then switch on its tools in Copilot's agent mode.
Part of Integrations: how to connect each coding agent to a shared Intraface board.
Create %USERPROFILE%\.mcp.json in Visual Studio and add Intraface, then save it.
{ "servers": { "intraface": { "url": "https://app.intraface.cc/mcp" } } }Needs Visual Studio 2026, or Visual Studio 2022 version 17.14 or later, with GitHub Copilot.
Select Authentication Required in the CodeLens above the server. Your browser opens.
Sign in and click Allow.
In the Copilot chat pane, switch to Agent mode, open Tools and tick Intraface’s tools.
Give Copilot 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: add the server and sign in from CodeLens
You need Visual Studio 2026, or Visual Studio 2022 version 17.14 or later, with GitHub Copilot.
Create %USERPROFILE%\.mcp.json in Visual Studio, so you get the JSON schema as you type, and add Intraface:
{
"servers": {
"intraface": {
"url": "https://app.intraface.cc/mcp"
}
}
}
Save it. Above the server, select Authentication Required in the CodeLens and sign in to Intraface in the browser window that opens, then click Allow. Later, Manage Authentication in the same CodeLens lets you sign in again. If you don't see CodeLens, turn it on under Tools, Options, Text Editor, CodeLens.
%USERPROFILE%\.mcp.json loads for every solution. To share the server with your team, put the same entry in <SOLUTIONDIR>\.mcp.json and check it in.
Option B: a token instead of the browser
If the browser sign-in doesn't finish, use an Intraface token. Create one in the Intraface app under Settings, then Agents; it's shown once. Visual Studio also reads <SOLUTIONDIR>\.vscode\mcp.json, the format VS Code uses, where the token goes in a header:
{
"servers": {
"intraface": {
"type": "http",
"url": "https://app.intraface.cc/mcp",
"headers": { "Authorization": "Bearer ifc_your_token_here" }
}
}
}
Keep that file out of source control, since it holds your token.
What works once you're connected
In the Copilot chat pane, switch to Agent mode and open Tools. Intraface's tools start switched off, like every MCP server's in Visual Studio, so tick the ones you want, or all of them.
Then ask: "Read
Your whole team can point agents at the same board. Publishes go in one at a time, so nobody's work is overwritten. If a teammate changed the same file first, Copilot pulls the new version and redoes its edit.
Troubleshooting
- A confirmation for every call. Use the Confirm dropdown (Allow on 2022) to approve a tool for the session, the solution or always. Reset those choices under Tools, Options, GitHub, Copilot.
- Earlier approvals vanished. When a server's tool list changes, Visual Studio clears approvals and fetches the tools again. Approve them once more.
- A policy error on the server. Your GitHub organization keeps a list of approved MCP servers. Ask an admin to add Intraface.
- No Agent mode at all. An admin can turn off agent mode and MCP for your Copilot subscription on the Copilot dashboard.
FAQ
- Which mcp.json should hold the Intraface server in Visual Studio?
- %USERPROFILE%\.mcp.json loads for every solution and is yours alone. The .mcp.json at the solution root is meant for source control, so use it to share the server with your team, and never put a token in it.
- Why did Visual Studio ask me to trust the Intraface server again?
- From Visual Studio 2026 version 18.7, a trust dialog appears when a server's configuration or tools change. Accept runs the new version, Always Trust stops future prompts for that server, and Reject keeps it stopped.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.