Skip to main content
Glama
abuhamza

Tideways MCP Server

by abuhamza

Related Servers

Alternatives to Tideways MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Lets AI assistants query Dynatrace Managed environments — services, traces, metrics, pods, and problems — by running read-only GET requests through your already logged-in browser session, so no API tokens are needed. All traffic stays on your machine between the AI client, a local server, and a browser extension.
      39
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying and analysis of OpenTelemetry traces, metrics, and logs stored in Elasticsearch/OpenSearch, allowing AI assistants to investigate performance issues, find root causes, and explore system behavior.
      7 npm
      14
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to New Relic with read-only access to NRQL, logs, metrics, traces, alerts, and more. Offers optional, gated write operations with a dry-run and confirmation workflow.
      19 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides Claude and other AI agents with read-only, guardrailed access to Pinpoint APM data, enabling production debugging through traces, metrics, transactions, and service topology.
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI assistants to interact with Mender IoT platform for device management, deployment monitoring, and fleet analysis through natural language commands. Provides read-only access to device status, deployment logs, releases, and system monitoring capabilities.
      2
      MIT

    TDQS

    A4.3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (list_issues vs get_issue, search_traces vs get_transaction). The performance family—get_performance, get_performance_summary, get_history, get_transaction—overlaps in domain but the descriptions carefully delineate granularity and use cases, leaving only mild ambiguity.

    Naming Consistency5/5

    All tools follow a consistent tideways_<verb>_<noun> pattern (list_issues, get_performance, search_traces, get_observations). Prefix and verb/noun conventions are uniform throughout with no deviations.

    Tool Count5/5

    Ten tools is well-scoped for an observability/monitoring server. Each tool maps to a distinct facet (issues, projects, services, performance, traces, history, observations) without redundancy.

    Completeness4/5

    The surface covers the core read workflows well: discovery (projects/services), performance windows, transactions, traces, issues and automatic findings. It is read-only by nature, so lifecycle coverage is reasonable, though some deeper drill-downs (e.g. arbitrary trace-by-bottleneck filtering) are noted as unavailable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues