honeycomb-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HONEYCOMB_API_KEY | Yes | Your Honeycomb API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| honeycomb_authB | Get authentication information and validate API key |
| honeycomb_datasets_listB | List all datasets in the environment |
| honeycomb_dataset_getC | Get information about a specific dataset |
| honeycomb_datasets_createC | Create a new dataset |
| honeycomb_datasets_updateC | Update an existing dataset |
| honeycomb_columns_listC | List all columns in a dataset |
| honeycomb_query_createC | Create a new query for a dataset |
| honeycomb_query_getC | Get information about a specific query |
| honeycomb_query_result_createC | Create a new query result (run a query) |
| honeycomb_query_result_getC | Get results of a specific query execution |
| honeycomb_event_createC | Create a new event in a dataset |
| honeycomb_batch_event_createC | Create multiple events in a dataset in a single batch |
| honeycomb_boards_listB | List all boards |
| honeycomb_board_getC | Get information about a specific board |
| honeycomb_board_createC | Create a new board |
| honeycomb_board_updateC | Update an existing board |
| honeycomb_board_deleteB | Delete a board |
| honeycomb_markers_listC | List all markers for a dataset |
| honeycomb_marker_createC | Create a new marker for a dataset |
| honeycomb_marker_getC | Get information about a specific marker |
| honeycomb_marker_updateC | Update an existing marker |
| honeycomb_marker_deleteC | Delete a marker |
| honeycomb_slos_listC | List all SLOs for a dataset |
| honeycomb_slo_getC | Get information about a specific SLO |
| honeycomb_slo_createC | Create a new SLO for a dataset |
| honeycomb_slo_updateC | Update an existing SLO |
| honeycomb_triggers_listC | List all triggers for a dataset |
| honeycomb_trigger_getC | Get information about a specific trigger |
| honeycomb_trigger_createC | Create a new trigger for a dataset |
| honeycomb_trigger_updateC | Update an existing trigger |
| honeycomb_trigger_deleteC | Delete a trigger |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 31 tools
Every tool has a clearly distinct purpose targeting specific resources (boards, datasets, markers, queries, SLOs, triggers) and actions (create, get, list, update, delete). The descriptions explicitly differentiate between operations like query creation vs. query execution, and batch vs. single event creation, leaving no ambiguity.
All tools follow a consistent pattern of honeycomb_resource_action or honeycomb_resources_action (e.g., honeycomb_board_get, honeycomb_boards_list). The naming is uniformly snake_case with clear verb-noun combinations, making it highly predictable and readable throughout the set.
With 31 tools, the count feels heavy for a single server, potentially overwhelming for agents. While it covers multiple domains (boards, datasets, markers, queries, SLOs, triggers), it might benefit from consolidation or modularization, as typical well-scoped servers have 3-15 tools.
The tool surface provides complete CRUD/lifecycle coverage for each resource type (boards, datasets, markers, SLOs, triggers) and includes essential operations like query execution and batch event creation. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.