Skip to main content
Connect Honeycomb to any AI agent that supports the Model Context Protocol (MCP) so it can query your telemetry, investigate issues, and answer questions using your live Honeycomb data. This guide covers the fastest way to connect, manual configuration for specific clients, and authentication with an API key.
If you need to get data into Honeycomb using sample data, real instrumentation, or connecting to an existing pipeline, start with Send data with AI instead.

Before you begin

Make sure that:

Put your agent to work

Run the prompt associated with your region in your AI agent:

Connect to the Honeycomb MCP server (US)

Once your agent authenticates, it can query your telemetry, investigate issues, and answer questions using your live Honeycomb data. For the list of tools that Honeycomb MCP exposes to your agent, visit the MCP Tools Reference.

Connect manually

For step-by-step configuration instructions, select your client:
Connect Amazon Q Developer to Honeycomb MCP using the qchat CLI:
  1. Run the command associated with your region in your terminal:
  2. Run any MCP tool. Authenticate and grant the requested permissions to finish connecting.
Want your agent to send data too? Send data with AI walks through running guided onboarding to help you instrument your application.

Authenticate with an API key

If you are building autonomous or unattended agents and cannot use OAuth, then you can authenticate with an API key. Only team owners can generate an API key.
Prefer OAuth in most use cases. Use an API key only when your agent cannot support interactive login.
1

Generate an API key in Honeycomb

  1. Log in to your Honeycomb account.
  2. Navigate to Account > Team Settings > API Keys.
  3. Select Create Management API Key.
  4. Name your key (for example, “MCP Integration”).
  5. Choose the Model Context Protocol and Environments scopes, then grant permissions:
    • Read: Required for all Honeycomb MCP operations. Be sure to grant read for both MCP and Environments.
    • Write: Required for tools that create or update Honeycomb resources, including Boards, Triggers, SLOs, notification/alert recipients, and Canvas investigations. To explore the complete list of write tools, visit the MCP Tools Reference.
  6. Copy the Key ID and Key Secret, and store them somewhere safe. You will need them later, and you won’t be able to see them again.
2

Add your API key to your agent

The exact configuration process varies by agent, but here is an example configuration mcp.json snippet used by agents like Claude Code or Cursor:
Be sure to use the appropriate endpoint for your region, and replace KEY_ID and SECRET_KEY with your actual key values.
Pay attention to formatting, including spacing and colon (:) characters.If your tool cannot parse the Authorization header correctly, try putting the Bearer prefix directly in the environment variable: "HONEYCOMB_API_KEY": "Bearer KEY_ID:SECRET_KEY".
As a security best practice, make sure that keys being used for MCP integrations do not carry any other scopes, and that you do not commit them to source control.
3

Confirm the connection

Once connected, test by asking your agent to list available tools or fetch available teams and environments. You should get results if your key and permissions are set up correctly.

Next steps

Continue your MCP journey:
  • Example Use Cases: Explore real-world use cases and tips for working with Honeycomb via MCP.
  • Tools Reference: Learn about the tools Honeycomb MCP exposes to AI agents.
  • Troubleshooting: Fix common MCP configuration and connection issues.