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 LlamaIndex 12 tools — connect in under 2 minutes

Name: FireHydrant
Availability: InStock
Author: Vinkius

docs.llamaindex.ai/en/stable/module_guides/tools/mcp

Built by Vinkius GDPR 12 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add FireHydrant as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

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

import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to FireHydrant. "
            "You have 12 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in FireHydrant?"
    )
    print(response)

asyncio.run(main())

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.

LlamaIndex agents combine FireHydrant tool responses with indexed documents for comprehensive, grounded answers. Connect 12 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

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 LlamaIndex 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 LlamaIndex via MCP

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

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save to agent.py and run: python agent.py

Explore tools

The agent discovers 12 tools from FireHydrant

Why Use LlamaIndex with the FireHydrant MCP Server

LlamaIndex provides unique advantages when paired with FireHydrant through the Model Context Protocol.

Data-first architecture: LlamaIndex agents combine FireHydrant tool responses with indexed documents for comprehensive, grounded answers

Query pipeline framework lets you chain FireHydrant tool calls with transformations, filters, and re-rankers in a typed pipeline

Multi-source reasoning: agents can query FireHydrant, a vector store, and a SQL database in a single turn and synthesize results

Observability integrations show exactly what FireHydrant tools were called, what data was returned, and how it influenced the final answer

FireHydrant + LlamaIndex Use Cases

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

Hybrid search: combine FireHydrant real-time data with embedded document indexes for answers that are both current and comprehensive

Data enrichment: query FireHydrant to augment indexed data with live information before generating user-facing responses

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying FireHydrant for fresh data

Analytical workflows: chain FireHydrant queries with LlamaIndex's data connectors to build multi-source analytical reports

FireHydrant MCP Tools for LlamaIndex (12)

These 12 tools become available when you connect FireHydrant to LlamaIndex 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 LlamaIndex

Ready-to-use prompts you can give your LlamaIndex 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 LlamaIndex

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

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

FireHydrant + LlamaIndex FAQ

Common questions about integrating FireHydrant MCP Server with LlamaIndex.

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query FireHydrant tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.