INDIVIDUAL MCP TOOL
spike_list_services
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}.
LIVE ENDPOINT
https://spikesh.usefulapi.io/mcp
Connect to this endpoint to inspect the live schema for spike_list_services and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.spikesh-mcp]
url = "https://spikesh.usefulapi.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"spikesh-mcp": {
"type": "http",
"url": "https://spikesh.usefulapi.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: spikesh-mcp
Remote MCP URL: https://spikesh.usefulapi.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"spikesh-mcp": {
"url": "https://spikesh.usefulapi.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"spikesh-mcp": {
"type": "http",
"url": "https://spikesh.usefulapi.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "spikesh-mcp",
"transport": "streamable-http",
"url": "https://spikesh.usefulapi.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
spike_list_teams— List all teams in the Spike.spike_list_incidents— List incidents for a team — {incidents:[.spike_list_triggered_incidents— List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue.spike_list_acknowledged_incidents— List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team.spike_get_incident— Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}.spike_get_incident_activity_log— Get the chronological activity log for an incident — {incident, activities:[.spike_list_on_calls— List a team's on-call schedules — {oncalls:[.spike_get_on_call— Get one on-call schedule by id — {oncall:{_id, name, timezone, teams, users, activeShift, renderedShifts}}.