Arkansas Code vs Lex Ray
A side-by-side look at the Arkansas Code and Lex Ray MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Arkansas CodeLegal · Local subprocess (stdio)Arkansas Code of 1987 — state statutes by citation and by topic search.41FairAuth: no auth requiredL
Lex RayLegalStructured EU and UK legislation: public metadata, free sample articles, and entitled full text.39FairAuth: no auth requiredVerdict: choose Arkansas Code for legal work as a local process; choose Lex Ray for legal. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Arkansas Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
LChoose Lex Ray when
- You need dedicated capabilities in the Legal domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Arkansas Code | L Lex Ray |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 41/100 · Fair | 39/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Arkansas Code | View Lex Ray |
Tools & capabilities
Arkansas Code tools
No tool names declared yet. Check the project README from the listing page.
Lex Ray 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.
Arkansas Code
{
"mcpServers": {
"arkansas-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-arkansas-code"
]
}
}
}
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.
Frequently asked questions
Arkansas Code is categorized under Legal and uses a local stdio subprocess. Lex Ray belongs to Legal and uses an install path we have not confirmed yet. Pick Arkansas Code for legal work and Lex Ray for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Lex Ray has no confirmed install command yet — follow its own setup instructions.
Arkansas Code is listed as free. Auth: no auth required. Lex Ray has no declared pricing — check the project's own site. Auth: no auth required. 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 arkansas-code and lex-ray as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Arkansas Code has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Lex Ray has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.