signal_start — hookpulse MCP Tool
signal_start
(signal start) is one of 29 tools on the
hookpulse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call signal_start from your client
- Claude Code hookpulse signal_start run in your project directory
- Claude Desktop hookpulse signal_start ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor hookpulse signal_start ~/.cursor/mcp.json
- VS Code hookpulse signal_start .vscode/mcp.json
- Zed hookpulse signal_start ~/.config/zed/settings.json
- Windsurf hookpulse signal_start ~/.codeium/windsurf/mcp_config.json
- Cline hookpulse signal_start ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI hookpulse signal_start ~/.gemini/settings.json
- Grok hookpulse signal_start .mcp.json (in your project root)
- ChatGPT hookpulse signal_start Settings → Connectors → Advanced → Developer mode
- Claude.ai hookpulse signal_start Settings → Connectors → Add custom connector
- LangChain hookpulse signal_start pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hookpulse https://hookpulse.net/mcpOther tools on this server
- list_plans
- buy_plan
- cancel_plan
- api_index
- health
- create_guest
- list_endpoints
- create_endpoint
- create_site
- check_site
- list_sites
- import_crontab
- get_endpoint
- delete_endpoint
- list_events
- ping_ingest
- signal_fail
- signal_exit_code
- ingest_key
- ingest_key_rotate
- ping_slug
- signal_slug
- pricing
- status_feed_url
- status_feed_rotate
- list_templates
- contact
- get_api_x402_check
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.