Tideways MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (debug, info, warn, error) | info |
| TIDEWAYS_ORG | Yes | Tideways organization name | |
| TIDEWAYS_TOKEN | Yes | Tideways API access token | |
| TIDEWAYS_PROJECT | Yes | Tideways project name | |
| TIDEWAYS_BASE_URL | No | Tideways API base URL | https://app.tideways.io/apps/api |
| TIDEWAYS_RATE_LIMIT | No | API requests per hour — match to your plan (Team/Pro: 2500, Standard: 1000, Basic: 250) | 2500 |
| TIDEWAYS_MAX_RETRIES | No | Maximum API retry attempts | 3 |
| TIDEWAYS_REQUEST_TIMEOUT | No | API request timeout (ms) | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_performance_metricsA | Retrieve aggregate performance metrics and system-wide statistics in JSON format. Use for monitoring overall application health, trends, and high-level performance overview (use get_traces for detailed individual request analysis). |
| get_performance_summaryB | Retrieve time-series performance summary data in 15-minute intervals in JSON format for trend analysis and historical comparison. Returns data aggregated in 15-minute time buckets showing requests, errors, and 95th percentile response times. |
| get_issuesA | Retrieve and analyze recent errors, exceptions, and performance issues in JSON format for actionable insights |
| get_historical_dataA | Retrieve historical performance data in JSON format for a specific date with configurable granularity. Analyze daily, weekly, or monthly performance trends, transaction reports, and time-series metrics. |
| get_tracesA | Analyze individual trace samples in JSON format for detailed bottleneck identification and performance debugging. Use for investigating specific slow requests, not system-wide statistics (use get_performance_metrics for aggregate data). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Tools are mostly distinct, but get_performance_metrics and get_performance_summary both deal with performance data, requiring careful reading of descriptions to differentiate. get_historical_data also overlaps slightly with time-series data, but descriptions help clarify.
All tools follow a consistent 'get_<noun>' pattern in snake_case, making it predictable and easy for an agent to understand the action and resource.
5 tools is a well-scoped set for a performance monitoring server, covering the essential retrievals without unnecessary bloat.
Covers all typical retrieval needs for application performance: historical data, issues, aggregate metrics, time-series summary, and individual traces. Minor gap in missing alerting or write operations, but retrieval surface is solid.