Skip to main content
Glama
thrivecausemetics

TrackJS MCP Server

by thrivecausemetics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to TrackJS MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • 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 Server Sentry

      Zzzccs123
      F
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript implementation of a Model Context Protocol server that connects to Sentry error tracking service, allowing AI models to query and analyze error reports and events.
      17 npm
      -
    • Raygun MCP Server by MindscapeHQ

      Raygun MCP Serverofficial

      MindscapeHQ
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP Server for Raygun's API V3 endpoints for interacting with your Crash Reporting and Real User Monitoring applications. This server provides comprehensive access to Raygun's API features through the Model Context Protocol.
      40 npm
      22
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_errors lists errors with filtering, get_error_details retrieves specifics for a single error, and get_error_messages aggregates common messages. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow the same verb_noun pattern (get_errors, get_error_details, get_error_messages) using snake_case consistently. The naming convention is uniform and predictable.

    Tool Count5/5

    With only 3 tools, the set is well-scoped for a focused error-monitoring server. Each tool serves a necessary function and none feel redundant or excessive.

    Completeness4/5

    The server covers the core read-only workflow: listing/filtering errors, viewing details, and aggregating messages. It lacks write/update operations, but that appears outside its intended scope as a retrieval-focused tool.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources