LexQ MCP server

LexQ CLI

The Decision Operations Platform for engineering teams.

CLI and MCP server for LexQ — move business rules out of

your deploy pipeline, prove every change with Impact Simulation, and ship without

a git push.

Website · Docs · Console · MCP Registry

Why LexQ?

Your business rules — pricing, promotions, fee logic, eligibility checks — change often. But every change ships through the same PR → review → staging → deploy cycle as your core application code. A one-line discount rule takes two weeks.

This is an architectural problem, not a process problem. Business logic that changes weekly shouldn't live in code that ships quarterly.

LexQ separates the two. Rules live outside your application. You change them in a visual console or through this CLI. You prove every change with Impact Simulation against real execution data. You deploy without touching your codebase.

Every decision leaves a full audit trace.

Install

npm install -g @lexq/cli

Or run without installing:

npx @lexq/cli

Requires Node.js 22+.

Quick Start

# 1. Authenticate
lexq auth login
# Enter your API key (create one at console.lexq.io → Management → API Keys)

# 2. Verify
lexq auth whoami

# 3. Start from a domain template — provisions facts, sample rules, and a policy group
lexq domain-templates list
lexq domain-templates apply --template ECOMMERCE
# Returns: policyGroupId, policyVersionId, factsCreated, rulesCreated

# 4. Test a rule against your data before shipping
lexq analytics dry-run --version-id <VERSION_ID> --debug \
  --json '{"facts":{"loyaltyTier":"PLATINUM","purchaseSubtotalUsd":150}}'

# 5. Deploy
lexq deploy publish --group-id <GROUP_ID> --version-id <VERSION_ID> --memo "v1"
lexq deploy live --group-id <GROUP_ID> --version-id <VERSION_ID> --memo "Initial deploy"

For AI Agents — the Complete Partner API

LexQ is designed to be AI-native. The entire policy engine Partner API is exposed via Model Context Protocol. Claude, Cursor, and other MCP-compatible agents can create, simulate, and deploy rules autonomously, with human approval before production.

Claude.ai (Cloud — no install)

1. Settings → Connectors → Add Custom Integration
2. Enter: https://mcp.lexq.io
3. Sign in with your LexQ account and select an API key
4. Done — the full toolset available in every conversation

Remote (Streamable HTTP)

For any MCP client that supports remote servers:

{
  "mcpServers": {
    "lexq": {
      "url": "https://mcp.lexq.io"
    }
  }
}

OAuth 2.1 authentication is handled automatically by your client.

Local (stdio)

Run LexQ CLI as a local MCP server:

lexq serve --mcp

Claude Desktop

Add to claudedesktopconfig.json:

{
  "mcpServers": {
    "lexq": {
      "command": "npx",
      "args": [
        "-y",
        "@lexq/cli",
        "serve",
        "--mcp"
      ]
    }
  }
}

VS Code / Cursor

.vscode/mcp.json:

{
  "servers": {
    "lexq": {
      "command": "npx",
      "args": [
        "-y",
        "@lexq/cli",
        "serve",
        "--mcp"
      ]
    }
  }
}

Prerequisite: lexq auth login must have been run once to store an

API key in ~/.lexq/config.json, or LEXQAPIKEY must be set in the client's

environment block.

Registry

The server is listed on the official MCP Registry as io.lexq/lexq. Clients that browse the registry find both the npm package and the hosted endpoint in that one entry.

Protocol Support

Shortened. The full README is on GitHub.