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