OpenLens exposes a remote MCP server so agents can onboard clients, run visibility scans, read every metric the dashboard shows, and manage projects on your behalf. One OAuth sign-in, no API keys to copy.
Quick reference
| |
|---|
| Server URL | https://openlens.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 (browser flow) |
| stdio fallback | npx -y mcp-remote https://openlens.com/mcp |
Install in your client
Open claude.ai/customize/connectors, click Add custom connector, and enter https://openlens.com/mcp. The connector then shows up in Claude.ai web, Claude Desktop, and Claude Code automatically. In Claude, open Settings → Connectors → Add custom connector, enter https://openlens.com/mcp, and connect.
In your terminal, run:claude mcp add openlens --transport http https://openlens.com/mcp
/mcp, pick openlens, and finish the browser sign-in. Turn on Settings → Connectors → Advanced → Developer Mode, then Add custom connector with URL https://openlens.com/mcp and Auth set to OAuth.
One-click install. Or add manually to ~/.cursor/mcp.json:{
"mcpServers": {
"openlens": { "url": "https://openlens.com/mcp" }
}
}
Add to .vscode/mcp.json:{
"servers": {
"openlens": { "type": "http", "url": "https://openlens.com/mcp" }
}
}
In your terminal, run:codex mcp add openlens --url https://openlens.com/mcp
Add to ~/.codeium/windsurf/mcp_config.json:{
"mcpServers": {
"openlens": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://openlens.com/mcp"]
}
}
}
Add to ~/.config/zed/settings.json:{
"context_servers": {
"openlens": {
"source": "custom",
"command": "npx",
"args": ["-y", "mcp-remote", "https://openlens.com/mcp"]
}
}
}
Point it at https://openlens.com/mcp if it supports streamable HTTP. Otherwise wrap it with the stdio shim:npx -y mcp-remote https://openlens.com/mcp
Verify it works
From any client, ask the agent:
“List my OpenLens projects.”
list_projects and return at least one row.
Troubleshooting
- Auth error or “needs client registration”: sign out of your client and reconnect. The OAuth handshake has to complete on first install.
- Stale token: clear the mcp-remote cache with
rm -rf ~/.mcp-auth/ and retry.
- VS Code: “server failed to start”: Node 18+ has to be on PATH so the editor can spawn
npx.
- Anything else: email contact@aibread.com with the client, version, and the exact error.
The server exposes ~40 tools across project setup, brands, platforms, topics, prompts, prompt attributes, runs, visibility analytics, workstreams, and scheduling. See the tools reference for the full list grouped by surface.