bridge_docs_section — WasapFlow Bridge MCP Tool
bridge_docs_section
(bridge docs section) 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_docs_section from your client
- Claude Code WasapFlow Bridge bridge_docs_section run in your project directory
- Claude Desktop WasapFlow Bridge bridge_docs_section ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WasapFlow Bridge bridge_docs_section ~/.cursor/mcp.json
- VS Code WasapFlow Bridge bridge_docs_section .vscode/mcp.json
- Zed WasapFlow Bridge bridge_docs_section ~/.config/zed/settings.json
- Windsurf WasapFlow Bridge bridge_docs_section ~/.codeium/windsurf/mcp_config.json
- Cline WasapFlow Bridge bridge_docs_section ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WasapFlow Bridge bridge_docs_section ~/.gemini/settings.json
- Grok WasapFlow Bridge bridge_docs_section .mcp.json (in your project root)
- ChatGPT WasapFlow Bridge bridge_docs_section Settings → Connectors → Advanced → Developer mode
- Claude.ai WasapFlow Bridge bridge_docs_section Settings → Connectors → Add custom connector
- LangChain WasapFlow Bridge bridge_docs_section 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.