Before you start

You need a Lens API key. Create one in Settings → API. It is shown once, so copy it somewhere safe. The MCP connector uses the same key as the REST API: one credential, revocable from the same screen.

The server endpoint is:

https://getlens.xyz/api/mcp

Claude Code

One command. Run it in your terminal, replacing the key with your own.

claude mcp add --transport http lens https://getlens.xyz/api/mcp \
  --header "Authorization: Bearer lens_sk_your_key_here"

Verify with claude mcp list. Lens should appear as connected.

Claude Desktop

Open Settings → Developer → Edit Config, then add the block below toclaude_desktop_config.jsonand restart the app.

Remote server (recommended)

{
  "mcpServers": {
    "lens": {
      "type": "http",
      "url": "https://getlens.xyz/api/mcp",
      "headers": {
        "Authorization": "Bearer lens_sk_your_key_here"
      }
    }
  }
}

If your build of Claude Desktop only supports local (stdio) servers, bridge to the remote endpoint with mcp-remote:

stdio bridge (older clients)

{
  "mcpServers": {
    "lens": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://getlens.xyz/api/mcp",
        "--header", "Authorization: Bearer lens_sk_your_key_here"
      ]
    }
  }
}

Any other MCP client

Lens implements the Streamable HTTP transport: JSON-RPC 2.0 overPOSTwith a bearer token. Point any compliant client at the endpoint and pass the key in theAuthorization header.

Verify the connection by hand

curl -sS https://getlens.xyz/api/mcp \
  -H "Authorization: Bearer lens_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A healthy server responds with the tool list. A 401 means the key is missing, wrong, or revoked.

Available tools

Nine tools, mirroring the public REST API. Claude picks the right one from these descriptions, so you can just ask in plain language.

list_workspaces

List the deals, matters or projects in the Lens organization. Call this first when the user refers to a deal or workspace by name rather than by id, to resolve the name to an id.

get_workspace

Fetch one workspace by id, including its vertical, status and description.

create_workspace

Create a new deal, matter or project. Use only when the user explicitly asks for a new workspace — this writes to their Lens account.

list_index_runs

List Index runs — the structured extractions Lens performs across a set of documents. Extracted answers are omitted here; call get_index_run for those.

get_index_run

Fetch one Index run with every extracted cell and its citations. This is how you read what Lens found in the documents — use it to answer questions about document contents.

start_index_run

Start an existing Index run. This consumes the organization's AI credits and takes minutes — it returns a job id immediately. Poll get_job until status is completed, then read the results with get_index_run.

query_knowledge_base

Search the entities Lens has extracted across every document in the organization — companies, people, metrics, risks — with mention counts and a sample citation. Use this to answer "what do we know about X" without opening individual documents. Requires the Pro or Institutional plan.

generate_memo

Generate a synthesis memo for a workspace from its documents. Consumes AI credits and takes several minutes — returns a job id immediately; poll get_job for the finished markdown. Requires the Pro or Institutional plan.

get_job

Check an asynchronous operation started by start_index_run or generate_memo. When status is "completed" the result field holds the output; when "failed" the error field explains why.

Things worth knowing

Your key is scoped to one organization. The connector can only ever see the data of the organization that issued the key.
Two tools cost AI credits:start_index_runandgenerate_memo. Both are asynchronous: they return a job id straight away, and Claude pollsget_job until the work finishes.
The Knowledge Base and memo tools need the Team or Institutional plan. On Starter they return a clear plan-limit message rather than failing silently.
Rate limits are per key, per minute, and match the REST API: starter 60/5, team 300/20, scale 1000/60 (standard / AI tools).
Revoking a key kills the connector immediately. Revoke from Settings → API; no separate MCP credential to chase.

Try it

Once connected, ask Claude things like:

“What deals do we have in due diligence?”
“What did the Index run on Project Atlas find about change-of-control clauses?”
“What do we know about Meridian Logistics across all our documents?”
“Draft an IC memo for Project Atlas covering the executive summary, key risks and valuation.”

Prefer plain HTTP? The same capabilities are available as a REST API. see the API reference.