LexQ — the Decision Operations Platform for engineering teams
@lexq-io
About LexQ — the Decision Operations Platform for engineering teams
The official MCP server for LexQ — the Decision Operations Platform for engineering teams. Manage business rules from your AI agent: create policy groups, define rules with visual conditions, run dry-run tests, Impact Simulation, A/B testing, deployments, and integrations.
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"lexq": {
"command": "npx",
"args": [
"-y",
"@lexq/cli",
"serve",
"--mcp"
]
}
}
}Tools
55Show current authentication info (tenant name, role, API key mask).
List all policy groups. Supports pagination and optional status/keyword filters.
Get a single policy group by ID.
Create a new policy group. Requires name and priority. Optionally set conflict resolution, activation group, and description.
Update an existing policy group. Only provided fields are updated.
Archive a policy group. Only non-live groups can be deleted. This is irreversible.
Start an A/B test on a policy group. Requires a challenger version ID and traffic split percentages.
Stop a running A/B test. Specify which version to keep.
Adjust traffic weights of a running A/B test.
List all versions of a policy group.
Get a single version by ID, including its rules and fact requirements.
Create a new DRAFT version in a policy group. Provide a commit message and optional effective date range.
Update a DRAFT version. Only DRAFT versions can be modified.
Delete a DRAFT version. Only DRAFT versions can be deleted.
Clone an existing version to create a new DRAFT. Useful when the source version is already published.
List all rules in a version. Returns summary with conditionSummary and actionSummary.
Get full rule detail including condition tree and action definitions.
Create a rule in a DRAFT version. Requires name, priority, condition tree, and actions array. Condition: { type: "SINGLE", field, operator, value, valueType } or { type: "GROUP", operator: "AND"|"OR", children: [...] } Operators: EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_OR_EQUAL, LESS_THAN, LESS_THAN_OR_EQUAL, CONTAINS, IN, NOT_IN Value types: STRING, NUMBER, BOOLEAN, LIST_STRING, LIST_NUMBER Actions: [{ type, parameters }] Types: DISCOUNT, POINT, COUPON_ISSUE, BLOCK, NOTIFICATION, WEBHOOK, SET_FACT, ADD_TAG
Update an existing rule in a DRAFT version. Only provided fields are changed.
Delete a rule from a DRAFT version.
Reorder rules by specifying rule IDs and their new priorities. Array index 0 = highest priority.
Enable or disable a rule without deleting it.
List all fact definitions (input variable schema). Shows key, type, and required status. Always check this before creating rules.
Register a new input variable. Key must be lowercase with underscores (e.g. payment_amount). Types: STRING, NUMBER, BOOLEAN, LIST_STRING, LIST_NUMBER.
Update a fact definition. Key and type cannot be changed. System facts only allow name and description changes.
Delete a fact definition. System facts cannot be deleted.
Publish a DRAFT version (DRAFT → ACTIVE). Locks the version from further edits. Must have at least one rule.
Deploy an ACTIVE (published) version to live traffic. Takes effect immediately.
Rollback to the previous deployed version. Only available if there is a previous version.
Remove the live version from traffic. The version stays ACTIVE but no longer serves requests.
List deployment history across all groups.
Get detailed info about a specific deployment including snapshot hash and integrity check.
Show current deployment status of all groups — which version is live, last deployment type, and deployer.
Execute a single dry run against a version. Tests how rules evaluate given input facts without side effects. Example input: { "facts": { "payment_amount": 100000, "customer_tier": "VIP" } } Always dry-run before publishing to validate rule behavior.
Compare dry run results between two versions using the same input facts. Useful for validating changes.
Analyze which input facts a version requires. Returns required keys, types, and an example request body.
Start a batch simulation against historical execution data. Example body: { "policyVersionId": "<uuid>", "dataset": { "type": "HISTORICAL", "source": "EXECUTION_LOGS", "from": "2025-01-01", "to": "2025-01-31" }, "options": { "baselinePolicyVersionId": "<uuid>", "includeRuleStats": true, "maxRecords": 10000 } }
Get simulation status and results. Poll until status is COMPLETED or FAILED.
List simulation history with optional filters.
Cancel a running or pending simulation.
Export simulation results as JSON or CSV. Returns the raw data.
Upload inline CSV or JSON content as a simulation dataset. The content is uploaded to S3 and a path is returned. Use this path in simulation start with dataset type UPLOADED. CSV example: user_id,payment_amount user_001,150000 user_002,50000 JSON example: [{"user_id":"user_001","payment_amount":150000}, {"user_id":"user_002","payment_amount":50000}]
Generate a sample CSV or JSON template based on the required facts of a version. Use this to understand the expected data format before uploading a dataset.
List policy execution history. Shows trace ID, group, version, status, match result, and latency.
Get full execution detail including request facts, result traces, and decision traces.
Get execution KPIs: total executions, success/failure counts, success rate, and average latency.
List all external integrations (webhooks, CRM, notification, etc.).
Get integration detail by ID.
Create or update an integration. Types: COUPON, POINT, NOTIFICATION, CRM, MESSENGER, WEBHOOK.
Delete an integration by ID.
Show available integration types and their required configuration fields.
List system failure logs from background tasks (webhook calls, coupon issuance, etc.).
Get failure log detail by ID.
Process a single failure log: RETRY, RESOLVE, or IGNORE.
Process multiple failure logs at once. Provide an array of log IDs and the action.
Overview
What is LexQ?
LexQ is a Decision Operations Platform with built-in simulation for engineering teams. It allows you to define, test, and deploy business rules without touching application code.
How to use LexQ?
Use the MCP server to manage rules. The LexQ CLI is available on npm (see GitHub and npm links in the README). Refer to the official documentation at docs.lexq.io for complete setup and configuration.
Key features of LexQ
- Visual rule builder with conflict resolution
- Dry Run: test rules with single inputs before publishing
- Impact Simulation: replay thousands of records against new rule versions
- A/B testing: split live traffic between rule versions
- Git-style versioning with instant rollback
- Webhook and notification integrations
Use cases of LexQ
- Define and test business rules without writing application code
- Simulate rule changes against historical data before deployment
- Run A/B experiments on live traffic to compare rule versions
- Roll back to previous rule versions instantly if needed
- Integrate rule changes with existing workflows via webhooks
FAQ from LexQ
How does LexQ help with testing rules before deployment?
LexQ offers Dry Run for testing rules with single inputs and Impact Simulation for replaying thousands of records against new rule versions.
Does LexQ support version control and rollback?
Yes, LexQ provides Git-style versioning with instant rollback capability.
Can LexQ integrate with other tools?
LexQ provides webhook and notification integrations for connecting with existing workflows.
Is there a visual interface for building rules?
Yes, LexQ includes a visual rule builder with conflict resolution.
How do I get started with LexQ?
You can access the LexQ console at console.lexq.io or install the CLI from npm. Full documentation is available at docs.lexq.io.
More Developer Tools MCP servers
Code Index MCP
johnhuang316A Model Context Protocol (MCP) server that helps large language models index, search, and analyze code repositories with minimal setup
MCP Unity Editor (Game Engine)
CoderGamesterModel Context Protocol (MCP) plugin to connect with Unity Editor — designed for Cursor, Claude Code, Codex, Windsurf and other IDEs
DevDocs by CyberAGI 🚀
cyberagiincCompletely free, private, UI based Tech Documentation MCP server. Designed for coders and software developers in mind. Easily integrate into Cursor, Windsurf, Cline, Roo Code, Claude Desktop App
Serena
oraiosA powerful MCP toolkit for coding, providing semantic retrieval and editing capabilities - the IDE for your agent
Hello World MCP Server (Reference Extension)
anthropicsDesktop Extensions: One-click local MCP server installation in desktop apps
Comments