get_historical_data
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.
LABSCO SUMMARY
get_performance_metrics and get_traces answer different questions, and each description points at the other for the case it does not cover.
The first is the aggregate view and the second the individual-request view, which is the split that decides whether you are looking at a trend or at one slow request. The useful filtering lives in get_traces: min_response_time_ms and max_response_time_ms bound the sample to the requests worth reading, and has_callgraph narrows to the traces carrying enough detail to act on. The 15-minute buckets in get_performance_summary are what make a spike visible at all — a daily aggregate would flatten it out of existence.
What it is
A Tideways client with 5 tools covering aggregate performance metrics, a 15-minute-interval summary, errors and issues, historical data at a chosen granularity, and individual trace samples.
What you get
- get_performance_metrics returns aggregate performance and system-wide statistics as JSON, for overall health and trends.
- get_performance_summary returns a time series in 15-minute buckets showing requests, errors and 95th-percentile response times.
- get_issues returns recent errors, exceptions and performance issues, filterable by issue type and status with paging.
- get_historical_data returns historical performance for a specific date at daily, weekly or monthly granularity.
- get_traces returns individual trace samples, filtered by transaction name, environment, a minimum and maximum response time, a date range, whether a call graph is present, and a sort order.
Requirements
Tideways access for the project you want to read: a token in TIDEWAYS_TOKEN, with the organisation and project named by TIDEWAYS_ORG and TIDEWAYS_PROJECT.
Setup effort
One command plus a key — npx tideways-mcp, then supply credentials
USE CASES
01
Finding out whether the application is healthy right now
The aggregate view gives the shape and the 15-minute buckets show whether something just moved, which a daily figure would hide.
02
Chasing down one slow endpoint
Bounding the sample by response time and requiring a call graph gets you the traces with enough detail to act on rather than a random slice.
03
Reading the errors that are actually happening
Issues filter by type and status, so what comes back is the open set rather than everything ever recorded.
04
Comparing this week against last
Historical data takes a date and a granularity, so the comparison is between like periods rather than between two live snapshots.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_issues
Retrieve and analyze recent errors, exceptions, and performance issues in JSON format for actionable insights
get_performance_metrics
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_summary
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_traces
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).
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. The default TIDEWAYS_RATE_LIMIT of 2500/hr matches the Team/Pro allowance, so a Basic-plan account left at the default will hit Tideways' own limit.
Requires
- npx on PATH
- TIDEWAYS_TOKEN in your environment
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx tideways-mcpMCP Clients
Claude Desktop — npx, Cursor — npx
JSON
{
"mcpServers": {
"tideways": {
"command": "npx",
"args": [
"tideways-mcp"
],
"env": {
"TIDEWAYS_TOKEN": "<YOUR_TIDEWAYS_TOKEN>",
"TIDEWAYS_ORG": "<YOUR_TIDEWAYS_ORG>",
"TIDEWAYS_PROJECT": "<YOUR_TIDEWAYS_PROJECT>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"tideways": {
"command": "npx",
"args": [
"tideways-mcp"
],
"env": {
"TIDEWAYS_TOKEN": "<YOUR_TIDEWAYS_TOKEN>",
"TIDEWAYS_ORG": "<YOUR_TIDEWAYS_ORG>",
"TIDEWAYS_PROJECT": "<YOUR_TIDEWAYS_PROJECT>"
}
}
}
}
