spike_get_incident_activity_log — Spike.sh MCP by usefulapi MCP Tool
spike_get_incident_activity_log
(spike get incident activity log) is one of 16 tools on the
Spike.sh MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call spike_get_incident_activity_log from your client
- Claude Code Spike.sh MCP by usefulapi spike_get_incident_activity_log run in your project directory
- Claude Desktop Spike.sh MCP by usefulapi spike_get_incident_activity_log ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Spike.sh MCP by usefulapi spike_get_incident_activity_log ~/.cursor/mcp.json
- VS Code Spike.sh MCP by usefulapi spike_get_incident_activity_log .vscode/mcp.json
- Zed Spike.sh MCP by usefulapi spike_get_incident_activity_log ~/.config/zed/settings.json
- Windsurf Spike.sh MCP by usefulapi spike_get_incident_activity_log ~/.codeium/windsurf/mcp_config.json
- Cline Spike.sh MCP by usefulapi spike_get_incident_activity_log ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Spike.sh MCP by usefulapi spike_get_incident_activity_log ~/.gemini/settings.json
- Grok Spike.sh MCP by usefulapi spike_get_incident_activity_log .mcp.json (in your project root)
- ChatGPT Spike.sh MCP by usefulapi spike_get_incident_activity_log Settings → Connectors → Advanced → Developer mode
- Claude.ai Spike.sh MCP by usefulapi spike_get_incident_activity_log Settings → Connectors → Add custom connector
- LangChain Spike.sh MCP by usefulapi spike_get_incident_activity_log pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp
Other tools on this server
- spike_list_teams
- spike_list_incidents
- spike_list_triggered_incidents
- spike_list_acknowledged_incidents
- spike_get_incident
- spike_list_on_calls
- spike_get_on_call
- spike_who_is_on_call_next
- spike_list_escalations
- spike_get_escalation
- spike_list_services
- spike_get_service
- spike_acknowledge_incidents
- spike_resolve_incidents
- spike_set_incident_priority
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.