Skip to content

coder-vscode-electron-driver-ext: MCP runs fail — missing MCP_GATEWAY_URL / gateway sidecar in deploy manifest #824

Closed

Description

Original author: Cedric Vidal (@cedricvidal)

Summary

Runs that include MCP servers fail immediately on the coder-vscode-electron-driver-ext worker with:

Processing failed: MCP servers configured but MCP_GATEWAY_URL is not set — cannot proceed without gateway

The worker is shipped to int without an MCP gateway sidecar and without MCP_GATEWAY_URL, so any run that resolves at least one MCP server is rejected at setup time.

Repro

Log excerpt

[INFO ] Resolving 1 MCP server(s)
[INFO ] Resolved MCP servers: MS Learn
...
[INFO ] Active extensions before VS Code launch: github.copilot-chat@0.40.0, ms-azuretools.vscode-azureresourcegroups@0.12.4, ms-azuretools.vscode-cosmosdb@0.32.1, undefined_publisher.copilot-driver-ext@0.0.1
[ERROR] Processing failed: MCP servers configured but MCP_GATEWAY_URL is not set — cannot proceed without gateway

Root cause

The throw site is shared across all three coder workers:

But only the two ACP workers are deployed with the gateway:

$ rg -n 'MCP_GATEWAY_URL|mcp-gateway|mcpjungle' deploy/base/workers/
deploy/base/workers/coder-acp-claude-code.yaml:72:            - name: MCP_GATEWAY_URL
deploy/base/workers/coder-acp-copilot.yaml:72:            - name: MCP_GATEWAY_URL

deploy/base/workers/coder-vscode-electron-driver-ext.yaml (84 lines vs 172 for coder-acp-copilot.yaml) is missing both:

  1. The MCP_GATEWAY_URL=http://localhost:8080 env var on the worker container.
  2. The mcp-gateway (ghcr.io/mcpjungle/mcpjungle:latest-stdio) sidecar container.

Proposed fix

Mirror the MCP gateway setup from deploy/base/workers/coder-acp-copilot.yaml into deploy/base/workers/coder-vscode-electron-driver-ext.yaml:

  • Add MCP_GATEWAY_URL env var to the worker container.
  • Add the mcp-gateway sidecar with the same image, env, and ports.
  • Verify NO_PROXY and any cluster networking allow localhost:8080 traffic from the worker (the proxy stack on this worker may need a tweak).

Impact

All MCP-enabled scenarios on coder-vscode-electron-driver-ext are currently unrunnable on int (and presumably prod once promoted).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions