Skip to main content
Glama
vltansky

GlitchTip MCP Server

by vltansky

Related Servers

Alternatives to GlitchTip MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Integrates GlitchTip error monitoring with AI assistants, enabling them to fetch, analyze, and debug issues from your GlitchTip instance.
      2
      10 npm
      6
      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
      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
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to retrieve and analyze Sentry issues, including error reports, stacktraces, and debugging information from Sentry.io.
      6 npm
      1
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      Connects AI tools directly to Codemend production error monitoring to list, analyze, and resolve software crashes. It enables users to retrieve AI-generated fixes and automatically open GitHub pull requests to address production issues.
      5
      3 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves all issues, while the other fetches the latest event for a specific issue. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern with the prefix 'glitchtip_' followed by a descriptive noun phrase (issues, latest_event). This uniformity enhances readability and predictability, adhering to a clear convention throughout the tool set.

    Tool Count2/5

    With only two tools, the server feels under-scoped for a monitoring or error-tracking domain like GlitchTip. Essential operations such as creating, updating, or resolving issues are missing, which limits the server's utility and suggests an incomplete implementation.

    Completeness2/5

    The tool set is severely incomplete for error tracking. While it allows reading issues and events, it lacks CRUD operations (e.g., create, update, delete issues) and other key functionalities like searching or filtering, which are critical for comprehensive agent workflows in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues