Skip to main content
Glama
bobbyrgoldsmith

LightScout MCP

by bobbyrgoldsmith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHROME_PATHNo/usr/bin/chromium
PUPPETEER_SKIP_CHROMIUM_DOWNLOADNotrue

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
analyze_performanceA

Run Lighthouse on a URL and get Core Web Vitals scores, metrics, and prioritized recommendations. Returns LCP, FCP, CLS, TBT, SI, TTFB with good/needs-improvement/poor ratings.

compare_performanceA

Compare Core Web Vitals between two URLs, or the same URL on mobile vs desktop. Shows per-metric deltas with winner indicators.

check_thresholdA

Pass/fail check against performance thresholds. Use for CI quality gates. Defaults use Google's 'poor' thresholds — only fails if metrics are genuinely bad.

crawl_siteA

Discover all pages on a site (via sitemap.xml or link crawling) and run Lighthouse on each. Returns per-page results plus site-wide summary with avg/min/max scores and common issues. Max 20 pages, 3 parallel runs.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: single URL analysis, threshold pass/fail check, two-URL comparison, and multi-page crawl. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with lowercase underscores: analyze_performance, check_threshold, compare_performance, crawl_site. No deviations.

Tool Count5/5

Four tools is well-scoped for the performance auditing domain. Each tool serves a necessary function without bloat or deficiency.

Completeness4/5

Core workflows (single analysis, comparison, crawl, CI gate) are covered. Minor gap: no tool for customizing thresholds, but defaults are sensible.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources