Legis-Intel MCP multi-client setup
Endpoint: https://www.jusnrem.legal/mcp
Transport: Streamable HTTP (JSON responses), authenticated, read-only research tools.
Access: operator-issued pilot keys; paid subscriptions and browser OAuth are not active.
Use one key per client. Keep keys outside repositories. Never put a key in a URL.

Claude Code: merge claude-code.json into .mcp.json and supply QANUN_ACCESS_TOKEN in the launching environment. Use /mcp to check the connection.
VS Code: merge vscode.json into .vscode/mcp.json; the client prompts for the key.
Claude API: set ANTHROPIC_API_KEY, ANTHROPIC_MODEL, QANUN_ACCESS_TOKEN; run python claude.py.
Grok API: set XAI_API_KEY, XAI_MODEL, QANUN_ACCESS_TOKEN; run python grok.py.
Provider API calls may incur separate charges; samples are not run automatically.
Other stdio clients: download bridge.mjs, install Node.js 22+, replace both absolute paths in stdio-client.json, then merge the server entry into your client's MCP configuration. The token file must contain only your access key.
Each client has its own configuration format; the stdio example uses the common mcpServers format.

Test prompt: Find Health Care Commission legislation and return the original source links.
Expected: two held title matches, with current force unknown; never infer current applicability.
Only public held-corpus research is exposed. Private manuscript records are not in this hosted service.

Credential lifecycle: operator keys expire, can be scoped to individual tools, and are revoked by removing their hash from the host configuration and redeploying. No subscription, durable quota, OAuth, or payment entitlement is implied.