CoreDash. Real User Monitoring for Core Web Vitals
@corewebvitals
CoreDash. Real User Monitoring for Core Web Vitals について
Query LCP, INP, and CLS field data from real visitors. Three tools: get_metrics, get_timeseries, get_histogram. Filter and group by device, country, page path, browser, OS, and 20+ dimensions. All data is real user monitoring (RUM) at the p75 percentile, the standard Google uses
基本情報
設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"coredash": {
"url": "https://app.coredash.app/api/mcp",
"headers": {
"Authorization": "Bearer cdk_YOUR_API_KEY"
}
}
}
}ツール
ツールは検出されませんでした
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
What is CoreDash?
CoreDash is a Real User Monitoring (RUM) MCP server for Core Web Vitals. It provides LCP, INP, CLS, FCP, and TTFB field data from real visitors, accessible through any MCP‑compatible client for developers monitoring production web performance.
How to use CoreDash?
Generate an API key at https://coredash.app/settings/api, then add the server to your MCP client with the header Authorization: Bearer cdk_YOUR_API_KEY. OAuth is also supported via WWW Authenticate discovery.
Key features of CoreDash
- Query current performance scores with get_metrics, filterable by 20+ dimensions
- Analyze performance over time with get_timeseries and automatic trend detection
- View distribution shape of a single metric with get_histogram (40 buckets with ratings)
- Data from real users at the p75 percentile, matching Google’s ranking standard
- Filter and group by device type, country, page path, URL, browser, OS, and attribution elements
Use cases of CoreDash
- Monitor Core Web Vitals from real users in production
- Detect regressions and trends in loading, interactivity, and visual stability
- Compare performance across segments (e.g., mobile vs desktop)
- Pinpoint which page elements cause slow LCP, slow INP, or layout shifts
FAQ from CoreDash
What metrics does CoreDash track?
LCP, INP, CLS, FCP, and TTFB, all measured at the p75 percentile.
What dimensions can I filter and group by?
Device type, country, page path, URL, browser, OS, plus 20+ more including attribution elements (lcpel, inpel, clsel).
How do I authenticate?
Use a Bearer token API key via the Authorization header, or OAuth via WWW Authenticate discovery.
Where does the data come from?
All data comes from real users in production – not synthetic testing.
Where can I generate an API key?
「開発者ツール」の他のコンテンツ
TalkToFigma
sonnylazuardiTalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
test
harlancA simple,high performance and secure live media server in pure Rust (RTMP[cluster]/RTSP/WebRTC[whip/whep]/HTTP-FLV/HLS).🦀
sentry-mcp
getsentryAn MCP server for interacting with Sentry via LLMs.
Serena
oraiosA powerful MCP toolkit for coding, providing semantic retrieval and editing capabilities - the IDE for your agent
Test
x1xhlolFULL Augment Code, Claude Code, Cluely, CodeBuddy, Comet, Cursor, Devin AI, Junie, Kiro, Leap.new, Lovable, Manus, NotionAI, Orchids.app, Perplexity, Poke, Qoder, Replit, Same.dev, Trae, Traycer AI, VSCode Agent, Warp.dev, Windsurf, Xcode, Z.ai Code, Dia & v0. (And other Open Sou
コメント