Bring the legislation into your conversation.

Run this command in a terminal with Codex CLI installed:

codex mcp add legum-law --url https://law.legumlawfirm.co/mcp

Alternatively, merge this entry into your user configuration at ~/.codex/config.toml:

[mcp_servers.legum-law]
url = "https://law.legumlawfirm.co/mcp"

Use codex mcp list to confirm the entry, then start a new Codex session and check that the tools are available. MCP configuration is shared by supported Codex surfaces; organization policy may restrict it.

Official Codex MCP documentation

Use ChatGPT’s custom remote MCP connection flow where it is available to your account. In the current developer documentation, open Plugins, select the plus button and choose Add custom MCP server. Enter a name such as Legum Legal Resources and the endpoint URL, choose no authentication where prompted, then review the discovered tools.

Some workspaces expose creation through Apps and developer mode instead. Availability and publishing permissions depend on your plan and workspace settings. After installation, select the integration in a new conversation. If custom MCP creation is absent, check the official guide or ask your workspace administrator.

Official ChatGPT connection guide

Add the remote server from a terminal:

claude mcp add --transport http legum-law https://law.legumlawfirm.co/mcp

Start Claude Code and use /mcp to inspect the connection and tools. The default scope is local to the current project; choose a different scope only if you want the configuration shared more widely.

Official Claude Code MCP guide

Open Customize → Connectors, choose + Add → Add custom connector, then supply the name Legum Legal Resources and the endpoint URL. Continue and enable the connector for your conversation. Legum does not require a separate sign-in.

Team and Enterprise workspaces may require an owner to add the custom web connector in organization settings before members can enable it. Follow the provider’s current instructions for your account.

Official Claude custom connector guide

In VS Code, select your agent harness, then run Chat: Open Customizations from the Command Palette. Open MCP Servers, choose Add Server, select HTTP, enter the endpoint URL, and choose a configuration destination. MCP: Add Server is another way to open the guided setup. To share the connection with a compatible Copilot workspace, merge this into the workspace-root .mcp.json:

{
  "mcpServers": {
    "legum-law": {
      "type": "http",
      "url": "https://law.legumlawfirm.co/mcp"
    }
  }
}

Review and trust the server when prompted, then enable its tools in a compatible agent chat. Available features depend on your selected agent and organization policy.

Official VS Code MCP guide

Merge this entry into the mcpServers object in your Gemini CLI settings.json, at user scope (~/.gemini/settings.json) or project scope (.gemini/settings.json):

{
  "mcpServers": {
    "legum-law": {
      "httpUrl": "https://law.legumlawfirm.co/mcp"
    }
  }
}

Restart Gemini CLI and inspect its MCP server list. This configuration is for Gemini CLI; it does not imply support in the consumer Gemini web app.

Official Gemini CLI MCP guide

Check the exact endpoint, including /mcp, and select Streamable HTTP rather than a local command or legacy SSE configuration. A normal browser visit is not a complete MCP connection test. Check the client’s MCP status and error log; a gateway error or unavailable endpoint requires the service to be restored before retrying.

The Legum endpoint needs no account or token. Choose no authentication if your client offers it. Your assistant provider may still require you to sign in to its own service. If it insists on OAuth for this endpoint, check that it supports unauthenticated remote MCP and that the URL is correct.

Restart or reconnect the client after adding the server. Review its tool-selection and trust settings, and check whether workspace policy permits custom MCP servers. This service exposes the three tools listed above; it does not grant access to the rest of your assistant’s tools.

Try the official title and jurisdiction, then retrieve an enactment using an identifier returned by search. Check the enactment’s provision identifiers rather than assuming every provision uses a section number. The collection may not contain the law or edition you need. Browse the legislation catalogue directly as a fallback.