sitelens-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SITELENS_MCP_PORT | No | Localhost bridge port | 19527 |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sitelens_pingA | Health check: whether the local SiteLens bridge is up, which port it uses, and how many reports are cached. |
| sitelens_get_latest_reportA | Return the latest AnalysisReport JSON pushed by the SiteLens extension. Optional url substring filter. |
| sitelens_list_reportsA | List cached SiteLens reports as summaries only (url, analyzedAt, score, module issue counts). Newest first. |
| sitelens_export_checklistA | Build a severity-ordered actionable checklist from the latest (or url-matched) report: SEO warn/fail, image suggestions, a11y, security. No AI. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: health check (ping), retrieve the newest full report, enumerate cached report summaries, and derive a checklist. The only near-overlap (get_latest_report vs list_reports) is clearly separated by 'full AnalysisReport JSON' versus 'summaries only, newest first.' An agent can select correctly from names alone.
All four tools share the sitelens_ prefix and a verb_noun pattern (get_latest_report, list_reports, export_checklist), which is predictable. The lone deviation is sitelens_ping, a bare verb with no noun, but that is idiomatic for a health check.
Four tools is on the lean side but each covers a genuinely separate need (health, fetch, enumerate, transform). Nothing appears redundant, though the surface is thin enough that a couple of convenience tools could reasonably have been added.
The domain is a read-only bridge over cached reports, and the surface covers discovery (list), retrieval (get latest, with url filtering), health, and one derived output (checklist). Minor gap: there is no way to fetch an older or specific report by id/url beyond 'latest matching,' and no cache-clearing operation.