honeybadger mcp

    2

    Connect your AI agent to Honeybadger to list production faults, fetch stack traces, and automate bug fixes.

    $30

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    honeybadger mcp

    Example session with this skill installed

    List the most recent unresolved Honeybadger errors in production for project 76543 and analyze the top one.

    • Read your context and instructions
    • Compiled the honeybadger mcp

    I have retrieved the latest unresolved faults for project 76543. The most critical issue is a NameError occurring in the checkout flow.

    Honeybadger finding

    • Fault ID: 98210334
    • Class / message: NameError: undefined local variable or method 'apply_discount' for #<Order:0x0000>
    • Environment: production
    • Occurrences: 42 (last seen 5 minutes ago)
    • Primary location: app/models/order.rb:112 in process_payment

    Root cause: The method process_payment references apply_discount, but this method was recently renamed to apply_promotional_discount in the last deployment, leaving a stale reference in the payment logic.

    • Recommended fix: Update line 112 in app/models/order.rb to call the correct method name.

    Verification: Run bundle exec rspec spec/models/order_spec.rb and check the Honeybadger dashboard after deployment to ensure no new notices appear for this ID.

    
    # Proposed patch for app/models/order.rb
    def process_payment
    -  apply_discount
    +  apply_promotional_discount
       gateway.authorize(total)
     end
    

    Next steps

    1. Open app/models/order.rb at line 112 to verify the context.
    2. Apply the method name change.
    3. Run the existing test suite to check for side effects.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Manual error tracking wastes developer time. This skill connects your AI agent directly to Honeybadger to inspect live production faults and suggest fixes without leaving your editor.

    What it does

    • Fault discovery lists unresolved production errors with filtering for environment, project, and status.
    • Deep analysis pulls complete stack traces and error metadata to identify root causes.
    • Context retrieval fetches specific notices to inspect session data, CGI params, and environment variables.
    • Source mapping correlates remote stack frames to local workspace files for immediate debugging.
    • Fix generation proposes concrete patches and regression tests based on real-world error data.

    How it works

    1. Setup guides you through configuring the MCP server with your API key and project ID.
    2. Triage lists recent unresolved faults to identify high-priority issues.
    3. Analyze runs a deep dive on a specific fault ID to extract stack context and fix suggestions.
    4. Locate opens the relevant local files identified in the Honeybadger trace.
    5. Resolve implements the suggested fix and summarizes the findings for the team.

    Frameworks & tools

    Built for any MCP-capable agent including Cursor, Claude Desktop, Claude Code, and Windsurf. Requires Node.js 18+ and a Honeybadger account.

    Why this beats prompting it yourself

    Pasting stack traces manually is slow and prone to losing critical context like session data or environment metadata. This skill automates the data retrieval, ensuring the agent sees the exact production state that caused the crash.

    Use cases

    • Debugging a NoMethodError appearing in the production environment.
    • Daily triage of unresolved exceptions across multiple Honeybadger projects.
    • Identifying which recent deployment introduced a specific regression.
    • Reviewing session and param data for elusive edge-case bugs.

    Known limitations

    This skill is read-only and cannot resolve or delete faults in the Honeybadger UI. It requires a personal auth token and does not support SSO-only environments without API access.

    Read-only access only; cannot resolve or delete faults via MCP. Requires Node.js 18+ and manual input of API keys.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Honeybadger MCP
    Node.js
    Config MCP

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill allows your AI agent to directly query Honeybadger's API to retrieve production error logs, stack traces, and environment metadata, enabling it to suggest fixes based on real-world crash data rather than manual copy-pasting.

    The honeybadger-mcp skill is compatible with any MCP-enabled environment, including Cursor, Claude Desktop, Claude Code, and Windsurf, provided you have Node.js 18 or higher installed.

    Setup is straightforward: you will need to provide your Honeybadger API key and Project ID within your agent's MCP configuration file to establish a secure connection to your error data.

    For security, the skill is currently read-only; it can fetch and analyze fault data to propose code fixes, but it cannot resolve, ignore, or delete errors within the Honeybadger dashboard itself.

    Yes, the skill is designed to map remote stack frames from Honeybadger notices to the corresponding files in your local workspace, allowing the agent to open and edit the exact lines of code where the error occurred.

    New in LLM Ops