get_network_errors — BugEzy MCP Tool Read-only
get_network_errors
(get network errors) is one of 14 tools on the
BugEzy
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_network_errors from your client
- Claude Code BugEzy get_network_errors run in your project directory
- Claude Desktop BugEzy get_network_errors ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BugEzy get_network_errors ~/.cursor/mcp.json
- VS Code BugEzy get_network_errors .vscode/mcp.json
- Zed BugEzy get_network_errors ~/.config/zed/settings.json
- Windsurf BugEzy get_network_errors ~/.codeium/windsurf/mcp_config.json
- Cline BugEzy get_network_errors ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BugEzy get_network_errors ~/.gemini/settings.json
- Grok BugEzy get_network_errors .mcp.json (in your project root)
- ChatGPT BugEzy get_network_errors Settings → Connectors → Advanced → Developer mode
- Claude.ai BugEzy get_network_errors Settings → Connectors → Add custom connector
- LangChain BugEzy get_network_errors pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http bugezy https://bugezy.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.