Production connection guide

Bring Marli into the agent you already use.

Ask questions across your connected Lytica data from ChatGPT, Codex, Claude Code, or Cursor. Sign in with your existing Lytica account—no API key or token handoff.

01 / Connect

Three steps. Your credentials stay yours.

  1. 01

    Add the server

    Use the production endpoint in your preferred client.

  2. 02

    Sign in with Lytica

    Your browser opens so you can sign in and choose an organization.

  3. 03

    Ask Marli

    The connection can read only the data available to that Lytica organization.

02 / Client setup

Choose where you work.

Each client authorizes Marli separately, even when you use the same Lytica account.

Anthropic

Claude Code

CLI

Add Marli at user scope to make it available in every Claude Code project, then complete browser sign-in.

Claude Code setup commands
claude mcp add --transport http --scope user marli https://mcp.lyticalabs.ai/mcp
claude mcp login marli
claude mcp list

Finish in Claude

If authentication does not open automatically, launch Claude Code, enter/mcp, choose marli, and select Authenticate.

The --scope user flag is intentional. Remove it if you want a project-private configuration instead.

Managed Claude Code installations can restrict MCP servers. Ask your administrator to allow the production endpoint if Marli is blocked.

Anthropic’s MCP guide
Anysphere

Cursor

Add to Cursor
Manual setup

Add the JSON configuration

Save globally at ~/.cursor/mcp.json, or per project at.cursor/mcp.json.

Cursor MCP configuration
{
  "mcpServers": {
    "marli": {
      "url": "https://mcp.lyticalabs.ai/mcp"
    }
  }
}
Verify & authenticate

Use Cursor Agent

Cursor Agent setup commands
agent mcp enable marli
agent mcp login marli
agent mcp list
agent mcp list-tools marli

Current releases use agent. If your installation exposescursor-agent, that command is a compatible alias.

Cursor Enterprise can manage MCP centrally. Ask your administrator if Marli does not appear or cannot be enabled.

03 / Authentication

A browser login—not a secret exchange.

Marli uses OAuth to connect the client to the Lytica account and organization you approve.

Never paste credentials

Do not paste an API key, OAuth client ID, client secret, bearer token, JWT, authorization code, or Lytica password into client configuration or chat.

Organization-bound access

Access follows your current Lytica membership. Marli can only read sources connected and available to the organization approved during sign-in.

Switch safely

To change organizations or accounts, disconnect Marli in that client, connect it again, and complete browser sign-in for the intended organization.

04 / Verify

Confirm the account before asking business questions.

Run this once after connecting. Marli should identify the approved organization and report only sources available through that signed-in account.

Suggested first prompt
Use Marli to tell me which Lytica organization this authenticated connection belongs to and summarize the connected data sources available to me. Do not guess or use web search.