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