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