monitor_update — searchnapply MCP Prompt
monitor_update
is one of 3 prompts on the
searchnapply
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke monitor_update from your client
- Claude Code searchnapply Prompt/monitor_update run in your project directory
- Claude Desktop searchnapply Prompt/monitor_update ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor searchnapply Prompt/monitor_update ~/.cursor/mcp.json
- VS Code searchnapply Prompt/monitor_update .vscode/mcp.json
- Zed searchnapply Prompt/monitor_update ~/.config/zed/settings.json
- Windsurf searchnapply Prompt/monitor_update ~/.codeium/windsurf/mcp_config.json
- Cline searchnapply Prompt/monitor_update ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI searchnapply Prompt/monitor_update ~/.gemini/settings.json
- Grok searchnapply Prompt/monitor_update .mcp.json (in your project root)
- ChatGPT searchnapply Prompt/monitor_update Settings → Connectors → Advanced → Developer mode
- Claude.ai searchnapply Prompt/monitor_update Settings → Connectors → Add custom connector
- LangChain searchnapply Prompt/monitor_update pip install langchain-mcp-adapters
Other prompts on this server
searchnapply also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.