MCP server for Tideways performance monitoring integration with AI assistants
MCP server for Tideways performance monitoring integration with AI assistants. That is what the tideways mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
A Model Context Protocol (MCP) server that enables AI assistants to query Tideways performance monitoring data and provide conversational performance insights for PHP applications.
The server publishes 6 tools. What each one is for:
get_performance_metrics — Retrieve aggregate performance metrics and system-wide statisticsget_performance_summary — Retrieve time-series performance summary data in 15-minute intervals for trend analysisget_issues — Retrieve and analyze recent errors, exceptions, and performance issuesget_traces — Analyze individual trace samples for detailed bottleneck identification and performance debuggingget_historical_data — Retrieve historical performance data for specific dates with configurable granularityBuilding — The Building tool exposed by this serverConfiguration is passed through the environment: TIDEWAYS_TOKEN, TIDEWAYS_ORG, TIDEWAYS_PROJECT, LOG_LEVEL, TIDEWAYS_BASE_URL, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
metrics, issues, traces) - see API documentation - Access to a Tideways organization and projecttideways-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tideways's toolset — get_performance_metrics, get_performance_summary, get_issues and 3 more — is a fair guide to whether it matches your workflow. It is maintained by 5hahil; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_performance_metrics | Retrieve aggregate performance metrics and system-wide statistics. |
| get_performance_summary | Retrieve time-series performance summary data in 15-minute intervals for trend analysis. |
| get_issues | Retrieve and analyze recent errors, exceptions, and performance issues. |
| get_traces | Analyze individual trace samples for detailed bottleneck identification and performance debugging. |
| get_historical_data | Retrieve historical performance data for specific dates with configurable granularity. |
| Building | The Building tool exposed by this server. |
{
"mcpServers": {
"tideways": {
"command": "npx",
"args": ["tideways-mcp"],
"env": {
"TIDEWAYS_TOKEN": "your_token",
"TIDEWAYS_ORG": "your_org",
"TIDEWAYS_PROJECT": "your_project"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
metrics, issues, traces) - see API documentation - Access to a Tideways organization and project| Variable | Description | Required |
|---|---|---|
| TIDEWAYS_TOKEN | Credential the server authenticates with. | Yes |
| TIDEWAYS_ORG | Configuration value read at startup. | Optional |
| TIDEWAYS_PROJECT | Configuration value read at startup. | Optional |
| LOG_LEVEL | Configuration value read at startup. | Optional |
| TIDEWAYS_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.