signal_exit_code — hookpulse MCP Tool
signal_exit_code
(signal exit code) is one of 41 tools on the
hookpulse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call signal_exit_code from your client
- Claude Code hookpulse signal_exit_code run in your project directory
- Claude Desktop hookpulse signal_exit_code ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor hookpulse signal_exit_code ~/.cursor/mcp.json
- VS Code hookpulse signal_exit_code .vscode/mcp.json
- Zed hookpulse signal_exit_code ~/.config/zed/settings.json
- Windsurf hookpulse signal_exit_code ~/.codeium/windsurf/mcp_config.json
- Cline hookpulse signal_exit_code ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI hookpulse signal_exit_code ~/.gemini/settings.json
- Grok hookpulse signal_exit_code .mcp.json (in your project root)
- ChatGPT hookpulse signal_exit_code Settings → Connectors → Advanced → Developer mode
- Claude.ai hookpulse signal_exit_code Settings → Connectors → Add custom connector
- LangChain hookpulse signal_exit_code pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hookpulse https://hookpulse.net/mcpOther tools on this server
- list_environments
- create_environment
- get_environment
- create_device_input
- list_device_inputs
- get_device_input_setup
- list_device_input_history
- get_device_input_batch
- delete_device_input
- set_device_input_active
- list_input_fleet
- report_environment
- list_collections
- create_collection
- get_collection_series
- update_collection
- delete_collection
- update_environment
- delete_environment
- api_index
- health
- create_guest
- list_endpoints
- create_endpoint
- import_crontab
- get_endpoint
- delete_endpoint
- list_events
- ping_ingest
- signal_start
- signal_fail
- ingest_key
- ingest_key_rotate
- ping_slug
- billing
- status_feed_url
- status_feed_rotate
- list_templates
- contact
- pricing
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.