Windsurf Bursia MCP Visitor Gateway Canary human_oversight_policy
How to: Windsurf Bursia MCP Visitor Gateway Canary human_oversight_policy
Add Bursia MCP Visitor Gateway Canary to Windsurf
-
01
Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"bursia-canary": {
"serverUrl": "https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp"
}
}
}-
02
Save the file and restart Windsurf.
-
03
Ask for something human_oversight_policy does. Windsurf lists the server's tools on connect and calls human_oversight_policy itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Bursia MCP Visitor Gateway Canary's identifier in your config matches the one above exactly.
Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.