OpenLens MCP integrations
The OpenLens MCP server is a single endpoint that any MCP-capable AI client can connect to. One OAuth sign-in. About 40 tools for projects, brands, topics, prompts, runs, citations, workstreams, and scheduling. Pick your client below for the exact setup steps.
Common to all clients
| 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 |
Claude
Code editor
- CursorSetup guide →
Add the OpenLens MCP server to Cursor in one click and drive AI visibility scans from the editor.
- VS CodeSetup guide →
Add the OpenLens MCP server to VS Code Copilot Chat (agent mode) with a one-line config.
- WindsurfSetup guide →
Wire the OpenLens MCP server into Windsurf via mcp_config.json and the mcp-remote stdio shim.
- ZedSetup guide →
Add OpenLens as a context server in Zed's settings.json. Drive AI visibility scans from the editor.
Chat
CLI
Beyond the listed clients
Any client that supports streamable HTTP can point directly at https://openlens.com/mcp. For clients that only support stdio, wrap the URL with the mcp-remote shim:
npx -y mcp-remote https://openlens.com/mcpFor the full reference (tools, auth flow, troubleshooting), see the MCP server docs on docs.openlens.com.