Global law
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
Legal practice management: redacted matters, sources, drafts and verified legal professionals.
作者提供的原文
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-03 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Relex Legal。按照 https://mcp.popnx.com/i/legal-relex-relex.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(relex.legal) · ✓ 命令已检查 2026年11月20日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Relex Legalhttps://relex.legal/api/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsRelex Legal
用 Relex Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Relex Legal,或回答中出现 Relex Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Relex Legalhttps://relex.legal/api/mcp开启新聊天,输入前先从插件列表中选择 Relex Legal
用 Relex Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Relex Legal,或回答中出现 Relex Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user relex https://relex.legal/api/mcp应能看到 Relex Legal 在列表中并显示已连接
用 Relex Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Relex Legal,或回答中出现 Relex Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Relex Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Relex Legal,或回答中出现 Relex Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Relex Legal 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Relex Legal,或回答中出现 Relex Legal 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://relex.legal/api/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user relex https://relex.legal/api/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"relex": {
"url": "https://relex.legal/api/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"relex": {
"type": "http",
"url": "https://relex.legal/api/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过域名 relex.legal 验证(注册中心会核实域名所有权)
代码最后更新于17天前
不适用:由 relex.legal 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 899 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/legal-relex-relex)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于17天前,最新版本(0.1.11)于17天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Global law, Open Legal Data (Germany), LibreJustice, InfraNode, Fedlex Connector
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
The law of nearly every country on earth, any date: read it, see what changed it, check citations.
German court decisions (Rechtsprechung) and laws (Gesetze) with citation graph and citation checks.
Search French-language and European case law and French legal texts (codes, statutes, treaties).
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types.
Search Swiss federal legislation: laws, articles, amendments via the Fedlex SPARQL endpoint.
| 本项 Relex Legal | Global law | Open Legal Data (Germany) | LibreJustice | InfraNode | Fedlex Connector | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | AGPL-3.0 | NOASSERTION | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Legal Workspace — One source of truth for any Agent — confidential by design
Keep legal knowledge, matter context and saved progress in Relex, independently of the assistant you use. Authorize another compatible agent to continue from the same stored context, without rebuilding the background in another chat.
https://relex.legal/api/mcp and authorize your own Relex account. Installing a package does not authorize private data.Portability covers information saved in Relex, not automatic import of private chat histories or a model's internal memory. Client-side identity encryption, de-identification and MCP access controls protect the supported workflows; de-identified legal facts may still be sensitive. Review what you authorize.
Use Legal Workspace for persistent legal context; the Legal SDK for building your firm's or legal department's own platform; and the Legal Marketplace to discover published professional profiles or make an AI-first law firm discoverable across specialties.
An agent may help find a professional and prepare a reference-only request. The user must review and approve sharing in Relex. Discovery is not engagement, a completed conflict check, payment or a guarantee of professional availability.
Each area is a search tag on the MCP server; see how-relex-works.md §0 and §7.
| Area | Over MCP |
|---|---|
| Matters and portable context | Matter context, redacted sources, saved work products, steering conclusions |
| Ontology | Matter graph read and evidence-backed corrections; firm ontology |
| Know-how | Playbooks, clause library (search, add, update), labelled templates (create, list by label, update), knowledge sources |
| Research | Cached official legal text |
| Data collection | Which channels feed the workspace (status only) |
| Agreements | Drafts, review comments, enforceability advisory, agreements from templates |
| Intake | Evaluation agent, guest-link redemption |
| E-signature | Prepare for signature (the user confirms the send in Relex); signature status by signer role |
| Invoices | Create and read (the user confirms the send in Relex) |
| Payments | Payment status and online-payment readiness (read-only) |
Deletions, sends to people outside Relex, billing and payment writes, uploads and connecting channels happen in the Relex app. Relex output is legal information, not legal advice; a qualified lawyer reviews it before anyone relies on it.
Client support depends on the host product, plan and administrator settings. Gemini CLI support does not imply support in every Gemini web experience. Harvey BYOMCP is a customer-admin connection path, not a claim of Harvey Connector Library listing or approval. Check the current connector guides and portable-context guide.
https://relex.legal/api/mcp
Transport: Streamable HTTP (MCP). Auth: OAuth 2.1 + PKCE (browser sign-in with Google/Apple — no key to paste). Static API keys work as a CI/headless fallback.
Thirteen tools:
| Tool | Purpose |
|---|---|
list_matters | List up to 20 authorized matter references (caseId + deep link; no names or client identity) (read-only) |
read_matter_context | Read an authorized matter's saved, redacted context (read-only) |
diagnose_matter_sources | Per-source readiness, failure code and repair action (read-only) |
read_matter_source | Read one source's full redacted text in pages (read-only) |
save_matter_work_product | Save a draft or a new revision of one (revision-checked write) |
correct_matter_ontology | Apply typed ontology operations with evidence references (revision-checked write) |
conclude_matter_session | Conclude an open steering session; conclusions are saved to the matter thread (write) |
find_legal_professionals | Find published, professionally verified Marketplace profiles (read-only) |
read_legal_professional | Read a published profile and its request availability (read-only) |
prepare_professional_request | Prepare a request to a professional; returns an approval link, sends and charges nothing |
search | Discover API endpoints from the OpenAPI surface (read-only) |
read_api | Read one validated GET endpoint with the user's auth + PII guard (read-only) |
execute | Create, update or delete through one validated endpoint (POST/PUT/PATCH/DELETE) with the user's auth + PII guard |
The MCP handler lives in the Relex backend (/v1/mcp). This repo is configuration, skills, and install docs — not a separate server to host.
{
"mcpServers": { "relex": { "type": "http", "url": "https://relex.legal/api/mcp" } } }
Some clients use url / httpUrl instead of type+url. Same endpoint.
# Claude Code (HTTP + OAuth)
claude mcp add --transport http relex https://relex.legal/api/mcp
gemini mcp add --transport http relex https://relex.legal/api/mcp
claude mcp add --transport http relex https://relex.legal/api/mcp \ --header "Authorization: Bearer rlx_..."
After connect, say: "Set up my practice workflow with Relex."
Same MCP URL; different UI labels:
| Product | Official UI name |
|---|---|
| Claude | Custom connector |
| ChatGPT | App / custom MCP connector (Developer mode) |
| Grok.com | Connector → Custom |
| Grok Build | MCP server / plugin |
| Gemini CLI | MCP server |
| Gemini Enterprise | Custom MCP Server |
| Cursor / generic | MCP server |
Always name it Relex, URL https://relex.legal/api/mcp.
| Plan type | Who installs | Who signs in |
|---|---|---|
| Personal | You add the connector / app / MCP server | You Connect + OAuth |
| Team / Business / Enterprise | Owner or admin adds once | Each member finds Relex listed and Connects *their* Relex account |
Members on Team plans usually cannot add custom entries themselves.
Hosts that support MCP OAuth: unauthenticated call → 401 + WWW-Authenticate: resource_metadata=… → browser Google/Apple on relex.legal → bearer token on later search/read_api/execute. Full walkthrough: docs/oauth.md and https://relex.legal/docs/connectors/mcp
Full install flows: docs/install.md.
relex-mcp/
├── plugin/ │ ├── .mcp.json Remote MCP connector URL │ ├── skills/ PII-safe workflow skills (agent-agnostic) │ ├── agents/ Onboarding guide │ ├── commands/ /relex-setup, /relex-connect │ └── references/ ├── docs/ │ ├── install.md All clients + personal vs team │ ├── connect-generic.md Cursor, Windsurf, custom hosts │ └── positioning.md ├── SECURITY.md └── README.md
Act as senior counsel + steering layer over Relex's execution harness: start cases, steer drafting sessions, audit the case ontology, ground citations, run intake → e-sign → invoice — while never receiving names, national IDs, or document plaintext. Those steps deep-link into the browser.
AGPL-3.0-or-later — see LICENSE.
| Step | Where |
|---|---|
| Files are uploaded to a matter | Case page in the Relex app (https://relex.legal/dashboard/cases/{caseId}, Attach) |
| The assistant reads redacted sources | read_matter_context, read_matter_source (parties as [PARTY_NAME_n] labels) |
| The assistant saves its work | save_matter_work_product: markdown with label tokens, versioned in the matter |
| The user exports the finished document | Relex app: Word, PDF, Google Drive, signing, email. Labels become the parties' real details in the user's browser, after the user's PII password when parties are sealed |
Identity fields and original files never reach the assistant. The full guide, including ontology operations, agents and every endpoint area, is plugin/references/how-relex-works.md.
The hosted connector at https://relex.legal/api/mcp exposes thirteen tools: list_matters, read_matter_context, read_matter_source, diagnose_matter_sources, save_matter_work_product, correct_matter_ontology, conclude_matter_session, find_legal_professionals, read_legal_professional, prepare_professional_request, search, read_api, and execute. Auth is OAuth 2.1 + PKCE. The default connector scopes are relex.cases.read relex.cases.write relex.draft; these are the scopes the 401 WWW-Authenticate challenge requests. relex.agent is an optional fourth scope for agent features; the challenge omits it by design, and the OAuth metadata (scopes_supported) and the MCP server card list all four.
Generic remote MCP clients: point Streamable HTTP at https://relex.legal/api/mcp and complete browser OAuth.