Log inSubmit server
LexQ logo

LexQ

Manage LexQ business rules, simulate decisions, inspect execution history, and deploy policy versions through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install LexQ

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "lexq": {
      "command": "npx",
      "args": [
        "-y",
        "@lexq/cli"
      ],
      "env": {
        "LEXQ_API_KEY": "YOUR_VALUE_HERE",
        "PARTNER_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y @lexq/cli

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 10d ago.

Overview

LexQ MCP server connects AI agents to the LexQ policy engine for managing policy groups, versions, rules, facts, simulations, deployments, and execution data. It exposes the same tool set through a hosted Streamable HTTP endpoint or the LexQ CLI's local stdio mode. Agents can test changes against historical executions or uploaded datasets before deployment, then review audit and execution details. Reach for LexQ when business rules such as pricing, promotions, fees, or eligibility checks need to change independently of an application release.

Use cases

  • Author and revise pricing or eligibility rules
  • Simulate policy changes against past executions
  • Replay decisions and inspect execution history
  • Deploy or roll back policy versions
  • Profile rule latency and review provenance

Key features

  • Policy group, version, rule, and fact management
  • Impact Simulation and dataset-based testing
  • Decision replay and execution history
  • Deployment, rollback, undeploy, and scheduling
  • Audit, provenance, logs, and latency profiles
  • Hosted Streamable HTTP and local stdio modes

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @lexq/cli (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads3.2kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How LexQ works

What LexQ MCP server does

LexQ MCP server gives MCP-compatible agents access to LexQ's decision operations platform. It is intended for teams that keep business rules outside application code and call the LexQ API to evaluate them. Agents can manage policy groups, versions, rules, and facts; run simulations and replays; inspect execution history; and publish or change deployed versions.

The server covers the main lifecycle of a policy change. An agent can create or update rules, test a version with supplied facts, compare outcomes, inspect prior decisions, and deploy a selected version. Domain templates can provision facts, sample rules, and a policy group as a starting point.

How it works

LexQ provides two connection modes with the same tool definitions:

  • A hosted Streamable HTTP server at https://mcp.lexq.io.
  • A local stdio server started with lexq serve --mcp.

Remote clients authenticate through OAuth 2.1. For local use, the CLI reads an API key saved by lexq auth login, or the MCP client's environment can provide LEXQ_API_KEY. The server can also use PARTNER_BASE_URL to select a different API base URL.

The CLI and hosted endpoint support MCP revisions 2026-07-28 and 2025-11-25. Clients use the revision appropriate to their opening request; no protocol setting is required. Approval remains under the MCP client's control. Deployment, rollback, and undeploy operations are marked destructive so clients can request confirmation before executing them.

Setup and configuration

Install the CLI globally with:

Terminal
npm install -g @lexq/cli

Node.js 22 or newer is required. You can also run the package through npx without a global installation.

Authenticate the CLI with lexq auth login, then check the account with lexq auth whoami. The API key is stored in ~/.lexq/config.json; the file is protected with owner-only permissions when saved by the CLI. For a local MCP client, configure the command as npx -y @lexq/cli serve --mcp, or run an installed lexq serve --mcp command.

A remote client can use this configuration:

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

For local MCP use, set LEXQ_API_KEY in the client's environment or authenticate once with the CLI. LEXQ_API_KEY and PARTNER_BASE_URL take precedence over stored configuration for the MCP server.

Tools and capabilities

Available operations cover:

  • Policy groups, ordering, conflict resolution, and A/B tests.
  • Policy versions, cloning, updates, and deletion.
  • Rules, facts, rule ordering, toggles, and action metadata.
  • Domain template listing, preview, and application.
  • Dry runs, comparisons, Impact Simulation jobs, dataset uploads, exports, and cancellation.
  • Publishing, going live, rollback, undeploy, deployment history, diffs, and schedules.
  • Decision replay, execution history, statistics, failure logs, provenance, and latency profiles.
  • Webhook subscription management and testing.

The package also includes agent-oriented skill files covering authentication, policy concepts, rule syntax, simulation, execution data, and end-to-end workflows.

Limitations and notes

LexQ operations require access to the LexQ API and an API key with suitable permissions. The local configuration stores the API key as plain text, protected by filesystem permissions. Destructive deployment actions should be treated as approval-gated operations in the MCP client. The server manages LexQ policies and decisions; it does not replace the application service that evaluates those policies in production.

Read the full README View source on GitHub

Reviews

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

Frequently Asked Questions about LexQ

LexQ is an MCP server that connects AI agents to the LexQ policy engine. Its main tools manage policy groups, versions, rules, and facts, run simulations and decision replays, inspect execution history, and deploy or roll back policy versions through hosted HTTP or local stdio.

Install it with `npm install -g @lexq/cli`, then run `lexq serve --mcp` for local stdio access. Node.js 22 or newer is required. You can also use `npx -y @lexq/cli serve --mcp` without installing the package globally.

Yes, LexQ works with Cursor through either its hosted Streamable HTTP endpoint or a local stdio configuration. For local use, add the `npx -y @lexq/cli serve --mcp` command to `.vscode/mcp.json` and provide an API key through prior CLI login or `LEXQ_API_KEY`.

Set the server URL to `https://mcp.lexq.io` in a remote MCP client. OAuth 2.1 authentication is handled by the client, and the hosted endpoint exposes the same LexQ tool definitions as the local stdio server.

Yes, LexQ can run dry runs and Impact Simulation before deployment. Agents can test a version against supplied facts, compare dry-run results, or use historical executions and uploaded datasets to evaluate a proposed change.

Related MCP servers

All in Legal All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

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 PreviewLexQ AllMCPs Directory Badge
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>