How to Use the Honeycomb MCP in CrewAI

Q: Can I limit which Honeycomb MCP tools a specific CrewAI agent can access?

Yes, you can use the toolfilter option in MCPServerHTTP to restrict tool exposure. For example, you can give your Monitor Agent read-only access to listtriggers while restricting createmarker to your Coordinator Agent.

Q: What happens if a query times out during a CrewAI execution?

The agent executing getqueryresult will catch the timeout and log it to the shared memory space. Another agent can then take over to retry the query with a broader time window or simplified parameters.

Deploy specialized CrewAI agent teams to monitor Honeycomb telemetry and coordinate autonomous incident response.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Honeycomb MCP to CrewAI

Create your Vinkius account to connect Honeycomb 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 Honeycomb with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Coordinated Telemetry Analysis with CrewAI

This Honeycomb MCP Server allows your CrewAI team to divide and conquer complex performance investigations. While your Monitor Agent runs `list_triggers` to detect anomalies, your Analyst Agent uses `list_datasets` to locate the source dataset. The Analyst Agent then calls `list_dataset_columns` to understand the telemetry schema. By sharing this context in common memory, the crew avoids redundant API calls and pinpoints bugs faster.

Autonomous Query Generation and Execution

The `create_query_specification` tool gives your CrewAI agents the power to construct complex telemetry queries through this MCP Server. A specialized Debugger Agent writes the query parameters based on error logs it receives from other crew members. Once written, the agent executes `run_query` and hands off the execution ID to a Reporter Agent. This division of labor ensures that query creation and result parsing are handled by dedicated, specialized models.

Team-Wide Timeline Documentation

The `create_marker` tool enables your CrewAI operations team to document incident milestones automatically. When the crew confirms a successful mitigation, the Coordinator Agent flags the resolution timestamp. Other agents can verify the annotation by calling `list_markers` to ensure the timeline matches. This automated documentation loop keeps your entire SRE team aligned without requiring manual post-mortem writing.

Setup guide

Set up Honeycomb 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 Honeycomb tools as needed.

crew.py

from crewai import Agent, Task, Crew

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

task = Task(
    description="List recent Honeycomb 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="Honeycomb Analyst",
        goal="Access and analyze Honeycomb data via MCP.",
        backstory="Expert analyst with direct Honeycomb access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Honeycomb 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 Honeycomb. 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 Honeycomb 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 Honeycomb MCP in CrewAI

Your agents use CrewAI's shared memory system to pass the output of `list_dataset_columns`. This prevents multiple agents from hitting Honeycomb rate limits by making duplicate schema requests.

Yes, you can use the `tool_filter` option in `MCPServerHTTP` to restrict tool exposure. For example, you can give your Monitor Agent read-only access to `list_triggers` while restricting `create_marker` to your Coordinator Agent.

You install the crewai tools package and pass your unique Vinkius server endpoint URL in the `mcps` list. The framework automatically registers the tools and makes them available to your configured agents.

The agent executing `get_query_result` will catch the timeout and log it to the shared memory space. Another agent can then take over to retry the query with a broader time window or simplified parameters.

Your Honeycomb API keys are stored securely in Vinkius's ephemeral MCP environment and never exposed to the CrewAI Python runtime. The agents only interact with the sanitized tool definitions, keeping your core credentials isolated.

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