LexQ

Policy engine tools: author rules, simulate impact, replay decisions, and deploy.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.

Manual Client & Custom JSON ConfigExpand JSON ▾

No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for LexQ, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.

Documentation Overview

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

Terminal

npm install -g @lexq/cli

Or run without installing:

Terminal

npx @lexq/cli

Requires Node.js 22+.

Quick Start

bash

# 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)

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

Remote (Streamable HTTP)

For any MCP client that supports remote servers:

config.json

{
  "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:

bash

lexq serve --mcp

Claude Desktop

Add to claude_desktop_config.json:

config.json

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

VS Code / Cursor

.vscode/mcp.json:

config.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 LEXQ_API_KEY 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

The local stdio server and the hosted Streamable HTTP endpoint both serve two MCP revisions from one set of tool definitions, so a client sees the same tools either way.

Revision	How a client reaches it
`2026-07-28`	A per-request `_meta` envelope. No handshake.
`2025-11-25`	The `initialize` handshake.

There is nothing to configure. The server answers in whichever revision the opening message used, so a client can move to 2026-07-28 on its own schedule and one that has not moved keeps working.

AI Agent Skills

LexQ CLI ships with AI Agent Skills — structured documentation agents read to understand how to use the tools, not just what they are.

Code

skills/
├── lexq-shared/SKILL.md       Core concepts, auth, workflow
├── lexq-groups/SKILL.md       Policy groups, conflict resolution, A/B testing
├── lexq-rules/SKILL.md        Condition syntax, action types, mutex
├── lexq-simulation/SKILL.md   Dry run, Impact Simulation, compare
├── lexq-execution/SKILL.md    History, stats, failure logs, provenance, replay, latency profile
└── lexq-recipes/SKILL.md      End-to-end recipes

.claude/CLAUDE.md              Claude Code project context
AGENTS.md                      Universal agent guide (Cursor, Windsurf, Gemini CLI, Cline)
CONTEXT.md                     Platform architecture & glossary

After installing @lexq/cli, agents can read skills from:

Code

node_modules/@lexq/cli/skills/
node_modules/@lexq/cli/AGENTS.md
node_modules/@lexq/cli/CONTEXT.md

Commands

Code

lexq auth                  login | logout | whoami
lexq status                API health check
lexq serve                 Run as MCP stdio server (--mcp)
lexq groups                list | get | create | update | delete | reorder
lexq groups ab-test        start | stop | adjust
lexq versions              list | get | create | update | delete | clone
lexq rules                 list | get | create | update | delete | reorder | toggle
lexq facts                 list | create | update | delete | action-metadata | unregistered
lexq domain-templates      list | preview | apply
lexq deploy                publish | live | rollback | undeploy | history | detail | overview | deployable | diff | schedule | unschedule | schedules
lexq analytics             dry-run | dry-run-compare | requirements
lexq analytics simulation  start | status | list | cancel | export
lexq analytics dataset     upload | template
lexq profile               <groupId> — per-rule latency profile
lexq history               list | get | stats
lexq replay                decision | start | list | get | cancel
lexq logs                  list | get | action | bulk-action
lexq provenance            get | reveal-audits
lexq webhook-subscriptions list | get | save | delete | test

Global Options

Flag	Description
`--format <json\|table>`	Output format (default: `json`)
`--api-key <key>`	Override stored API key
`--base-url <url>`	Override API base URL
`--dry-run`	Preview the HTTP request without executing
`--verbose`	Show request/response details
`--no-color`	Disable colored output

Configuration

Config is stored at ~/.lexq/config.json:

config.json

{
  "apiKey": "YOUR_API_KEY",
  "baseUrl": "https://api.lexq.io/api/v1/partners",
  "format": "json"
}

The file holds an API key in plain text, so it is written 0600 inside a 0700 directory — readable by its owner and nobody else on the machine. An install created by an older version is repaired on the next save.

Environment variables

These are read by the MCP server (lexq serve --mcp) and take precedence over the stored config. They let an editor or CI target an environment through the client's own config block, without writing to ~/.lexq/config.json. CLI commands use --api-key and --base-url instead.

Variable	Overrides
`LEXQ_API_KEY`	`apiKey`
`PARTNER_BASE_URL`	`baseUrl`

Development

bash

git clone https://github.com/lexq-io/lexq-cli.git
cd lexq-cli
pnpm install
pnpm build
pnpm start -- groups list

bash

pnpm typecheck                  # Type check
pnpm lint                       # ESLint
pnpm build                      # Bundle to dist/

Checks that guard a stated fact against the thing that owns it. All of them run in CI.

bash

pnpm enums:check                # Generated enums match the engine contract
pnpm prose:check                # Numbers and code tables in prose match the contract
pnpm ab-key:check               # Tool descriptions still name the A/B traffic key
pnpm surface:check              # Nothing internal reached a public file
pnpm registry:check             # server.json agrees with package.json
pnpm schemas:check              # tools/list matches the recorded snapshot (needs a build)
pnpm test:fact-key              # Fact key grammar
pnpm test:decimals              # Metric precision display
pnpm test:export-format         # Export byte fidelity
pnpm protocol:check             # README matches the revisions the server serves

Security

Report a vulnerability through GitHub's private reporting form. The policy, including what is in scope, is in SECURITY.md.

License

Apache-2.0

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about LexQ

We don't have a confirmed install command for LexQ yet, so we don't publish a generated one — a guessed package name would point at the wrong package or none at all. Follow the project's own README or setup instructions (https://github.com/lexq-io/lexq-cli) for the current steps.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/lexq?style=directory)](https://allmcps.com/mcp/lexq)

HTML Embed

<a href="https://allmcps.com/mcp/lexq"><img src="https://allmcps.com/api/badge/lexq?style=directory" alt="LexQ on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to LexQ →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients

LexQ

Policy engine tools: author rules, simulate impact, replay decisions, and deploy.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Manual Client & Custom JSON ConfigExpand JSON ▾

Documentation Overview

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?

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

Every decision leaves a full audit trace.

Install

Terminal

npm install -g @lexq/cli

Or run without installing:

Terminal

npx @lexq/cli

Requires Node.js 22+.

Quick Start

bash

# 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

Claude.ai (Cloud — no install)

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

Remote (Streamable HTTP)

For any MCP client that supports remote servers:

config.json

{
  "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:

bash

lexq serve --mcp

Claude Desktop

Add to claude_desktop_config.json:

config.json

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

VS Code / Cursor

.vscode/mcp.json:

config.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 LEXQ_API_KEY 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

The local stdio server and the hosted Streamable HTTP endpoint both serve two MCP revisions from one set of tool definitions, so a client sees the same tools either way.

Revision	How a client reaches it
`2026-07-28`	A per-request `_meta` envelope. No handshake.
`2025-11-25`	The `initialize` handshake.

There is nothing to configure. The server answers in whichever revision the opening message used, so a client can move to 2026-07-28 on its own schedule and one that has not moved keeps working.

AI Agent Skills

LexQ CLI ships with AI Agent Skills — structured documentation agents read to understand how to use the tools, not just what they are.

Code

skills/
├── lexq-shared/SKILL.md       Core concepts, auth, workflow
├── lexq-groups/SKILL.md       Policy groups, conflict resolution, A/B testing
├── lexq-rules/SKILL.md        Condition syntax, action types, mutex
├── lexq-simulation/SKILL.md   Dry run, Impact Simulation, compare
├── lexq-execution/SKILL.md    History, stats, failure logs, provenance, replay, latency profile
└── lexq-recipes/SKILL.md      End-to-end recipes

.claude/CLAUDE.md              Claude Code project context
AGENTS.md                      Universal agent guide (Cursor, Windsurf, Gemini CLI, Cline)
CONTEXT.md                     Platform architecture & glossary

After installing @lexq/cli, agents can read skills from:

Code

node_modules/@lexq/cli/skills/
node_modules/@lexq/cli/AGENTS.md
node_modules/@lexq/cli/CONTEXT.md

Commands

Code

lexq auth                  login | logout | whoami
lexq status                API health check
lexq serve                 Run as MCP stdio server (--mcp)
lexq groups                list | get | create | update | delete | reorder
lexq groups ab-test        start | stop | adjust
lexq versions              list | get | create | update | delete | clone
lexq rules                 list | get | create | update | delete | reorder | toggle
lexq facts                 list | create | update | delete | action-metadata | unregistered
lexq domain-templates      list | preview | apply
lexq deploy                publish | live | rollback | undeploy | history | detail | overview | deployable | diff | schedule | unschedule | schedules
lexq analytics             dry-run | dry-run-compare | requirements
lexq analytics simulation  start | status | list | cancel | export
lexq analytics dataset     upload | template
lexq profile               <groupId> — per-rule latency profile
lexq history               list | get | stats
lexq replay                decision | start | list | get | cancel
lexq logs                  list | get | action | bulk-action
lexq provenance            get | reveal-audits
lexq webhook-subscriptions list | get | save | delete | test

Global Options

Flag	Description
`--format <json\|table>`	Output format (default: `json`)
`--api-key <key>`	Override stored API key
`--base-url <url>`	Override API base URL
`--dry-run`	Preview the HTTP request without executing
`--verbose`	Show request/response details
`--no-color`	Disable colored output

Configuration

Config is stored at ~/.lexq/config.json:

config.json

{
  "apiKey": "YOUR_API_KEY",
  "baseUrl": "https://api.lexq.io/api/v1/partners",
  "format": "json"
}

Environment variables

Variable	Overrides
`LEXQ_API_KEY`	`apiKey`
`PARTNER_BASE_URL`	`baseUrl`

Development

bash

git clone https://github.com/lexq-io/lexq-cli.git
cd lexq-cli
pnpm install
pnpm build
pnpm start -- groups list

bash

pnpm typecheck                  # Type check
pnpm lint                       # ESLint
pnpm build                      # Bundle to dist/

Checks that guard a stated fact against the thing that owns it. All of them run in CI.

bash

pnpm enums:check                # Generated enums match the engine contract
pnpm prose:check                # Numbers and code tables in prose match the contract
pnpm ab-key:check               # Tool descriptions still name the A/B traffic key
pnpm surface:check              # Nothing internal reached a public file
pnpm registry:check             # server.json agrees with package.json
pnpm schemas:check              # tools/list matches the recorded snapshot (needs a build)
pnpm test:fact-key              # Fact key grammar
pnpm test:decimals              # Metric precision display
pnpm test:export-format         # Export byte fidelity
pnpm protocol:check             # README matches the revisions the server serves

Security

Report a vulnerability through GitHub's private reporting form. The policy, including what is in scope, is in SECURITY.md.

License

Apache-2.0

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about LexQ

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/lexq?style=directory)](https://allmcps.com/mcp/lexq)

HTML Embed

<a href="https://allmcps.com/mcp/lexq"><img src="https://allmcps.com/api/badge/lexq?style=directory" alt="LexQ on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to LexQ →Install in Claude Desktop Install in Cursor Install in VS Code Setup guides for all 13 MCP clients