Skip to main content
Glama

Related Servers

Alternatives to Bugsink MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with the Honeybadger error monitoring service to list, filter, and analyze fault data. It provides tools for fetching error lists and retrieving detailed fault information from Honeybadger projects.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Read and manage your Argulog error tracking data - issues, projects, alerts, releases, billing, and admin operations - from any LLM agent. Authenticates with a Personal Access Token from the dashboard: PAT scopes gate writes server-side.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query, analyze, and resolve errors within the GlitchTip error tracking platform by providing access to issue details and stacktraces. It allows users to list unresolved issues and mark them as fixed using natural language commands.
      3
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Integrates GlitchTip error monitoring with AI assistants to fetch, analyze, and debug production errors. It enables users to list issues, retrieve event details, and perform guided triage of application errors through natural language.
      2
      98 npm
      11
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Glitchtip error tracking platform through natural language. Provides access to issues, events, projects, teams, and organization management for comprehensive error monitoring and debugging.
      7
      15 npm
      3
      AGPL 3.0
    • A
      license
      B
      quality
      F
      maintenance
      Enables AI assistants to query and analyze errors from Bugsink self-hosted error tracking instances. Supports listing projects, teams, issues, and viewing detailed error events with stacktraces.
      16
      743 npm
      17
      MIT

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools are clearly distinct: list_* for collections, get_* for single items, and get_event_stacktrace for stacktraces. However, get_event and get_event_stacktrace both relate to event details, and get_latest_event_stacktrace could be confused with get_event_stacktrace without reading carefully, but descriptions clarify.

    Naming Consistency4/5

    Naming follows a consistent list_/get_ pattern with entities. The exception is get_latest_event_stacktrace, which deviates from the simple get_<entity> structure but still uses the get_ prefix and describes the specific action clearly.

    Tool Count5/5

    With 8 tools covering teams, projects, issues, events, and stacktraces, the count is well-scoped for a read-only error tracking server. No redundancy or excess, and it's within the typical 3-15 tool range.

    Completeness4/5

    The tool set provides comprehensive read access to the core domain: listing entities, retrieving details, and fetching stacktraces. Missing are write operations, but the server appears focused on inspection/troubleshooting, so no critical gaps for that purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues