Skip to main content
Glama
olaj

unofficial-trackjs-mcp

by olaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to unofficial-trackjs-mcp

No user-submitted related servers found.

    Related Servers

    • Rudow MCP Server

      prenzio
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to query application projects directly for logs, metrics, incidents, and semantic search through read-only tools.
      17
      MIT

    • Sprinklr MCP Server

      daiict218
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants read-only access to Sprinklr data via MCP, allowing querying reports, searching cases, and calling Sprinklr API endpoints.
      4 npm
      ISC

    • google-analytics-mcp-server

      getmcpads-com
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to query Google Analytics 4 reporting and configuration data through 27 read-only tools, including pivots, funnels, realtime reports, Admin API inspection, and diagnostics, with identifiers redacted by default.
      27
      530 npm
      Apache 2.0

    • sparkmedic-mcp

      brianzavareh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to perform automated root-cause analysis of slow Apache Spark and Databricks jobs by listing applications, planning and running diagnoses, retrieving stage and SQL plan details, and listing diagnosis rules via read-only MCP tools.
      Apache 2.0
    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

    A4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct aggregation dimension (individual errors, by message, by URL, by day, by hour, page views, usage), and descriptions explicitly state when to prefer one over another (e.g. top_messages before list_errors). The main potential confusion is between the parallel day/hour variants and between page_views_by_hour and usage_by_hour, but the granularity/scope wording keeps them distinguishable.

    Naming Consistency4/5

    Six of eight tools follow a clean resource_by_dimension pattern (errors_by_url, errors_by_day, page_views_by_hour, usage_by_hour). Two outliers use verb-first naming (list_errors, top_messages) which is readable and arguably intentional for 'list raw items' vs 'aggregate', but breaks strict uniformity.

    Tool Count5/5

    Eight tools is well-scoped for an error-analytics server; each tool covers a distinct report shape (raw errors, groupings, time series, traffic, account usage) with no redundant entries.

    Completeness3/5

    The read-oriented analytics surface is solid (individual errors, groupings, daily/hourly trends, traffic for error-rate math), but triage status is only ever read, never updated, and there are no breakdowns by browser, release, or application despite such data being present in error records. Agents can answer 'what is breaking' questions but cannot manage or slice errors beyond URL/time.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources