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