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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect LawVu to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect LawVu once
-
Open Connections, choose Add connection, and pick LawVu.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in LawVu. LawVu's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
LawVu MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect LawVu to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with LawVu through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Legal
Get the story on a matter before the meeting
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.
-
Legal
Open a matter from a request
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.
-
Sales
Check where a customer contract stands
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.
-
Procurement
Kick off a vendor contract review
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.
-
Compliance
Find the policy answer in LawVu knowledge
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.
-
HR
Keep employment matters moving after a call
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.
Try asking
- “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”
Compare
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting LawVu gets you
5 screens from the product, each doing one job for your LawVu account.
The agent
Ask about a matter in plain words.
Three starter prompts pull live answers from LawVu matters, contracts and knowledge.
- matters
- contracts
- tasks
- workflows
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings LawVu to every client.
Claude, ChatGPT and Cursor use LawVu through one governed endpoint, no SDK or shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own LawVu toolbox.
Legal, procurement and sales each see a toolbox scoped to the work they do.
- Legal
- Sales
- Procurement
- Compliance
ElaichiToolboxesShared connections
Teammates work in LawVu without a credential.
One person connects LawVu, shares it with teams, and nobody else handles a login.
- Legal
- Sales
- Procurement
- Compliance
ElaichiConnectionsAudit log
Every LawVu call answers who did what.
When, who, what happened, type and resource, written to a log nobody can edit.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the LawVu digest itself.
Open matters are fetched, grouped and drafted into a digest a person approves before posting.
LawVu digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch matters
LawVu
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
LawVu
Queued
Collections and dashboards
LawVu health numbers arrive without being asked.
Matters created over 14 days, by team, computed on a schedule without a model.
LawVu health
Refreshed 4 minutes ago · every 15 minutes · from the matters collection
Matters
1,284 ↓ 12%
Contracts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Matters created
Last 14 days
By team
Share of activity
Legal 34%
Sales 27%
Procurement 21%
Compliance 18%
Related connectors
More from the catalog
FAQ
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 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.
Put LawVu in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.