Use SiteLens MCP globally in Cursor
SiteLens MCP runs as a standalone Node process. It does not require the SiteLens monorepo to be open.
npm install
npm install @sitelensapi/mcp
npx -y @sitelensapi/mcp sitelens-mcp setup
npx -y @sitelensapi/mcp -- --self-test
npx -y @sitelensapi/mcp sitelens doctor --cursor- Local QA uses bundled Chromium (no Docker).
- Cloud API key is optional until you use cloud tools.
- Flows live in
.sitelens/flowsin your open workspace. - Auth profiles live under
~/.sitelens.
Global ~/.cursor/mcp.json (recommended)
Use stdio MCP only — no extra subcommands in args:
{
"mcpServers": {
"sitelens": {
"command": "npx",
"args": ["-y", "@sitelensapi/mcp"],
"env": {
"SITELENS_MODE": "local",
"SITELENS_DEFAULT_URL": "http://127.0.0.1:3000"
}
}
}
}Restart Cursor after saving mcp.json.
Do not use in Cursor mcp.json
"args": ["-y", "@sitelensapi/mcp", "sitelens-mcp", "setup"]— runs one-shot setup, not MCP."args": ["-y", "@sitelensapi/mcp", "sitelens", "doctor"]— exits after diagnostics.SITELENS_MCP_HTTP=1— loopback HTTP on 8787; SiteLens Desktop uses a separate HTTP runtime.
Diagnostics
npx -y @sitelensapi/mcp sitelens doctor --cursorLocal free vs cloud (optional)
Local tools (sitelens_qa_run, auth, compare/list local runs) are free with no API key. Cloud tools register when
SITELENS_API_KEY is set and SITELENS_MODE is all or cloud.
Dashboard copy-paste: app.sitelensapi.com/mcp.