Tideways MCP Server
Related Servers
Alternatives to Tideways MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLets 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.39MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.16 npm14MIT
- AlicenseNot gradedqualityCmaintenanceConnects 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.32 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides 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
- AlicenseNot gradedqualityFmaintenanceEnables 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.2MIT
- AlicenseBqualityDmaintenanceEnables natural-language investigation of Datadog data including logs, metrics, monitors, traces, hosts, dashboards, events, and incidents, all through read-only API access.142,108 npmMIT
TDQS
Scored across 8 tools
The three performance-reporting tools (get_performance, get_performance_summary, get_history) overlap in surface area, but the descriptions carefully delimit each: per-minute detail vs 15-minute trend buckets vs daily/weekly/monthly historical reports. The list_* tools target clearly different resources (projects, services, issues), and search_traces and get_observations are distinct enough.
All tools share the tideways_ prefix and follow a consistent verb_noun pattern (list_projects, list_services, list_issues, search_traces, get_performance, get_history, get_observations). get_performance_summary is a minor variant on the same verb but still readable and predictable.
Eight tools is well-matched to an APM/observability server, covering projects, services, performance, issues, traces, history and observations without redundancy. Each tool earns its place with a distinct investigative role.
The surface covers the main observability lifecycle: discovering projects/services, listing issues, inspecting traces, and pulling performance/history/observations. Minor gaps exist (e.g. no issue detail/status-update tool, no explicit environment listing), but agents can work around these with the given tools.