How do I declare a new incident using the agent?

You can use the 'create_incident' tool. Simply provide a name and optionally a summary and severity level. The agent will trigger the declaration in FireHydrant and return the new incident details.

Can I see recent infrastructure changes using this server?

Yes! The 'list_change_events' tool retrieves a history of recent changes. This is extremely useful for identifying potential root causes during an active incident investigation.

How do I add a status update to an ongoing incident?

Use the 'add_incident_note' tool. You'll need the Incident ID and the text of your update. The note will be immediately posted to the incident's timeline for all responders to see.

FireHydrant MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: FireHydrant
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to FireHydrant through Vinkius, pass the Edge URL in the `mcps` parameter and every FireHydrant tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="FireHydrant Specialist",
    goal="Help users interact with FireHydrant effectively",
    backstory=(
        "You are an expert at leveraging FireHydrant tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in FireHydrant "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 FireHydrant MCP Server

Connect your FireHydrant account to any AI agent and automate your incident management workflows through the Model Context Protocol (MCP). FireHydrant provides a comprehensive platform for declaring incidents, managing service catalogs, and coordinating team responses. Now, you can manage your site reliability and incident response directly through natural conversation.

When paired with CrewAI, FireHydrant becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call FireHydrant tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Incident Management — Declare new incidents, list active ones, and update milestones or fields instantly.
Service Catalog — Access and list all defined services to understand impact and dependencies during an outage.
Team Coordination — List and manage responder teams to ensure the right people are assigned to every incident.
Timeline Updates — Post notes and status updates directly to an incident's timeline from your chat interface.
Runbook Execution — List active runbooks to understand the automated workflows available for your response.
Post-Incident Analysis — Retrieve retrospectives and post-incident reviews to facilitate learning and improvement.
Change Tracking — List change events to identify recent infrastructure or code changes that might have triggered an incident.

The FireHydrant MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI 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 FireHydrant to CrewAI via MCP

Follow these steps to integrate the FireHydrant MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from FireHydrant

Why Use CrewAI with the FireHydrant MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with FireHydrant through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

FireHydrant + CrewAI Use Cases

Practical scenarios where CrewAI combined with the FireHydrant MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries FireHydrant for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries FireHydrant, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain FireHydrant tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries FireHydrant against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

FireHydrant MCP Tools for CrewAI (12)

These 12 tools become available when you connect FireHydrant to CrewAI via MCP:

add_incident_note

Add note to incident

create_incident

Create a new incident

get_incident

Get incident details

get_service

Get service details

get_team

Get team details

list_change_events

List change events

list_incidents

List incidents

list_retrospectives

List retrospectives

list_runbooks

List active runbooks

list_services

List service catalog

list_teams

List responder teams

update_incident

Update an incident

Example Prompts for FireHydrant in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with FireHydrant immediately.

"List all currently active incidents in FireHydrant."

"Declare a new sev-2 incident: 'Redis Connection Spikes'."

"Add a note to incident 'inc_123': 'Investigating potential cache invalidation issue'."

Troubleshooting FireHydrant MCP Server with CrewAI

Common issues when connecting FireHydrant to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

FireHydrant + CrewAI FAQ

Common questions about integrating FireHydrant MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.