Skip to content

Connect VS Code to a Voozeo MCP server

Updated October 24, 2026

To connect VS Code to your Voozeo MCP server, paste a block into .vscode/mcp.json: VS Code asks for the key on first start and does not store it in the file.

What you need

  • A Voozeo server in the "active" state, which means at least one source is ready. See getting started.
  • The MCP key of that server. It is shown only once; if you lost it, regenerate it.
  • If your server uses OAuth 2.0, there is no key: add the server URL alone, then each person signs in with their own account at the API provider on the first call. See servers using OAuth.
  • A VS Code version with MCP support.

Add the server

  1. In Voozeo, open your server, go to the "Connection" tab and choose VS Code. The real URL is already filled in. If the block shows <YOUR_KEY>, replace it with your key.
  2. Create the .vscode/mcp.json file in your project and paste the block.
  3. Start the server from VS Code. It asks for the key: paste your MCP key.

VS Code · .vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "voozeo-key",
      "description": "Voozeo API key",
      "password": true
    }
  ],
  "servers": {
    "my-server": {
      "type": "http",
      "url": "https://mcp.example.com/s/<server-id>/mcp",
      "headers": {
        "Authorization": "Bearer ${input:voozeo-key}"
      }
    }
  }
}

VS Code uses the URL with the key in the Authorization header, and the key comes from a masked prompt. That makes the file safe to commit: it contains no secret. See the two URL forms.

One-click installation

Right after you create the server or regenerate its key, the Connection tab shows an "Add to VS Code" button. It opens VS Code with the server already filled in, key included, so use it only on your own computer. The button is not shown in the Android app, nor when the key can no longer be displayed: copy the block above instead.

Check the connection

  1. Ask the assistant in VS Code to list the tools of the server, or ask a question that needs one.
  2. Open the "Log" tab of the server in Voozeo: every tool call appears there.
  3. If in doubt, try the tool first in the "Test" tab. See testing in the sandbox.

Troubleshooting

VS Code reportsLikely causeWhere to look
Authentication error (401)Key missing, wrong, from another server, or regenerated401 on the AI side
Access denied (403)Server not "active", or workspace suspended403 on the AI side
Quota messageThe monthly call limit of your plan is reachedQuota reached

See also the official VS Code documentation on MCP configuration.

Next steps

Get started