OpenLens MCP + Claude.ai: Integration Guide
Add the OpenLens Model Context Protocol server to Claude.ai as a custom connector. This is the path for Claude.ai Team and Enterprise on the web. Once added at the workspace level, the connector shows up in Claude.ai web, Claude Desktop, and Claude Code automatically.
On Claude Free or Pro, use the Claude Desktop integration guide instead.
TL;DR
| Server URL | https://openlens.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 (browser flow) |
| Where | claude.ai/customize/connectors |
Add the connector
- Open claude.ai/customize/connectors.
- Click Add custom connector.
- Paste the server URL:
https://openlens.com/mcp - Submit the form.
Complete OAuth
Claude.ai opens the Clerk OAuth handshake in the same tab. Sign in with your OpenLens account and approve. The connector shows up as connected once the redirect completes.
Because Claude.ai syncs connectors across surfaces, the OpenLens tools now appear in Claude.ai web, Claude Desktop on every signed-in machine, and Claude Code for the same user, with no extra setup.
Verify it works
Start a new chat at claude.ai and ask:
“List my OpenLens projects.”
Claude will call list_projects and return at least one row. If the tool never fires, see Troubleshooting below.
What you can do once connected
The OpenLens MCP server exposes ~40 tools across project setup, brands, topics, prompts, runs, visibility analytics, citations, workstreams, and scheduling. From Claude.ai you can ask:
- “Build a competitive brief for project Helix. Pull share of voice by platform, top winning topics, and the three biggest losses since last month.”
- “What are the most-cited third-party publishers driving answers about us across ChatGPT and Perplexity? Group by outlet.”
- “Add a workstream for the new product launch and seed it with 8 prompts a buyer would actually type.”
- “Export the last quarter of visibility data for project Helix as a structured table I can drop into a board update.”
Troubleshooting
- “Add custom connector” button missing: custom connectors require a Team or Enterprise workspace, and workspace admins can disable them. Check with your admin.
- OAuth loop: sign out of Claude.ai, sign back in, then re-add the connector. A stale session can leave the OAuth flow stuck.
- Tools missing in Claude Desktop or Claude Code: quit and relaunch the app. Connector sync runs at startup.
- Anything else: email [email protected] with your workspace tier and the exact error.