This MCP server integrates Honeybadger error tracking with Cursor IDE, allowing you to fetch and analyze errors directly from your development environment.
- Node.js 18+ installed
- Honeybadger account with API access
- Cursor IDE with MCP support
git clone [email protected]:vishalzambre/honeybadger-mcp.git
cd honeybadger-mcp
npm install
npm run build
Global Installation:
npm install -g honeybadger-mcp
Then configure it in Cursor:
{
"mcpServers": {
"honeybadger": {
"command": "honeybadger-mcp",
"env": {
"HONEYBADGER_API_KEY": "your_api_key_here",
"HONEYBADGER_PROJECT_ID": "your_project_id"
}
}
}
}
Project-based Installation (Alternative):
If you prefer to manage the MCP server as a project dependency:
npm install honeybadger-mcp
In this case, the command in your Cursor mcp_servers.json
would point to the local installation within your project's node_modules
:
{
"mcpServers": {
"honeybadger": {
"command": "node",
"args": ["./node_modules/honeybadger-mcp/dist/index.js"],
"env": {
"HONEYBADGER_API_KEY": "your_api_key_here",
"HONEYBADGER_PROJECT_ID": "your_project_id"
}
}
}
}
Create a .env
file in your project root:
# Required: Your Honeybadger API key
HONEYBADGER_API_KEY=your_api_key_here
# Optional: Default project ID (can be overridden per request)
HONEYBADGER_PROJECT_ID=your_project_id
# Optional: Custom Honeybadger URL (defaults to https://app.honeybadger.io)
HONEYBADGER_BASE_URL=https://app.honeybadger.io
-
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
Add the MCP server to your Cursor configuration. Edit your ~/.cursor/mcp_servers.json
(or equivalent):
{
"mcpServers": {
"honeybadger": {
"command": "node",
"args": ["/path/to/honeybadger-mcp/dist/index.js"],
"env": {
"HONEYBADGER_API_KEY": "your_api_key_here",
"HONEYBADGER_PROJECT_ID": "your_project_id"
}
}
}
}
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:
# Navigate to your cloned honeybadger-mcp directory
npm install -g . # Installs from the current directory
# Then configure in Cursor as before
# ... (Cursor configuration for local global install)
Once configured, you can use these tools in Cursor:
List recent unresolved errors from Honeybadger in production environment
Get details for Honeybadger fault ID 12345
Analyze Honeybadger issue 12345 and provide fix suggestions
Get the latest 5 occurrences for Honeybadger fault 12345
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
Fetches detailed information about a specific fault.
Parameters:
fault_id
(required): The fault IDproject_id
(optional): Project ID
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)
Provides comprehensive analysis with fix suggestions.
Parameters:
fault_id
(required): The fault IDproject_id
(optional): Project IDinclude_context
(optional): Include request context (default: true)
- 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
- 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
Run the server directly to see error messages:
node dist/index.js
Check Cursor logs for MCP-related issues:
- macOS:
~/Library/Logs/Cursor/
- Windows:
%APPDATA%\Cursor\logs\
- Linux:
~/.config/Cursor/logs/
- 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
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
For issues with:
- This MCP server: Check the code and configuration
- Honeybadger API: Refer to Honeybadger API docs
- Cursor MCP integration: Check Cursor documentation