A side-by-side look at the Lex Ray and LexRay MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
LexRay tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Lex Ray
No confirmed install command for Lex Ray yet — follow the setup steps linked from its listing page rather than a guessed package name.
LexRay
No confirmed install command for LexRay yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Lex Ray is categorized under Legal and uses an install path we have not confirmed yet. LexRay belongs to Legal and uses an install path we have not confirmed yet. Pick Lex Ray for legal work and LexRay for legal.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Lex Ray has no declared pricing — check the project's own site. Auth: no auth required. LexRay is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lex-ray and lexray as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lex Ray has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. LexRay has 46/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.