How to add an MCP server to VS Code with OAuth

Setup, step by step

1. Step 1

   Create a Locus Pro account

   Sign up at paywithlocus.com/pro. The Free plan has no subscription. Paid calls use prepaid credits.

2. Step 2

   Add the server to your workspace

   Create .vscode/mcp.json in your project with this content. To add Locus for every workspace instead, run code --add-mcp with the same server.

   {
     "servers": {
       "locus": {
         "type": "http",
         "url": "https://api.paywithlocus.com/api/credits/mcp"
       }
     }
   }

3. Step 3

   Start the server

   Open the Command Palette, run MCP: List Servers, pick locus, and choose Start Server.

4. Step 4

   Approve Locus

   VS Code asks to let the server authenticate to Locus Pro MCP. Choose Allow, then Open to launch the browser. Sign in to Locus and approve the connection.

5. Step 5

   Check the connection

   Open Copilot Chat in agent mode and ask: "What's my Locus balance?" A balance check is free.

What do I need before adding Locus to VS Code?

You need VS Code with GitHub Copilot signed in. Copilot Chat is the part that calls MCP tools, and it has a free tier. Without a Copilot sign-in, the server connects but no chat can use it.

We tested VS Code 1.139.1. The server started, OAuth finished, and VS Code discovered all 11 Locus tools.

Should I add Locus to the workspace or my user profile?

Use .vscode/mcp.json to share the server with everyone who opens the repo. Each person still signs in to their own Locus account, so no credentials go in the file.

Use code --add-mcp, or MCP: Open User Configuration, to load Locus in every workspace on your machine.

• code --add-mcp '{"name":"locus","type":"http","url":"https://api.paywithlocus.com/api/credits/mcp"}'

How do I fix a VS Code MCP sign-in problem?

Run MCP: List Servers, pick locus, and restart it. If no browser tab opens, choose Copy on the external website prompt and paste the link into your browser.

• Check that the URL is exactly https://api.paywithlocus.com/api/credits/mcp.
• Open the server output from MCP: List Servers to see discovery and auth logs.
• Revoke the Visual Studio Code connection in Locus and sign in again to reset it.

Does VS Code get the Locus skills?

Not through this setup. The MCP server gives Copilot the tools. For usage guidance, Copilot can call the get_locus_guide tool, which returns the same operating guides the skills contain.