How to Use the Incident.io MCP in CrewAI

Q: Can I filter Incident.io tools for specific CrewAI agents?

Yes, use the toolfilter parameter in your agent setup. You can give the researcher agent access to listincidents while keeping other tools restricted.

Deploy a specialized incident response crew with CrewAI. Automate triage and on-call escalation without human intervention.

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 CrewAI

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Specialized incident response with CrewAI

Assign a dedicated agent to monitor `list_incidents` while another analyzes severity using `list_severities`. By splitting the work, your crew handles outages faster. This division of labor mimics a human NOC team. One agent gathers the facts, and the other prepares the response plan.

Automated on-call escalation

Your moderator agent can query `list_schedules` and `list_users` to find the right person for a high-priority bug. It takes the manual search out of the equation. When the agent finds the user, it can pass the incident details directly to them. You don't have to touch a thing until the fix is ready.

Incident role and team coordination

Use `list_incident_roles` and `list_teams` to ensure every incident has the correct stakeholders assigned. The agents coordinate these roles to keep your response organized. This keeps your incident metadata clean and accurate. No more missing assignments or confusion about who is responsible for what.

Setup guide

Set up Incident.io MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Incident.io tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Incident.io Analyst",
    goal="Access and analyze Incident.io data via MCP.",
    backstory="Expert analyst with direct Incident.io access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Incident.io transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Incident.io Analyst",
        goal="Access and analyze Incident.io data via MCP.",
        backstory="Expert analyst with direct Incident.io access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Incident.io transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

Yes, use the tool_filter parameter in your agent setup. You can give the researcher agent access to `list_incidents` while keeping other tools restricted.

Pass the server URL to your agent's mcps list. The framework handles the connection, and your agents can start calling the tools immediately.

It does. You can assign the MCP server to a manager agent that delegates specific queries to subordinate workers based on the incident type.

The server uses ephemeral sessions. Your incident history and user records are processed in memory and vanish once the crew completes the task.

If you have a large crew, you might. You should add a custom delay between agent tasks to stay within the API limits for your account.

Use it with your favorite AI tools

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