Coredash

io.github.corewebvitalsPublished by GitHub account corewebvitalsv1.0.1Updated Oct 25, 2026

Real User Monitoring for Core Web Vitals. Query LCP, INP, CLS field data from real visitors.

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

A hosted MCP server for CoreDash that lets an assistant query real-user Core Web Vitals (LCP, INP, CLS) field data with filters and grouping.

What you can do
Query current p75 performance scores, filtered and grouped by dimensions such as device, country, page path, URL, browser, OS and attribution selectors, with rated good/improve/poor buckets. Retrieve a metric over time with an improving, stable or regressing summary for spotting trends and regressions. Inspect the distribution shape of a single metric across roughly 40 buckets to see whether traffic is bimodal, long tailed or evenly slow.
When to use it
Useful when you want an assistant to answer questions about real-visitor performance, such as why LCP is slow on mobile in a country, whether INP regressed on a template recently, or how a metric is distributed across pages.
Requirements
A remote hosted endpoint connected over streamable HTTP; no local install. Authentication is required: OAuth browser sign-in (recommended) or an API key sent as the Authorization header in the form Bearer cdk_...; anonymous calls can initialize but not call tools.
Before you install
The API key is a secret passed in the Authorization header; keep it out of shared configs and logs. Tool calls require authentication and read performance data from your CoreDash account, which is stored in the EU. CoreDash itself is a paid product with plans starting at $19 per month.

Installation

In SourceWeft

  1. Open Coredash in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.corewebvitals%2Fcoredash/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "coredash": {
      "type": "http",
      "url": "https://app.coredash.app/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

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.

The MCP server is hosted at https://app.coredash.app/api/mcp. This repo holds the public connector docs and registry manifest. You do not need to install or run a server. You connect your MCP client directly to the hosted endpoint.

What CoreDash is

CoreDash is a Real User Monitoring platform built around Core Web Vitals. It collects LCP, INP, and CLS from real visitors and lets you segment by page template, country, device, browser, OS, and 20 plus other dimensions. Data is stored in the EU. The product runs without consent banners. Paid plans start at $19 per month. More at coredash.app.

Tools exposed via MCP

ToolPurpose
get_metricsCurrent performance scores at p75. Filter and group by any dimension. Use for "what is" questions.
get_timeseriesMetric over time with an improving, stable, or regressing summary. Use for regressions and trends.
get_histogramDistribution shape of a single metric across roughly 40 buckets. Use to see whether traffic is bimodal, long tailed, or evenly slow.

All three tools return rated buckets (good, improve, poor) matching the Core Web Vitals thresholds. Filter dimensions include device (d), country (cc), page path (ff), URL (u), browser, OS, and the LCP / INP / CLS attribution element selectors.

Authentication

The server supports two methods:

  1. OAuth (recommended). Point your MCP client at the server URL and complete the browser sign-in when prompted — no API key required. The server follows the WWW-Authenticate discovery flow and publishes /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource.
  2. API key. Best for CI or headless use. Generate one at coredash.app/settings/api and pass it as Authorization: Bearer cdk_YOUR_API_KEY.

Anonymous calls succeed for initialize (so clients can introspect server capabilities) and fail for any tool call.

Connecting

Claude Code

Add the server, then authenticate in the browser:

bash
claude mcp add --transport http coredash https://app.coredash.app/api/mcp

Run /mcp inside Claude Code, select coredash, and complete the OAuth sign-in.

To use an API key instead (e.g. in CI), pass it as a header:

bash
claude mcp add --transport http coredash https://app.coredash.app/api/mcp \  --header "Authorization: Bearer cdk_YOUR_API_KEY"

Cursor

Add to ~/.cursor/mcp.json, then click Login on the server in Cursor's MCP settings to complete OAuth:

json
{  "mcpServers": {    "coredash": {      "url": "https://app.coredash.app/api/mcp"    }  }}

To use an API key instead, add a "headers" block with "Authorization": "Bearer cdk_YOUR_API_KEY".

VS Code

Add to .vscode/mcp.json in your workspace (or the user config via the MCP: Open User Configuration command). VS Code prompts you to sign in on first use:

json
{  "servers": {    "coredash": {      "type": "http",      "url": "https://app.coredash.app/api/mcp"    }  }}

To use an API key instead, add a "headers" block with "Authorization": "Bearer cdk_YOUR_API_KEY".

Windsurf

Same JSON shape as Cursor, in the Windsurf MCP settings.

Any other MCP client

Point it at https://app.coredash.app/api/mcp with the streamable-http transport. Clients that support OAuth discover the flow via the WWW-Authenticate header; otherwise pass an Authorization: Bearer cdk_YOUR_API_KEY header.

Example queries

Why is LCP slow on mobile in Germany this week?Has INP regressed on the product detail template in the last 24 hours?Show me the LCP distribution on /checkout/* in the US.

Registry listing

This server is published on the Official MCP Registry as io.github.corewebvitals/coredash. From there it propagates to PulseMCP, Smithery, Glama, and Windsurf.

The registry manifest is in server.json. To publish a new version, edit the file and run mcp-publisher publish.

Related projects

  • cwv-superpowers. Skills package for Claude Code, Cursor, and Gemini that drives this MCP server to diagnose and fix Core Web Vitals issues.
  • Core Web Vitals Visualizer. Chrome extension. Lets you see CWV metrics overlayed on any page.

License

MIT. See LICENSE.

Source: README.md at commit 9c18b21

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts