monitor_my_box — Paw Pulse MCP Prompt
monitor_my_box
is one of 1 prompt on the
Paw Pulse
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke monitor_my_box from your client
- Claude Code Paw Pulse Prompt/monitor_my_box run in your project directory
- Claude Desktop Paw Pulse Prompt/monitor_my_box ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Paw Pulse Prompt/monitor_my_box ~/.cursor/mcp.json
- VS Code Paw Pulse Prompt/monitor_my_box .vscode/mcp.json
- Zed Paw Pulse Prompt/monitor_my_box ~/.config/zed/settings.json
- Windsurf Paw Pulse Prompt/monitor_my_box ~/.codeium/windsurf/mcp_config.json
- Cline Paw Pulse Prompt/monitor_my_box ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Paw Pulse Prompt/monitor_my_box ~/.gemini/settings.json
- Grok Paw Pulse Prompt/monitor_my_box .mcp.json (in your project root)
- ChatGPT Paw Pulse Prompt/monitor_my_box Settings → Connectors → Advanced → Developer mode
- Claude.ai Paw Pulse Prompt/monitor_my_box Settings → Connectors → Add custom connector
- LangChain Paw Pulse Prompt/monitor_my_box pip install langchain-mcp-adapters
Paw Pulse also offers 1 resource — 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 16 October 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.