Coredash MCP Server

Real User Monitoring for Core Web Vitals. Query LCP, INP, and CLS field data from real visitors through the Model Context Protocol. Exposed over MCP by the coredash mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Its toolset

Everything the assistant can do here goes through one of these:

• get_metrics — Current performance scores at p75. Filter and group by any dimension. Use for "what is" questions
• get_timeseries — Metric over time with an improving, stable, or regressing summary. Use for regressions and trends
• get_histogram — Distribution shape of a single metric across roughly 40 buckets. Use to see whether traffic is bimodal, long tailed, or evenly slow
• Cursor — Add to ~/.cursor/mcp.json, then click Login on the server in Cursor's MCP settings to complete OAuth:
• Windsurf — The Windsurf tool exposed by this server

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Coredash MCP's toolset — get_metrics, get_timeseries, get_histogram and 2 more — is a fair guide to whether it matches your workflow. It is maintained by corewebvitals; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the coredash mcp mcp server does with a few real requests.