Install in VS Code
Add Levirge Brain to VS Code with MCP: Add Server or mcp.json, sign in, and use its tools from Copilot Chat in Agent mode.
Needs GitHub Copilot installed and signed in: the tools run inside Copilot Chat.
Guided setup
1 · Add the server
Open the Command Palette (⇧⌘P / Ctrl+Shift+P) and run MCP: Add Server.
2 · Choose the transport
Choose HTTP.
3 · Paste the URL
Paste this and press Enter:
https://brain.levirge.com/mcp4 · Name it
Type levirge-brain as the Server ID and press Enter.
5 · Choose the scope
Choose Global so it works in every workspace.
6 · Sign in
Click Allow when VS Code asks to authenticate to auth.levirge.com, then Open when it asks to open the website. Sign in in the browser.
7 · Turn on the tools
Open Copilot Chat in Agent mode, click the tools icon and make sure
levirge-brain is ticked. Then verify with a read-only call: kb_overview
returns your workspace's knowledge summary.
Edit mcp.json
Run MCP: Open User Configuration from the Command Palette and add:
{
"servers": {
"levirge-brain": { "type": "http", "url": "https://brain.levirge.com/mcp" }
}
}Save, then run MCP: List Servers → levirge-brain → Start Server. Click Allow, then Open, and sign in.
Using a token instead
For machines that cannot open a browser. Get a
token first, add a headers line to the entry
in mcp.json, and start the server as above. No sign-in prompt will appear.
{
"servers": {
"levirge-brain": {
"type": "http",
"url": "https://brain.levirge.com/mcp",
"headers": { "Authorization": "Bearer <your-token>" }
}
}
}Troubleshooting
It did not prompt me to allow authentication. The server is not started
until you start it: run MCP: List Servers, pick levirge-brain, and choose
Start Server. The Allow prompt appears on start. To have it start on its
own, turn on the chat.mcp.autostart setting.
The tools are not in Copilot Chat. They only show in Agent mode. Switch the chat mode, then click the tools icon and make sure levirge-brain is ticked.
I connected, but there are no Brain tools. Clients read the tool list once, when they connect. Quit and reopen the app so it reconnects.
"401" or "Unauthorized" with a token. Check the header is exactly
Authorization: Bearer <your-token>, and that the token has not been revoked on
Profile → MCP Tokens.
Other clients
Every guide is listed under any MCP client. No workspace yet? Request access.