bridge_call_api — WasapFlow Bridge MCP Tool
bridge_call_api
(bridge call api) is one of 16 tools on the
WasapFlow Bridge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call bridge_call_api from your client
- Claude Code WasapFlow Bridge bridge_call_api run in your project directory
- Claude Desktop WasapFlow Bridge bridge_call_api ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WasapFlow Bridge bridge_call_api ~/.cursor/mcp.json
- VS Code WasapFlow Bridge bridge_call_api .vscode/mcp.json
- Zed WasapFlow Bridge bridge_call_api ~/.config/zed/settings.json
- Windsurf WasapFlow Bridge bridge_call_api ~/.codeium/windsurf/mcp_config.json
- Cline WasapFlow Bridge bridge_call_api ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WasapFlow Bridge bridge_call_api ~/.gemini/settings.json
- Grok WasapFlow Bridge bridge_call_api .mcp.json (in your project root)
- ChatGPT WasapFlow Bridge bridge_call_api Settings → Connectors → Advanced → Developer mode
- Claude.ai WasapFlow Bridge bridge_call_api Settings → Connectors → Add custom connector
- LangChain WasapFlow Bridge bridge_call_api pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bridge https://officialapi.wasapflow.com/bridge/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.