The Vibe OnCall MCP server lets coding agents — such as Claude Code and Cursor — connect directly to your organization's incidents, alerts, and on-call data through the Model Context Protocol (MCP). It is read-only and uses your existing Vibe OnCall API key.

Endpoint

<https://api-prod.vibraniumlabs.ai/mcp>

The endpoint uses the Streamable HTTP transport (JSON-RPC) and works with any MCP-compatible client.

Authentication

The MCP server uses the same API key as the Public API. Provide it as a bearer token:

Authorization: Bearer vlk_your_api_key_here

See API Key Management for instructions on creating and managing API keys. Requests without a valid key receive a 401 Unauthorized response.

Connecting your client

Claude Code

claude mcp add --transport http vibe-oncall \
  <https://api-prod.vibraniumlabs.ai/mcp> \
  --header "Authorization: Bearer vlk_your_api_key"

Cursor — add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "vibe-oncall": {
      "url": "<https://api-prod.vibraniumlabs.ai/mcp>",
      "headers": { "Authorization": "Bearer vlk_your_api_key" }
    }
  }
}

After connecting, your agent can discover and call the tools below.

Available tools

Tool Description
list_incidents List incidents for your organization. Filter by status, severity, and free-text search.
get_incident Get a single incident, including its timeline and postmortems.
list_alerts List alerts. Filter by status, severity, provider, team, service, search, and creation time.
get_alert Get a single alert, including labels, notes, lifecycle events, and linked incidents.
list_teams List your organization's teams with their names and short IDs.
who_is_on_call Show who is currently on call for a team, by team short ID.
list_services List services in your service catalog and their owning teams.