Skip to content

Connect an assistant to LexOpti

The LexOpti MCP server lets an AI assistant work in your LexOpti organization as you: find a client, read where its vigilance stands, list the alerts to review, follow a check, launch one and review an alert. The assistant acts with your role in one organization, and the audit trail records each of its actions as coming from the assistant.

https://app.lexopti.com/mcp

The server speaks the Model Context Protocol over Streamable HTTP and signs you in with OAuth: you only give your assistant this URL.

This server is for LexOpti members. To have an assistant search this documentation while you write an integration, connect the documentation MCP server instead: the LexOpti MCP server has no documentation tools.

  • You need a LexOpti account that is a member of the organization the assistant will work in.
  • An owner or an admin connects an assistant first. Claude, Claude Code, VS Code and ChatGPT identify themselves with a client metadata document. Until an owner or an admin of your organization authorizes such an assistant, other members cannot: their consent page asks them to see an owner or admin. The owner’s or admin’s consent approves it for the whole organization.
  • Keep the approval of write tools on « ask every time » in your assistant, never on « always allow »: when your assistant cannot show LexOpti’s own confirmation form, its approval of the call is all that stands before a launch. See confirmations.

With lexopti:read, the assistant finds clients and reads their vigilance, cases, alerts and checks; with lexopti:write, it also launches checks, creates cases and reviews alerts. It never confirms for you: before a launch it calls lexopti_preview_check and shows you who will be screened and the credits it costs, before a case it calls lexopti_preview_case and shows you its cost (without LexOpti’s form, the case is only a proposal you create in LexOpti), and the review of an alert is your decision and your reason, or a proposal you validate in LexOpti. The LexOpti MCP server reference lists the tools, the confirmations and the limits.

On claude.ai and Claude Desktop (Free, Pro, Max: one custom connector at most on Free):

  1. Open Customize > Connectors, select +, then Add custom connector.
  2. Name it LexOpti, paste https://app.lexopti.com/mcp and select Continue.
  3. Under OAuth client, keep Use Claude’s published identity (Recommended): Claude then identifies itself with its client metadata document. Do not choose Register automatically, which LexOpti does not offer.
  4. Select Add, then Connect, and sign in to LexOpti.

On a Team or Enterprise plan, an owner adds the connector in Organization settings > Connectors (Add > Custom); each member then selects Connect under Customize > Connectors. In a conversation, turn the connector on from + > Connectors.

Claude redirects to https://claude.ai/api/mcp/auth_callback after you sign in.

Terminal window
claude mcp add --transport http lexopti https://app.lexopti.com/mcp

Then run /mcp in a session, select lexopti and authenticate in the browser (or run claude mcp login lexopti). Add --scope user to use LexOpti in every project. Claude Code identifies itself with its client metadata document.

VS Code 1.106 or later identifies itself with its client metadata document. Add the server to .vscode/mcp.json in your workspace, or to your user configuration (MCP: Open User Configuration):

{
"servers": {
"lexopti": {
"type": "http",
"url": "https://app.lexopti.com/mcp"
}
}
}

Start the server from the file or from MCP: List Servers, then sign in to LexOpti when VS Code asks.

On ChatGPT on the web:

  1. Open Plugins, select +, then Add custom MCP server.
  2. Name it LexOpti and enter https://app.lexopti.com/mcp as Server URL.
  3. Choose OAuth authentication.
  4. Check I understand and want to continue, select Create as a plugin, install the plugin and sign in to LexOpti.

ChatGPT identifies itself with its client metadata document. On Business plans, only workspace admins and owners can add a server; on Enterprise and Edu, admins can let members do it. ChatGPT Pro allows read and fetch tools only: the assistant then reads LexOpti but cannot launch a check, create a case or review an alert.

Cursor does not support client metadata documents: it uses a public client LexOpti registered for Cursor. Add the server to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
"mcpServers": {
"lexopti": {
"url": "https://app.lexopti.com/mcp",
"auth": {
"CLIENT_ID": "<LexOpti client ID for Cursor>",
"scopes": ["offline_access", "lexopti:read", "lexopti:write"]
}
}
}
}

Cursor then opens LexOpti to sign in, and comes back to http://localhost:8787/callback.

Copilot Studio uses a confidential client LexOpti registers for your organization: write to contact@lexopti.com to get its client ID and secret. Then, in your agent:

  1. Open Tools, select Add a tool, New tool, then Model Context Protocol.

  2. Enter https://app.lexopti.com/mcp as Server URL, choose OAuth 2.0, then Manual, and fill in:

    Field Value
    Client ID and Client secret given by LexOpti
    Authorization URL https://app.lexopti.com/api/auth/oauth2/authorize
    Token URL template and Refresh URL https://app.lexopti.com/api/auth/oauth2/token
    Scopes openid email offline_access lexopti:read lexopti:write
  3. Select Create, and send the callback URL Copilot Studio shows to contact@lexopti.com: LexOpti adds it to your client.

MCP Inspector lets a developer call the tools by hand:

Terminal window
npx @modelcontextprotocol/inspector

In the web interface, add the server with the Streamable HTTP transport (http) and the URL above. The Inspector has no client metadata document of its own: give it the URL of one you publish over HTTPS (Client Settings > Client ID Metadata Document), whose redirect URI is http://localhost:6274/oauth/callback; an owner or admin of your organization authorizes it first. To call it from a terminal, add --cli https://app.lexopti.com/mcp --method tools/list --client-metadata-url <your document's URL>.

On a LexOpti development session, bun run mcp:inspector-client registers the Inspector’s client and prints the steps.

A sandbox organization works like any other: connect the assistant to it while choosing the organization. Its checks consult no source, return deterministic results and bill nothing (see Sandbox).

What you see What it means
401, « connect LexOpti again » The token is missing, expired, or no longer valid: you left the organization, your consent was revoked, or the organization blocked the assistant. Connect again.
403 insufficient_scope A write tool needs lexopti:write: authorize again with both scopes.
429, « retry in a minute » More than 120 calls a minute for you and this assistant.
A tool error naming what to do For example a read-only role, an expired preview, an alert no longer available, or the hourly launch limit. The assistant reads the message and acts on it.

A preview can also report incomplete_identity (identity fields to complete in LexOpti first) or insufficient_credits (the client’s dossier needs more credits than the organization holds): nothing is launched then.

  • Disconnect it for yourself: remove the connector in the assistant.
  • Revoke its access to the organization: an owner or admin asks LexOpti through the contact form (the Connected applications tab of the organization’s page lists the assistant, read only). LexOpti deletes the members’ authorizations and its tokens in the organization at once; a member can authorize it again.
  • Block it: at the same request, LexOpti cuts all its access to the organization at once, and no member can authorize it until it is unblocked.
  • Privacy policy: lexopti.com/en/privacy. LexOpti runs in the European Union and your data stays there.
  • What LexOpti keeps: what the assistant does as you (a launched check, the review of an alert) is kept like what you do in LexOpti, with the audit trail entry that names the assistant: five years after the end of the business relationship (CMF L561-12), then deleted or anonymised. LexOpti keeps nothing of your conversation.
  • What the assistant sees: the results it reads go to its provider (Anthropic, OpenAI, Microsoft, Anysphere) under that provider’s own terms. Choose an assistant your organization has approved for client data.
  • Support: contact@lexopti.com.