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