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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize the open matters for the sales team this month
Working in LawVu with Elaichi
-
Looked in LawVu
How to connect LawVu to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
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. 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.
LawVu MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with LawVu through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in LawVu is logged.
-
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”
What connecting LawVu gets you
5 screens from Elaichi, each doing one job for your LawVu account.
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, Cursor or Microsoft Copilot
The agent
Ask about a matter in plain words.
Three starter prompts pull live answers from LawVu matters, contracts and knowledge.
Copy the endpoint
AI apps
One endpoint brings LawVu to every client.
Claude, ChatGPT, Cursor and Microsoft Copilot use LawVu through one governed endpoint, no SDK or shared key.
Toolboxes
Each team gets its own LawVu toolbox.
Legal, procurement and sales each see a toolbox scoped to the work they do.
Shared connections
Teammates work in LawVu without a credential.
One person connects LawVu, shares it with teams, and nobody else handles a login.
Audit log
Every LawVu call answers who did what.
When, who, what happened, type and resource, written to a log nobody can edit.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
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 Jake Morgan
Approve Deny -
Post the digest
LawVu
Queued
Workflows
A schedule starts the LawVu digest itself.
Open matters are fetched, grouped and drafted into a digest a person approves before posting.
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%
Collections and dashboards
LawVu health numbers arrive without being asked.
Matters created over 14 days, by team, computed on a schedule without a model.
Why connect LawVu's MCP server through Elaichi
LawVu builds and runs this MCP server. Elaichi sits in front of it, so LawVu's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to LawVu's server directly, outside Elaichi, get none of this.
-
One address for every AI client
Claude, ChatGPT, Cursor and Microsoft Copilot reach LawVu's tools at the same Elaichi address as every other connected app. Nobody adds LawVu's server to each client one by one.
-
Each person signs in as themselves
Each person signs in to Elaichi as themselves. Members connect with their own LawVu sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
-
Rules checked before a call leaves
Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches LawVu's server. By default, a tool LawVu does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.
-
One audit log for every app
Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
-
Tool issues go to LawVu
LawVu builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the LawVu team.
For IT and engineering
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 | Free for one person; $15 per user per month on Gold. | 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.
Questions, answered
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, Microsoft Copilot, 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 role 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 restricting creating matters, adding tasks or starting workflows. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot