honeycomb-mcp-server
Honeycomb MCP (Model-Controller-Presenter) Server implementation
Documentation
Honeycomb MCP Server
*Read this in Japanese*
Overview
This server is an interface that uses the Model Context Protocol (MCP) to enable Claude AI to interact with the Honeycomb API.
With this MCP server, Claude AI can perform operations such as retrieving, creating, and updating Honeycomb datasets, queries, events, boards, markers, SLOs, and triggers.
About the Repository
This repository provides a standalone implementation of the Honeycomb MCP server. It integrates Claude AI with Honeycomb to streamline observability and monitoring workflows.
Setup
Prerequisites
- Node.js 18 or higher
- Honeycomb API key
Installation
# Install globally
npm install -g @kajirita2002/honeycomb-mcp-server
# Or use directly with npx
npx @kajirita2002/honeycomb-mcp-serverSetting Environment Variables
# Set environment variables
export HONEYCOMB_API_KEY="your_honeycomb_api_key"MCP Configuration Example
If you're using this MCP server, add the following configuration to your `mcp_config.json` file:
"honeycomb": {
"command": "npx",
"args": ["-y", "@kajirita2002/honeycomb-mcp-server"],
"env": {
"HONEYCOMB_API_KEY": "your_honeycomb_api_key"
}
}Starting the Server
# Start the server
npm startAvailable Tools
This MCP server provides the following tools:
Authentication
1. `honeycomb_auth`
Dataset Management
1. `honeycomb_datasets_list`
2. `honeycomb_dataset_get`
Column Management
1. `honeycomb_columns_list`
Query Management
1. `honeycomb_query_create`
2. `honeycomb_query_get`
3. `honeycomb_query_result_create`
4. `honeycomb_query_result_get`
Dataset Definitions
1. `honeycomb_dataset_definitions_list`
Board Management
1. `honeycomb_boards_list`
2. `honeycomb_board_get`
Example Usage
Here's an example of Claude using this MCP server to list datasets and run a query:
[Claude] Can you show me the available datasets in our Honeycomb environment?
[User] Sure, I'd like to see what datasets we have in Honeycomb.
[Claude] I'll list all the available datasets in your Honeycomb environment.
I'll use the honeycomb_datasets_list tool...
Here are your available datasets:
- production-metrics (slug: prod-metrics)
- staging-services (slug: staging-svc)
- application-logs (slug: app-logs)
Which dataset would you like to explore further?
[User] Let's look at the production-metrics dataset.
[Claude] I'll get details about the production-metrics dataset using honeycomb_dataset_get with the slug "prod-metrics"...
Now I'll create and run a query to show the average response time over the last 24 hours.
I'll use honeycomb_query_create and then honeycomb_query_result_create...
Here are the results showing the average response time trend:
[Query results visualization description]
Input:
{
"datasetSlug": "application-monitoring",
"data": {
"service": "api-gateway",
"duration_ms": 45.2,
"status_code": 200,
"endpoint": "/users",
"method": "GET"
}
}
Event created successfully! You can now see this event in the Honeycomb UI under the Application Monitoring dataset.
[Claude] I can also create a query to analyze this data. Let me create a query that shows the average duration by endpoint.
I'll use the honeycomb_query_create tool:
Input:
{
"datasetSlug": "application-monitoring",
"query": {
"calculations": [
{
"op": "AVG",
"column": "duration_ms"
}
],
"breakdowns": ["endpoint"],
"time_range": 3600
}
}Common Integration Patterns
1. Observability Automation
[User] Claude, please help me set up a new SLO for API response times.
[Claude] I can help with that. Let me create an SLO to track API response times.
I'll use honeycomb_slo_create with these parameters:
{
"datasetSlug": "production-api",
"name": "API Response Time SLO",
"description": "Tracks response time for critical API endpoints",
"sli": {
"alias": "Response Time =",
"value": 500
}
],
"breakdowns": ["service", "endpoint"],
"time_range": 3600,
"granularity": 60
}
}Creating dataset "Application Monitoring" with the description "Monitoring for our production application"...
[Claude uses honeycomb_datasets_create]
The dataset has been successfully created! Now we can add events to it.
Would you like me to create a sample event in the dataset to test it?
[User] Yes, please add a sample event.
[Claude] I'll add a sample event to the "Application Monitoring" dataset.
[Claude uses honeycomb_event_create]
Success! I've added a sample event to your "Application Monitoring" dataset with the following data:
{
"service": "api-server",
"message": "User login successful",
"duration_ms": 45,
"status_code": 200,
"endpoint": "/api/login",
"timestamp": "2025-03-25T14:30:00Z"
}
This event represents a successful user login operation that took 45ms to complete.
You can now view this event in your Honeycomb dashboard and start building queries to analyze your data.
## Error Handling
This MCP server returns error information in a consistent format. When an error occurs, the following structure is returned:{
"error": {
"message": "Detailed error description",
"code": "ERROR_CODE"
}
}
### Common Error Codes
- `AUTH_ERROR`: Authentication failed. Check your API key.
- `NOT_FOUND`: The requested resource was not found.
- `INVALID_PARAMETER`: One or more parameters are invalid.
- `RATE_LIMIT`: Honeycomb API rate limit has been reached.
- `SERVER_ERROR`: Internal server error occurred.
### Troubleshooting Tips
1. **Authentication Issues**
- Ensure your `HONEYCOMB_API_KEY` is set correctly
- Verify the API key has appropriate permissions
2. **Dataset Not Found**
- Confirm that the dataset slug is correct (check for typos)
- Make sure the dataset exists in your Honeycomb account
3. **Query Execution Issues**
- Validate that query parameters are formatted correctly
- Check column names in queries match those in your dataset
## Contributing
Contributions to the Honeycomb MCP server are welcome! Here's how you can contribute:
### Development Setup
1. Fork the repository
2. Clone your forkgit clone https://github.com/your-username/honeycomb-mcp-server.git
3. Install dependenciesnpm install
4. Make your changes
5. Run the buildnpm run build
6. Test your changes locally
### Pull Request Process
1. Create a feature branchgit checkout -b feat-your-feature-name
2. Commit your changes following [Conventional Commits](https://www.conventionalcommits.org/) formatgit commit -m "feat: add new feature"
3. Push to your forkgit push origin feat-your-feature-name
4. Open a Pull Request
### Coding Standards
- Use TypeScript for all new code
- Follow the existing code style
- Add comments for public APIs
- Write tests for new functionality
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.Frequently asked questions
What is honeycomb-mcp-server?
honeycomb-mcp-server is Honeycomb MCP (Model-Controller-Presenter) Server implementation
How do I install honeycomb-mcp-server?
Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.
Is honeycomb-mcp-server open source?
Yes — it is hosted on GitHub at https://github.com/kajirita2002/honeycomb-mcp-server and has 2 stars.
Related MCP tools
The all-in-one Desktop & Docker AI application with built-in RAG, AI agents, No-code agent builder, MCP compatibility, and more.
An AI-powered task-management system you can drop into Cursor, Lovable, Windsurf, Roo, and others. Built for the Model Context Protocol to enhance AI capabiliti
Fay是一个帮助数字人(2.5d、3d、移动、pc、网页)或大语言模型(openai兼容、deepseek)连通业务系统的mcp框架。 JavaScript-based implementation. Trusted by 12000+ developers.
CTTF: MCP integration between Cursor and Figma, allowing Cursor Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients. JavaScript-based implementation.
This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities JavaScript-based implementation.
Run your own MCP server? See who uses it and what to fix.
Measure it with TrackMCP