SiteLens MCP · SiteLens Local integration

Run SiteLens Local from your editor.

SiteLens MCP is the IDE integration layer for SiteLens Local—run real Chromium against localhost and private URLs with no API key from Cursor and other MCP hosts. When you need hosted execution, persisted history, or team-visible runs, add a workspace key for SiteLens Cloud/API. MCP enables developer workflows; it is not the primary product on its own.

npm install Five-minute workflow Cloud/API MCP + keys
Local browser QA from your editor — SiteLens Local via MCP
Cloud/API run digests — optional MCP resources when enabled

SiteLens Local via MCP

Free local execution

Install @sitelensapi/mcp from npm (any project—no SiteLens monorepo required), run sitelens_setup, then sitelens_run_local_qa against http://localhost:…—bundled Chromium executes on your machine. Saved auth profiles live under ~/.sitelens; project flows under .sitelens/flows. Cloud API key is optional for local-only QA.

npm install

Published

Run in any terminal before wiring Cursor. Package: @sitelensapi/mcp.

npm install @sitelensapi/mcp
npx @sitelensapi/mcp sitelens-mcp setup
npx @sitelensapi/mcp sitelens-mcp -- --self-test
npx @sitelensapi/mcp sitelens doctor

setup installs bundled Chromium (no Docker). --self-test and doctor verify runtime readiness.

Use SiteLens Local with Cursor

MCP

Configure SiteLens MCP in Cursor (sitelens_setup, sitelens_run_local_qa, sitelens_run_qa, …): Local tools exercise bundled Chromium on your machine with no key; Cloud/API tools call hosted execution when you set SITELENS_API_KEY.

Five-minute MCP workflow

Local-first: run npm install @sitelensapi/mcp and npx @sitelensapi/mcp sitelens-mcp setup, paste MCP config → sitelens_setup → SiteLens Local on localhost. Add dashboard sign-up and an API key only when you want SiteLens Cloud/API runs and persisted history.

1
Install from npm 
npm install @sitelensapi/mcp
npx @sitelensapi/mcp sitelens-mcp setup
2
Paste MCP config

Into ~/.cursor/mcp.json · restart Cursor. See dashboard MCP cockpit for a copy-paste JSON block.

3
Run setup 
Use the SiteLens MCP tool sitelens_setup.

Verifies bundled Chromium and artifact dirs—no API key required for Local tools.

4
SiteLens Local run

sitelens_run_local_qa for localhost and private URLs—runs on your machine at no cost.

5
Optional: SiteLens Cloud/API account

Sign up in the dashboard when you need hosted runs, monitoring direction, or team history.

6
Optional: API key + Cloud/API QA

Set SITELENS_API_KEY, then sitelens_run_qa for public URLs and persisted cloud runs.

MCP-ready prompts

Cursor

Each line maps to a concrete MCP tool—adjust URLs or flow ids to match your app.

Bootstrap

Use the SiteLens MCP tool sitelens_setup.

SiteLens Local smoke

Use the SiteLens MCP tool sitelens_run_local_qa to QA http://localhost:3000 desktop + mobile.

Compare Local runs

Use the SiteLens MCP tool sitelens_compare_local_runs to contrast my latest two SiteLens Local bundles.

SiteLens Cloud/API pass

Use the SiteLens MCP tool sitelens_run_qa against https://example.com with desktop + mobile viewports.

Cloud/API run memory (optional)

When you use Cloud/API tools, MCP can surface durable ids (sitelens_list_runs, sitelens_get_run) and resources such as sitelens://runs/{runId} for regressions across chat sessions—alongside persisted SiteLens Cloud/API history and SiteLens Studio flow runs.

Scenario Runner chains reusable flows in a shared browser session—saved auth profiles, parameterized flows, and multi-step workflow verification via sitelens_run_local_scenario. See the Scenario Runner guide.

Setup guides (npm README)

Public docs for @sitelensapi/mcp — no private repo links.

Related

Contact & onboarding

Beta access, MCP rollout help, or product updates — same short form everywhere.