How do I find my Honeycomb API Key?

Log in to Honeycomb, go to **Team Settings**, and navigate to the **API Keys** section. You will be able to generate and copy your Team API Key from there. Ensure you also note your account's region.

Which region should I select?

If your browser URL starts with `ui.eu1.honeycomb.io`, select **EU**. Otherwise, select **US**. Using the correct region is required for the integration to connect to the right API cluster.

Can I run a query and get the data back?

Yes! Use the `run_query` tool with a valid query ID. It will return a result ID, which you can then pass to the `get_query_result` tool once the analysis is complete.

Is the integration secure for telemetry data?

Absolutely. The integration uses official Honeycomb Team API keys over HTTPS. Your credentials and queried data are encrypted and stored securely within the Vinkius Cloud infrastructure.

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

Name: Honeycomb
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Honeycomb through Vinkius, pass the Edge URL in the `mcps` parameter and every Honeycomb 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="Honeycomb Specialist",
    goal="Help users interact with Honeycomb effectively",
    backstory=(
        "You are an expert at leveraging Honeycomb 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 Honeycomb "
        "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 Honeycomb MCP Server

Connect your Honeycomb.io observability platform to any AI agent and take full control of your telemetry data, query specifications, and incident markers through natural conversation.

When paired with CrewAI, Honeycomb becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Honeycomb 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

Dataset Oversight — List all event sources, retrieve detailed metadata, and monitor last access times for your datasets.
Query Management — Define new query specifications and execute them to retrieve granular performance insights.
Marker Automation — Create timeline annotations (e.g., for deployments or outages) to contextualize your data visualization.
Schema Insights — List and inspect columns within specific datasets to understand your event structure.
Team Collaboration — Access shared boards and retrieve information about your Honeycomb team configuration.
Incident Analysis — Use AI to run complex queries and retrieve results for rapid troubleshooting and RCA.

The Honeycomb 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 Honeycomb to CrewAI via MCP

Follow these steps to integrate the Honeycomb 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 Honeycomb

Why Use CrewAI with the Honeycomb MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Honeycomb 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

Honeycomb + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Honeycomb 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 Honeycomb, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Honeycomb 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 Honeycomb against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Honeycomb MCP Tools for CrewAI (12)

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

create_marker

Pass details as a JSON string in "body_json" (requires message). Use "__all__" for team-wide markers. Create a new marker (e.g., deploy, maintenance) on a dataset timeline

create_query_specification

Pass the specification as a JSON string in "query_json". Returns a query ID for execution. Create a new query specification for a dataset

get_dataset_details

Get metadata for a specific dataset

get_query_result

Retrieve the results of an executed query

get_team_details

Retrieve information about the Honeycomb team

list_dataset_columns

List all columns (fields) defined in a specific dataset

list_datasets

Use this to find the "slug" required for markers and queries. List all datasets in your Honeycomb team

list_honeycomb_boards

List all boards (dashboards) shared with the team

list_markers

List markers (annotations) for a dataset

list_queries

List query specifications for a specific dataset

list_triggers

List triggers (alerts) defined for a dataset

run_query

Poll for results using "get_query_result" with the returned result ID. Execute a query specification and return a result ID

Example Prompts for Honeycomb in CrewAI

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

"List all datasets and find one related to 'payment-gateway'."

"Create a marker on all datasets: 'Deploy v2.4.0 started'."

"Execute query ID 'q_99283' for the 'main-api' dataset."

Troubleshooting Honeycomb MCP Server with CrewAI

Common issues when connecting Honeycomb 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.

Honeycomb + CrewAI FAQ

Common questions about integrating Honeycomb 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.