mcpbeat Sign in

LexQ MCP Server

by lexq Your server? Claim it
answering

LexQ is answering right now. Last checked moments ago. 949 installs a week from npm. Last commit 26 Oct 2026.

The Decision Operations Platform for engineering teams

Installs per day peak 349 · avg 102 · +89% w/w
a month agotoday
Uptime history 55 days of history · worst day 96%
55 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
417 ms
Response time
average over 24h
949
Installs / week
npm and PyPI

Nothing serious here today

Today is the operative word: we check LexQ every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add lexq --transport http https://mcp.lexq.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.lexq.io/mcp
~/.codex/config.toml
[mcp_servers.lexq]
url = "https://mcp.lexq.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "lexq": {
      "url": "https://mcp.lexq.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "lexq": {
      "type": "http",
      "url": "https://mcp.lexq.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.lexq.io/mcp streamable-http sign-in 378 ms 0 min ago

Alternatives to LexQ

same job, measured the same way
Plexarm
by plexarm

The operating system for self-organised AI agent teams.

answering
Forkflux MCP
by forkflux

Self-hosted multi-agent collaboration and audit layer for AI-assisted engineering teams

101 installs/wk local only
Bilg
by bilgai

Shared memory for coding agents and their teams: docs, epics, tasks and decisions over MCP.

answering
Aurora Coach
by aurora-coach-com

Continuous improvement for software engineering teams: check-ins, improvements, suggestions.

answering
RoryPlans
by roryplans

AI work orchestration for plans, tasks, teams, and coding-agent dispatch.

answering
DevOpsCollab
by devopscollab

Senior LatAm engineers for US teams. Facts, role fit, and staffing requests.

3 tools answering
Meser10 MCP
by meser10

Operate the Meser 10 email and SMS platform from any MCP client. Read-only by default.

40 installs/wk local only
iKanban
by i-kanban

Tasks, sprints, releases and docs for engineering teams with AI coding agents.

answering

LexQ — questions

Answers built from our own checks of this server.

Why is there no tool list for LexQ?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is LexQ working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 417 ms. The bar chart above shows every period we have measured.
How do I connect LexQ?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to LexQ?
No API key is involved. LexQ answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is LexQ?
It answers our handshake in 417 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use LexQ?
The npm package @lexq/cli was installed 949 times in the last week. Week over week that is +89%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is LexQ open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 0 stars on GitHub and 2 open issues. The licence covers the code in the repository, not the hosted service at mcp.lexq.io, which runs on its operator's own terms.