OpenLens

OpenLens MCP + Cursor: Integration Guide

Add the OpenLens Model Context Protocol server to Cursor and drive AI brand visibility scans, citations, projects, and reports from inside the IDE. One OAuth sign-in. No API keys to copy.

TL;DR

Server URLhttps://openlens.com/mcp
TransportStreamable HTTP
AuthOAuth 2.1 (browser flow)
Config file~/.cursor/mcp.json

One-click install (works on macOS, Linux, Windows where Cursor is installed):

Add OpenLens to Cursor

Manual install

If the deeplink does not work or you want to manage the config in git, add the server entry yourself.

Open ~/.cursor/mcp.json (create it if missing) and paste:

{
  "mcpServers": {
    "openlens": { "url": "https://openlens.com/mcp" }
  }
}

For project-scoped configuration, use .cursor/mcp.json in the repo root with the same shape.

Complete OAuth

Restart Cursor. The first time the agent invokes an OpenLens tool, Cursor opens a browser tab for the Clerk OAuth handshake. Sign in with your OpenLens account and approve. The token is cached for future calls.

Verify it works

From any Cursor chat, ask:

“List my OpenLens projects.”

The agent should call list_projects and return at least one row. If the call hangs or returns nothing, 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 Cursor you can ask:

  • “Set up a new client called Acme. They sell laptop stands. Competitors are Roost and Rain Design. Track topics around ergonomic desk setups.”
  • “How is Acme doing this week across all platforms? Just the headline visibility plus where they are winning and losing.”
  • “Pull the top cited sources for Acme's last run and tell me where I should be pitching content.”
  • “Run prompts for project X and notify me when the run finishes.”

Troubleshooting

  • Auth error or “needs client registration”: sign out of Cursor (or remove the mcp-auth cache with rm -rf ~/.mcp-auth/) and retry. The OAuth handshake has to complete on first install.
  • Tools not showing up: verify the config file is valid JSON and that Cursor was restarted after the edit. Cursor reads MCP config at startup.
  • Anything else: email [email protected] with your Cursor version and the exact error.

Related