Enables fetching and analyzing error data from Honeybadger error tracking service, allowing users to list recent faults, get detailed information on specific errors, retrieve error occurrences, and receive AI-generated analysis with fix suggestions.
Provides integration with Node.js applications, allowing for error tracking and debugging of Node.js-based projects through the Honeybadger error monitoring service.
Honeybadger MCP Server Setup Guide
This MCP server integrates Honeybadger error tracking with Cursor IDE, allowing you to fetch and analyze errors directly from your development environment.
Prerequisites
- Node.js 18+ installed
- Honeybadger account with API access
- Cursor IDE with MCP support
Installation
1. Clone the MCP Server
2. Build the Project
3. Using as an NPM Package (Recommended)
Global Installation:
Then configure it in Cursor:
Project-based Installation (Alternative):
If you prefer to manage the MCP server as a project dependency:
In this case, the command in your Cursor mcp_servers.json
would point to the local installation within your project's node_modules
:
4. Configure Environment Variables
Create a .env
file in your project root:
4. Get Your Honeybadger Credentials
- API Key:
- Go to https://app.honeybadger.io/users/auth_tokens
- Create a new Personal Auth Token
- Copy the token for your
.env
file
- Project ID:
- Go to your project in Honeybadger
- The project ID is in the URL:
https://app.honeybadger.io/projects/{PROJECT_ID}
- Or find it in project settings
Cursor Configuration
1. Configure MCP in Cursor
Add the MCP server to your Cursor configuration. Edit your ~/.cursor/mcp_servers.json
(or equivalent):
2. Alternative: Global Installation
This section will be updated or removed as it's now covered above. If you prefer the old way of cloning and installing globally from a local path, you can still do so, but using the published npm package is recommended for easier updates and management.
If installing from a local clone:
Usage
Once configured, you can use these tools in Cursor:
1. List Recent Faults
2. Get Specific Fault Details
3. Analyze an Issue
4. Get Error Occurrences
Available Tools
list_honeybadger_faults
Lists recent faults with optional filtering by environment and resolved status.
Parameters:
project_id
(optional): Project IDlimit
(optional): Number of faults (default: 20, max: 100)environment
(optional): Filter by environmentresolved
(optional): Filter by resolved status
get_honeybadger_fault
Fetches detailed information about a specific fault.
Parameters:
fault_id
(required): The fault IDproject_id
(optional): Project ID
get_honeybadger_notices
Fetches notices (error occurrences) for a specific fault.
Parameters:
fault_id
(required): The fault IDproject_id
(optional): Project IDlimit
(optional): Number of notices (default: 10, max: 100)
analyze_honeybadger_issue
Provides comprehensive analysis with fix suggestions.
Parameters:
fault_id
(required): The fault IDproject_id
(optional): Project IDinclude_context
(optional): Include request context (default: true)
Example Workflow
- List recent errors: "Show me the latest unresolved errors from production"
- Analyze specific error: "Analyze Honeybadger fault 12345 and suggest fixes"
- Get error context: "Get the latest occurrences for fault 12345 with full context"
- Review and fix: Use the analysis to understand and fix the issue in your code
Troubleshooting
Common Issues
- Authentication Error: Verify your API key is correct and has proper permissions
- Project Not Found: Check your project ID is correct
- Connection Issues: Verify network access to Honeybadger API
Debug Mode
Run the server directly to see error messages:
Logs
Check Cursor logs for MCP-related issues:
- macOS:
~/Library/Logs/Cursor/
- Windows:
%APPDATA%\Cursor\logs\
- Linux:
~/.config/Cursor/logs/
Security Notes
- Store API keys securely and never commit them to version control
- Use environment-specific API keys when possible
- Consider using read-only API tokens for this integration
- Regularly rotate your API keys
Contributing
To extend this MCP server:
- Add new tools in the
setupToolHandlers()
method - Implement corresponding handler methods
- Update the tool list and documentation
- Test thoroughly with your Honeybadger setup
Support
For issues with:
- This MCP server: Check the code and configuration
- Honeybadger API: Refer to Honeybadger API docs
- Cursor MCP integration: Check Cursor documentation
This server cannot be installed
hybrid server
The server is able to function both locally and remotely, depending on the configuration or use case.
Integrates Honeybadger error tracking with Cursor IDE, allowing developers to fetch, analyze, and troubleshoot application errors directly from their development environment.
Related MCP Servers
- -securityAlicense-qualityFacilitates integration with the Cursor code editor by enabling real-time code indexing, analysis, and bi-directional communication with Claude, supporting concurrent sessions and automatic reconnection.Last updated -22131TypeScriptMIT License
- -securityAlicense-qualityAn AI-powered development toolkit for Cursor providing intelligent coding assistance through advanced reasoning, UI screenshot analysis, and code review tools.Last updated -839240TypeScriptMIT License
- -securityAlicense-qualityA Cursor-compatible toolkit that provides intelligent coding assistance through custom AI tools for code architecture planning, screenshot analysis, code review, and file reading capabilities.Last updated -8392TypeScriptMIT License
- -securityAlicense-qualityA collection of Laravel helper tools for integration with Cursor IDE, providing features like log viewing, error searching, artisan command execution, and model information display directly within the editor.Last updated -1PythonMIT License