Coredash

Name: Coredash
Author: corewebvitals

by corewebvitalscommunityv1.0.1

This MCP server provides access to CoreDash real user monitoring data for Core Web Vitals, letting clients query LCP, INP, and CLS from real visitors. It supports filtering, grouping, time-series analysis, and histogram views over the hosted CoreDash endpoint.

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

GitHub Repository Website

Install & configure

Prerequisites

optional
Create a CoreDash API key
Generate an API key in CoreDash settings if your MCP client does not support OAuth discovery/authentication. Tool calls require authentication; anonymous access only works for initialize.
https://coredash.app/settings/api'}]}]}},

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `coredash` MCP server into my current AI client (that's you).

Optional prerequisites:
- Create a CoreDash API key — Generate an API key in CoreDash settings if your MCP client does not support OAuth discovery/authentication. Tool calls require authentication; anonymous access only works for initialize. (https://coredash.app/settings/api'}]}]}},)

Canonical MCP server config (HTTP transport):
- url: `https://app.coredash.app/api/mcp`
- headers:
  - `Authorization`: `Bearer <your-coredash-api-key>`

Note: Hosted MCP server; no local installation or runtime command is needed. The README says clients should use the streamable-http transport. OAuth may be used instead of an API key for clients that support the WWW-Authenticate discovery flow, in which case the Authorization header may be omitted from static config.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: Hosted MCP server; no local installation or runtime command is needed. The README says clients should use the streamable-http transport. OAuth may be used instead of an API key for clients that support the WWW-Authenticate discovery flow, in which case the Authorization header may be omitted from static config.