Tideways MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | debug, info, warn or error, case-insensitive; logs go to stderr | info |
| TIDEWAYS_ENV | No | Default environment. Defaults to the API default. | |
| TIDEWAYS_ORG | No | Organization, to match a plain project name. Defaults to the token's projects. | |
| TIDEWAYS_TOKEN | Yes | API token | |
| TIDEWAYS_PROJECT | No | Default project; with several projects and no default, pass `project` per call. Defaults to the token's only project. | |
| TIDEWAYS_SERVICE | No | Default service. Defaults to the project's default service. | |
| TIDEWAYS_BASE_URL | No | API base URL, https only | https://app.tideways.io/apps/api |
| TIDEWAYS_REQUEST_TIMEOUT | No | Request timeout in ms, a positive integer up to 600000 | 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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tideways_list_projectsA | List the projects, scopes and rate-limit status of the configured Tideways API token. Call this first when unsure which project to use, or after a scope or unknown-project error. |
| tideways_list_servicesA | List the services of a project (web, APIs, workers, CLI) named by its open issues, the default service first. Call it when the user names an app, API or worker that is not a project, or a transaction that tideways_search_traces does not find in the default service, with "search" set to one word of it: each service is searched for that word and the services are sorted by matching traces, so the first ones serve it. Costs 3 requests, plus 1 per service searched: at most 30, and no more than a tenth of the hourly rate limit. Only services named by the newest open issues are listed; the Tideways UI service selector lists all. |
| tideways_get_performanceA | Performance of any window of 1-1440 minutes ending at "end" (default now) within the last ~30 days: totals (requests, error rate, p95/median/average response time, time per layer), the top 20 transactions by impact, and a timeline. Older windows return zeros; use tideways_get_history for them. For 15-minute trends over 30 days use tideways_get_performance_summary. |
| tideways_get_performance_summaryA | Requests, errors and p95 response time in 15-minute buckets for the last |
| tideways_list_issuesA | List error, slow-SQL or deprecation issues of a project, newest occurrence first, 10 per page. Use to find what is failing or slow and how often. One type and one status per call. Lists issues seen in the default service of one environment. There is no time filter; use lastOccurred to judge recency. |
| tideways_search_tracesA | Find individual request traces (at most 30 per call, newest first unless sortBy is set) with response time, memory, bottlenecks and the slowest layers. Use to investigate specific slow or failing requests; filter by text, time window and response time. |
| tideways_get_historyA | Daily, weekly or monthly performance report for a past date: total requests, error rate, p95, top 20 transactions by impact and a timeline. Use to compare days or weeks. A period that has not ended covers only its finished hours (pendingBuckets > 0), and today has no data until it ends; compare such periods per day or use tideways_get_performance_summary. Covers production and the project's default service only; for another environment or service use tideways_get_performance with end and minutes=1440 (one day per call). |
| tideways_get_observationsA | Automatic findings Tideways made for a project: PHP configuration problems (e.g. OPcache buffers, timeouts) and code bottlenecks detected in traces (e.g. N+1 queries, sleep, waits). Use for a quick health check or optimization ideas. Findings do not name the affected requests, and the API cannot filter traces by bottleneck: give the user the link, whose page in the Tideways UI lists recent affected traces. Do not infer N+1 queries from slow-SQL issues. |
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 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.