Connect Lenz to your coding tool.

# the Lenz plugin: the server plus the fact-check skill; then sign in from /mcp
$ claude plugin marketplace add lenzhq/lenz-mcp
$ claude plugin install lenz@lenz

# or the server alone, for every project; sign in with /mcp
$ claude mcp add --scope user --transport http lenz https://lenz.io/mcp

# with an API key instead, export LENZ_API_KEY=lenz_… and add:
# --header "Authorization: Bearer ${LENZ_API_KEY}"

Add to Cursor → Opens Cursor with Lenz ready to add; then click Authorize next to lenz in its MCP settings and sign in. Also in the Cursor Directory ↗

// with an API key instead (CI, a shared config): export LENZ_API_KEY=lenz_…
// and add to ~/.cursor/mcp.json. Cursor reads only ${env:NAME}.
{
  "mcpServers": {
    "lenz": {
      "url": "https://lenz.io/mcp",
      "headers": { "Authorization": "Bearer ${env:LENZ_API_KEY}" }
    }
  }
}

# adds Lenz to your VS Code profile; it asks you to sign in on first connection
$ code --add-mcp '{"name":"lenz","type":"http","url":"https://lenz.io/mcp"}'

# with an API key instead: run "MCP: Open User Configuration" in VS Code
# and add "headers": { "Authorization": "Bearer lenz_…" } to lenz

# registers the server in ~/.codex/config.toml and opens the Lenz sign-in
$ codex mcp add lenz --url https://lenz.io/mcp

# sign-in interrupted? run: codex mcp login lenz
# with an API key instead, add: --bearer-token-env-var LENZ_API_KEY
# and export LENZ_API_KEY=lenz_… where Codex runs

// add to your client's MCP config, with your key in place of lenz_…;
// a client that supports MCP sign-in can leave out "headers" and sign in
{
  "mcpServers": {
    "lenz": {
      "type": "http",
      "url": "https://lenz.io/mcp",
      "headers": {
        "Authorization": "Bearer lenz_…"
      }
    }
  }
}