How to Use the Incident.io MCP in Claude

Q: How do I connect Incident.io to Claude Desktop?

Open your claudedesktopconfig.json file and add the server configuration under the mcpServers key. For the browser version of Claude, paste the Vinkius URL directly into the Integrations settings. Restart the app, and you will see the tools ready in your chat input.

Q: Can I run custom queries on Incident.io via Claude Desktop?

Yes. You can instruct your agent to run listincidents combined with listcustomfields to filter for specific tags. The desktop app executes these calls locally, passing the filtered results directly into your active prompt context.

Q: How does this Incident.io MCP Server handle on-call schedules in Claude Desktop?

It queries your live roster using listschedules to find active responders. Your AI client then uses listusers to pull their contact info, letting you coordinate handoffs right from the chat box.

Triage production outages directly inside Claude Desktop using live Incident.io data.

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 Desktop

Create your Vinkius account to connect Incident.io to Claude Desktop 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 Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Triage incidents from your desktop chat

The `list_incidents` tool puts your active production issues directly into your Claude Desktop workspace. Instead of hunting through browser tabs during a high-severity outage, you ask your AI client to pull the current fire. It queries the API, grabs the details with `get_incident`, and shows you exactly what is broken right now. This setup runs locally via stdio or connects through a remote URL on claude.ai. You get immediate access to custom metadata using `list_custom_fields` to filter out the noise. No more copying and pasting JSON payloads between your terminal and the chat window.

Find on-call responders instantly with Claude Desktop

The `list_schedules` tool identifies who is currently carrying the pager without forcing you to open a separate dashboard. Your AI client matches active alerts against your team rosters using `list_users` and `list_teams`. You know exactly who to ping within seconds of an escalation. Because Claude Desktop can run tasks locally, it cross-references these schedules with your local configuration files. It uses `list_incident_roles` to verify who should take the lead on a specific system failure. This cuts down the time spent looking for the right engineer during a 3 AM wake-up call.

Audit incident metadata using this MCP Server

The `list_severities` tool lets your agent categorize incoming issues based on your team's specific definitions. You can audit historical alerts by pairing this with `list_incident_types` directly in the prompt. It maps out how your organization classifies downtime without manual data entry. Pulling catalog structures is straightforward with `list_catalog_types`. Your AI client uses this MCP Server to analyze how your metadata fields align with actual incident frequencies. You spot patterns in your response history without writing custom python scripts.

Setup guide

Set up Incident.io MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Incident.io MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Incident.io MCP configuration

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

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under incidentio-mcp.

json

{
  "mcpServers": {
    "incidentio-mcp": {
      "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 Desktop

Open your `claude_desktop_config.json` file and add the server configuration under the `mcpServers` key. For the browser version of Claude, paste the Vinkius URL directly into the Integrations settings. Restart the app, and you will see the tools ready in your chat input.

Yes. You can instruct your agent to run `list_incidents` combined with `list_custom_fields` to filter for specific tags. The desktop app executes these calls locally, passing the filtered results directly into your active prompt context.

It queries your live roster using `list_schedules` to find active responders. Your AI client then uses `list_users` to pull their contact info, letting you coordinate handoffs right from the chat box.

You need an active API key from your Incident.io workspace with read permissions. The MCP Server uses this token to run tools like `list_teams` and retrieve your operational data.

Your incident logs, on-call schedules, and user directories remain secure. Vinkius runs the server in an isolated sandbox, and Claude Desktop communicates with it via a secure local or HTTPS connection without storing your API tokens on external servers.

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