Skip to main content
Glama
c20020207

AppSignal MCP Server

by c20020207
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AppSignal MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Sentry

      MCP-100
      F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that retrieves and analyzes Sentry.io issues, allowing users to inspect error reports, stacktraces, and debugging information from their Sentry account.
      2
      22
      -

    • mcp-sentry

      fastmcp-me
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables retrieving and analyzing Sentry issues, including stacktraces and debugging information.
      2
      -

    • Waroom MCP

      topotal
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables interaction with Waroom API to retrieve incident information and postmortem details through a standardized protocol.
      26
      16 npm
      1
      MIT

    • AppSignal MCP

      pauldub
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and fetch error and performance monitoring data from AppSignal through the Model Context Protocol. Supports searching and retrieving detailed information about application errors and performance samples with flexible filtering options.
      5
      MIT
    • Sentry MCP Server by getsentry

      Sentry MCP Serverofficial

      getsentry
      F
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that lets AI assistants interact with the Sentry API to retrieve and analyze error data, manage projects, and monitor application performance.
      11
      12
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    D1.6/5.0

    Scored across 3 tools

    Disambiguation3/5

    The tools have distinct names (getIncident, getIncidentSample, listIncidents) suggesting different purposes, but without descriptions, it's unclear how 'getIncident' and 'getIncidentSample' differ—they could overlap in retrieving incident data. The 'listIncidents' is clearly separate for listing multiple incidents.

    Naming Consistency5/5

    All tool names follow a consistent camelCase pattern with clear verb-noun combinations (getIncident, getIncidentSample, listIncidents). There are no deviations in naming style, making them predictable and readable.

    Tool Count2/5

    With only 3 tools, the server feels thin for an incident management domain, as it likely lacks essential operations like creating, updating, or resolving incidents. This minimal set may not support complete agent workflows, indicating an under-scoped tool surface.

    Completeness2/5

    Inferred from the domain (incident management), there are significant gaps: no tools for creating, updating, deleting, or resolving incidents, and no coverage for related entities like alerts or metrics. This incomplete surface will likely cause agent failures in handling full incident lifecycles.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources