Incident.io MCP Server for Cline 10 tools — connect in under 2 minutes
Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Incident.io through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Incident.io and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"incidentio": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Incident.io MCP Server
Empower your AI agents to manage your incident response lifecycle with Incident.io. This MCP server allows you to list and retrieve incidents, manage roles and types, track custom fields, and view on-call schedules directly through the Incident.io API. Ideal for automating SRE workflows and incident coordination.
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Incident.io tool calls without waiting for prompts between steps. Connect 10 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
The Incident.io MCP Server exposes 10 tools through the Vinkius. Connect it to Cline in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Incident.io to Cline via MCP
Follow these steps to integrate the Incident.io MCP Server with Cline.
Open Cline MCP Settings
Click the MCP Servers icon in the Cline sidebar panel
Add remote server
Click "Add MCP Server" and paste the configuration above
Enable the server
Toggle the server switch to ON
Start using Incident.io
Ask Cline: "Using Incident.io, help me...". 10 tools available
Why Use Cline with the Incident.io MCP Server
Cline provides unique advantages when paired with Incident.io through the Model Context Protocol.
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Incident.io + Cline Use Cases
Practical scenarios where Cline combined with the Incident.io MCP Server delivers measurable value.
Autonomous feature building: tell Cline to fetch data from Incident.io and scaffold a complete module with types, handlers, and tests
Codebase refactoring: use Incident.io tools to validate live data while Cline restructures your code to match updated schemas
Automated testing: Cline fetches real responses from Incident.io and generates snapshot tests or mocks based on actual payloads
Incident response: query Incident.io for real-time status and let Cline generate hotfix patches based on the findings
Incident.io MCP Tools for Cline (10)
These 10 tools become available when you connect Incident.io to Cline via MCP:
get_incident
Retrieves details for a specific incident
list_catalog_types
Lists all defined catalog types
list_custom_fields
Lists all defined custom fields
list_incident_roles
Lists all defined incident roles
list_incident_types
Lists all defined incident types
list_incidents
Lists all incidents
list_schedules
Lists all on-call schedules
list_severities
Lists all defined incident severities
list_teams
Lists all teams
list_users
Lists all users
Example Prompts for Incident.io in Cline
Ready-to-use prompts you can give your Cline agent to start working with Incident.io immediately.
"List all ongoing incidents in Incident.io."
"Show me the on-call schedules for this week."
"Check the details for incident ID 'abc-123'."
Troubleshooting Incident.io MCP Server with Cline
Common issues when connecting Incident.io to Cline through the Vinkius, and how to resolve them.
Server shows error in sidebar
Incident.io + Cline FAQ
Common questions about integrating Incident.io MCP Server with Cline.
How does Cline connect to MCP servers?
Can Cline run MCP tools without approval?
Does Cline support multiple MCP servers at once?
Connect Incident.io with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Incident.io to Cline
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.