Visual Studio Code

Visual Studio Code supports remote MCP servers natively. Connect the GitHubCopilot agent mode directly to the platform with a HTTP server configuration.

Attention

OAuth tokens are limited by both their scope and platform permissions. Use a dedicated token and review tool calls before approving writing operations.

Prerequisites

• A current version of Visual Studio Code
• GitHub Copilot with agent mode enabled
• Access to a court of the platform
• A scoped the platform OAuth token

Endpoint

Choose the end point for your platform environment:

Environment	MCP URL
the platform US	https://us.probo.com/api/mcp/v1
the platform EU	https://eu.probo.com/api/mcp/v1
Custom	https://your-probo-instance.com/api/mcp/v1

The ___ZBT_I18N_RUNTIME_BLOCK_172__ segment is required.

Configure VS Code

1. Create a the platform OAuth token

   On the platform, open the account menu, select OAuth tokens, and create a purpose token called VS Code. Authentication guidance and guidance.

2. Choose the configuration scope

   • Create .vscode/mcp.json for a connection to the workspace.
   • Run MCP: Open User Configuration from the Command Palette for a connection available in each workspace.

3. Add the remote server

   {
     "servers": {
       "probo": {
         "type": "http",
         "url": "https://us.probo.com/api/mcp/v1",
         "headers": {
           "Authorization": "Bearer ${input:probo-api-token}"
         }
       }
     },
     "inputs": [
       {
         "type": "promptString",
         "id": "probo-api-token",
         "description": "Probo OAuth token",
         "password": true
       }
     ]
   }

   Replace the URL if you use the EU region or a self-hosted court. VS Code stores the requested secret separately, instead of writing it into the workspace file.

4. Start the server.

   Save mcp.json and then use Start the above action is the configuration probo. MCP: List Servers from the Command Palette and select probo.

Verify the connection

Open Chat, select Agent, and start with a read-only request:

Use Probo to list the organizations I can access.

The VS code should request the token at first use, request the approval of the tool, and then return it to the platform organizations.

List the open risks for organization org_xxx.
Summarize overdue compliance tasks without changing anything.

Share workspace configuration safely

You can commit .vscode/mcp.json when using an input variable. Do not replace ${input:probo-api-token} with a literal token.

Each contributor provides its own token, so the platform continues to impose the access and role of that person’s organization.

Troubleshooting

Serverul nu este listat

• Confirm that the workspace file is .vscode/mcp.json.
• Confirms that the top-level property is servers, not mcpServers.
• Validate JSON and run MCP: List Servers.

The server returns 401

• Run MCP: Reset Cached Tools or turn off and restart the server, then enter a valid token.
• Confirm that the title starts with Bearer .
• Generate a new token if the existing token has been revoked or has expired.

The server returns 404

Confirms that the URL ends with /api/mcp/v1. The route /api/mcp which is not a version is not a valid endpoint for the MCP platform.

Instrumentele sunt indisponibile

• Confirm the server running with MCP: List Servers.
• Confirm the platform’s role to access the requested organization and operation.
• Try the same end point with MCP Inspector.

For the configuration behavior VS specific to the code, see VS Code MCP server documentation.