human_bridge_request — Bursia MCP Visitor Gateway Canary MCP Tool
human_bridge_request
(human bridge request) is one of 15 tools on the
Bursia MCP Visitor Gateway Canary
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call human_bridge_request from your client
- Claude Code Bursia MCP Visitor Gateway Canary human_bridge_request run in your project directory
- Claude Desktop Bursia MCP Visitor Gateway Canary human_bridge_request ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bursia MCP Visitor Gateway Canary human_bridge_request ~/.cursor/mcp.json
- VS Code Bursia MCP Visitor Gateway Canary human_bridge_request .vscode/mcp.json
- Zed Bursia MCP Visitor Gateway Canary human_bridge_request ~/.config/zed/settings.json
- Windsurf Bursia MCP Visitor Gateway Canary human_bridge_request ~/.codeium/windsurf/mcp_config.json
- Cline Bursia MCP Visitor Gateway Canary human_bridge_request ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bursia MCP Visitor Gateway Canary human_bridge_request ~/.gemini/settings.json
- Grok Bursia MCP Visitor Gateway Canary human_bridge_request .mcp.json (in your project root)
- ChatGPT Bursia MCP Visitor Gateway Canary human_bridge_request Settings → Connectors → Advanced → Developer mode
- Claude.ai Bursia MCP Visitor Gateway Canary human_bridge_request Settings → Connectors → Add custom connector
- LangChain Bursia MCP Visitor Gateway Canary human_bridge_request pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bursia-canary https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcpOther tools on this server
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.