How to Use the Incident.io MCP in Claude Code

Q: Can I use Incident.io with Claude Code in CI?

Yes. Since it runs headless, you can include listincidents checks in your deployment scripts to gate releases during active outages.

Q: What is the Incident.io tool limit in Claude Code?

There is no hard limit on tool usage. You can query listusers or listteams as often as your API rate limits allow.

Claude Code runs headless incident checks against Incident.io, perfect for your CI/CD pipelines and terminal workflows.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Incident.io MCP to Claude Code

Create your Vinkius account to connect Incident.io to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Incident.io with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Terminal-based incident monitoring

Run `list_incidents` directly from your terminal using Claude Code. It pipes the output into your shell, letting you grep for specific error codes or teams. It’s built for DevOps engineers who want to check the status of an outage without ever opening a browser window.

Claude Code manages on-call schedules

Need to know who is on call? Claude Code calls `list_schedules` and returns the output to your CLI session instantly. This helps you script automated paging or status reports directly from your terminal environment.

Verify incident severities via CLI

Use Claude Code to check `list_severities` before you trigger an automated response. It ensures your script reacts only to the levels you define. This keeps your terminal-based automation precise and prevents unnecessary noise during minor incidents.

Setup guide

Set up Incident.io MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see incidentio-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Incident.io transactions." It will automatically discover and invoke the available Incident.io tools.

Terminal

claude mcp add --transport http incidentio-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Incident.io MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

{
  "mcpServers": {
    "incidentio-mcp": {
      "type": "url",
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Incident.io. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Incident.io now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Incident.io MCP in Claude Code

You install it using the claude mcp add command. It connects to the Vinkius endpoint and starts fetching data via the tools you select.

Yes. Since it runs headless, you can include `list_incidents` checks in your deployment scripts to gate releases during active outages.

No. The server keeps data in memory for the duration of the command. Once the process ends, the incident details are discarded.

There is no hard limit on tool usage. You can query `list_users` or `list_teams` as often as your API rate limits allow.

The server uses token-based auth for every request. Your incident records are transmitted over encrypted channels and never logged to disk.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript

Mastra AI sdk-typescript

Start using the Incident.io MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Get started