Connecting VS Code
Add the Zuse Bifrost MCP server to VS Code or the Claude Code extension, by signing in or with a personal access token.
Requirements
- VS Code 1.99 or newer, with MCP servers enabled (
chat.mcp.enabled), or the Claude Code extension. - A Zuse Bifrost account. VS Code signs you in; a personal access token is only needed when you want a connection narrower than your own reach.
The server address is written as https://mcp.example.test below; use the one your administrator shares.
Add the server
Run MCP: Add Server from the command palette, choose HTTP, and enter https://mcp.example.test with the name zusegenius. VS Code writes it to .vscode/mcp.json (workspace) or your user profile:
{
"servers": {
"zusegenius": {
"type": "http",
"url": "https://mcp.example.test"
}
}
}Sign in
When the server starts, VS Code asks to authenticate with Zuse Bifrost and opens your browser. Sign in if you are not already, read the consent screen and press Authorize; VS Code stores the connection in its secret storage, never in the config file.
Using the Claude Code extension instead? Open its terminal and run claude mcp add --transport http zusegenius https://mcp.example.test, then /mcp → Authenticate.
Use it
Open the chat panel in agent mode and prefix prompts with "using zusegenius" when you want MCP calls to run. Example:
Using zusegenius, what changed on project CRM today and who changed it?
The panel shows each tool invocation inline with an approve / deny prompt. Approve per call or pin auto-approve on the zusegenius namespace; tools that change data are marked so the prompt always appears for them.
Using a personal access token instead
Mint a token under Account Settings → API Tokens with the abilities you want the assistant to exercise and send it as a header; VS Code then skips the sign-in:
{
"servers": {
"zusegenius": {
"type": "http",
"url": "https://mcp.example.test",
"headers": {
"Authorization": "Bearer zg_live_YOUR_TOKEN"
}
}
}
}Prefer an input variable over a literal token in a workspace file that is committed.
Workspace vs. user scope
Put the config in the workspace .vscode/mcp.json if the Zuse Bifrost access should only apply to a specific repository. Keep it in your user profile if every VS Code window should have access.
Troubleshooting
- Never asked to sign in: the URL must be exactly the server's address; check View → Output → MCP for the server's log.
- Server fails to connect: the same output panel shows the handshake; a 401 there means the stored connection lapsed. Run MCP: Reset Trust or remove and re-add the server to sign in again.
- A tool is refused with a personal access token: the error envelope names the missing ability; mint a new token with it.
How is this guide?
Last updated on