# LawVu MCP connector

The LawVu connector brings matters, contracts, tasks and legal knowledge into Claude, ChatGPT and Cursor, so each person can search, summarize, open matters and start contract workflows inside their own LawVu access, with every call logged.

Source: https://elaichi.ai/connectors/lawvu/

## Facts

| | |
| --- | --- |
| Application | LawVu |
| Category | Compliance |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. LawVu builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@lawvu.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once LawVu is connected

- Summarize the open matters for the sales team this month
- Where does the Acme master services agreement stand?
- Create a matter for the new vendor NDA and add tasks

## Connect LawVu in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick LawVu.
2. Optionally set Share with, then press Connect.
3. Approve it in LawVu. LawVu's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which LawVu tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## LawVu MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## LawVu MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## LawVu MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect LawVu to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a LawVu tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with LawVu through Elaichi

### Get the story on a matter before the meeting

Legal. Ask for a summary of a matter, its latest updates and its open tasks before you walk into the steering meeting. The answer comes from the live LawVu record, not from memory.

### Open a matter from a request

Legal. Turn a request from the business into a new LawVu matter with the right details filled in, and add the first tasks so the work has an owner from the start.

### Check where a customer contract stands

Sales. Ask whether the agreement for an account is signed, still in review, or waiting on the other side, without pinging the legal team on a Friday afternoon.

### Kick off a vendor contract review

Procurement. Start the contract workflow for a new supplier agreement in LawVu from the conversation you are already having, instead of logging in and clicking through the form.

### Find the policy answer in LawVu knowledge

Compliance. Ask what the company position is on data retention or gifts from suppliers and get the answer from the LawVu knowledge base, with the source it came from.

### Keep employment matters moving after a call

HR. After a call with a lawyer, add the follow-up tasks to the matter right away so nothing waits on someone remembering to update LawVu later.

## Elaichi vs Zapier MCP vs Composio for LawVu

All three can connect LawVu to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over LawVu tools | Allow or restrict single LawVu tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per LawVu call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect LawVu to Claude?

Two steps. In Elaichi, choose LawVu and sign in with your normal LawVu login on LawVu's own sign-in page, since the connector connects over OAuth and there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. From then on Claude can work with LawVu matters, contracts and knowledge as you.

### Does LawVu work with ChatGPT and Cursor as well as Claude?

Yes. Once LawVu is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect LawVu once and every client you use picks it up.

### What can an AI agent actually do with my LawVu data?

It can search LawVu matters, contracts and knowledge and summarize what it finds, so you can ask where an agreement stands or what is open on a matter. It can also create a new matter, add tasks to one, and start a contract workflow. Short, concrete asks work best, such as the name of the matter or the counterparty rather than a long paragraph.

### Does connecting LawVu give the AI everything in my workspace?

No. Every call runs inside the LawVu access of the person who signed in, so the agent sees the matters, contracts and knowledge that person can already see in LawVu, and nothing more. Elaichi can narrow that access further for a team or a person, but it can never widen it beyond what LawVu itself allows.

### Can my team share one LawVu connection?

Yes. One person connects LawVu in Elaichi and shares the connection with a team, and nobody else ever handles a credential or a login. Each person still signs in to Elaichi as themselves, so the audit log names who opened a matter or started a workflow, even on a shared LawVu connection.

### Can I stop an agent from changing or creating things in LawVu?

Yes. Restrictions in Elaichi apply per action, so you can allow searching and summarizing LawVu matters and contracts while blocking creating matters, adding tasks or starting workflows. A restricted action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.

### What happens to a LawVu connection when someone leaves?

Offboarding a person in Elaichi ends their access to LawVu through every client at once. A LawVu connection shared with a team keeps working for everyone else on it. If you ever want LawVu gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

### Does the LawVu MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. LawVu is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for LawVu?

Yes. Both let Claude, ChatGPT or Cursor use LawVu. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every LawVu call.

### How is Elaichi different from Composio for LawVu?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to LawVu: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.