# Clio Grow MCP connector

The Clio Grow connector brings inbox leads, contacts, matters, notes and marketing campaigns into Claude, ChatGPT, Cursor and Microsoft Copilot, where each person works under their own Clio Grow sign-in and every call is logged.

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

## Facts

| | |
| --- | --- |
| Application | Clio Grow |
| Category | CRM |
| AI tools | 26 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, 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 Clio Grow is connected

- Add a contact note for Maria Lopez about today's consultation
- Which inbox leads came in this week and from which campaign?
- Show me the matter notes for the Harrington estate matter

## Connect Clio Grow in Elaichi

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

1. Open Connections, choose Add connection, and pick Clio Grow.
2. Optionally set Share with, then press Connect.
3. Supply your own Clio Grow app, then approve. Clio Grow needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

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

## Clio Grow 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.

## Clio Grow MCP connector for Claude Code

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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`.

## Clio Grow 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. The plugin directory lives at chatgpt.com/plugins.

## Clio Grow 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.

## Clio Grow MCP connector for Microsoft Copilot

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

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.
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.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Clio Grow 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

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Clio Grow tool needs "Use your connected apps". 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. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Clio Grow through Elaichi

### Log a new lead straight from the call

Intake. Ask the agent to create an inbox lead in Clio Grow with the caller's name, contact details and what they need, before the next call starts.

### Catch a contact up after a consultation

Intake. Add a contact note in Clio Grow with what was discussed, what the prospect decided and what happens next, so whoever picks it up knows where things stand.

### See which campaigns bring in leads

Marketing. Pull up Clio Grow marketing campaigns and inbox leads together to see where this month's prospects came from, and add a new source when a referral channel starts producing.

### Check a matter's history before a meeting

Attorneys. Ask for a Clio Grow matter by name, read its matter notes in one place, then add a note with what the client agreed.

### Keep matter types and locations current

Office administration. Add a new matter type when the firm takes on a new practice area, or create a location when an office opens, without clicking through settings.

### Review the intake pipeline each Monday

Firm leadership. List open inbox leads and recent matters in Clio Grow, see which team members are handling them, and ask for a plain summary of what moved this week.

## Elaichi vs Zapier MCP vs Composio for Clio Grow

All three can connect Clio Grow 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 Clio Grow tools | Allow or restrict single Clio Grow 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 Clio Grow 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](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 Clio Grow to Claude?

Connect Clio Grow in Elaichi first. Clio Grow requires an OAuth application registered inside Clio Grow itself, so one person at your firm creates it there, pastes its client ID and secret into Elaichi once, and then signs in to Clio Grow in the usual authorization window. After that, open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Nobody else at the firm ever handles that client ID or secret again.

### Does Clio Grow work with ChatGPT and Cursor as well as Claude?

Yes. Once Clio Grow 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 Clio Grow once and every client picks it up.

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

It can list and look up inbox leads, contacts, matters, matter types, locations and marketing campaigns in Clio Grow, and read the notes on a contact or a matter. It can also add new inbox leads, contact notes, matter notes, matter types, locations and sources. Short, specific asks such as adding a note to the Patel matter work better than long paragraphs.

### Does connecting Clio Grow give the AI everything in the firm's account?

No. Every call runs as the person who signed in to Clio Grow, so the agent sees the leads, contacts and matters that person can already see in Clio Grow, and nothing more. Elaichi can narrow that further by role or by person, and it can never widen it beyond what Clio Grow itself allows.

### Can my team share one Clio Grow connection?

Yes. One person connects Clio Grow in Elaichi and shares it with a team, and nobody else needs the client ID, the secret or any other credential. Each teammate still signs in to Elaichi as themselves, so every note added or lead created in Clio Grow is logged under their own name.

### Can I stop an agent from deleting or changing things in Clio Grow?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting a Clio Grow custom action, or creating a matter type, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it however the prompt is worded.

### What happens to a Clio Grow connection when someone leaves?

Offboarding that person in Elaichi ends their access to Clio Grow through every client at once. If they had shared the Clio Grow connection with a team, it keeps working for everyone else. Disconnecting Clio Grow once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

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

Yes. Clio Grow 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 Clio Grow?

Yes. Both let Claude, ChatGPT or Cursor use Clio Grow. 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 Clio Grow call.

### How is Elaichi different from Composio for Clio Grow?

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 Clio Grow: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 26 Clio Grow tools

Every tool below is callable through https://api.elaichi.ai/mcp once Clio Grow is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Clio Grow contact note** (Create). Create a note for a contact. Creates a new note for a contact. Required: contact_id, data.
- **List all Clio Grow contact notes** (List). List notes for a contact. Returns a paginated list of notes for a contact. Required: contact_id. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Get single Clio Grow contact by ID** (Get). Get a contact. Returns a single contact by ID. Required: id.
- **List all Clio Grow contacts** (List). List contacts. Returns a paginated list of contacts. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **List all Clio Grow current users** (List). Get current user. Returns the currently authenticated user.
- **Create a Clio Grow custom action** (Create). Create a custom action. Creates a new custom action. Required: data.
- **Delete a Clio Grow custom action by ID** (Delete). Delete a custom action. Deletes a single custom action by ID. Required: id.
- **List all Clio Grow custom actions** (List). List custom actions. Returns a paginated list of custom actions. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Create a Clio Grow inbox lead** (Create). Create an inbox lead. Creates a new inbox lead. Required: data.
- **Get single Clio Grow inbox lead by ID** (Get). Get an inbox lead. Returns a single inbox lead by ID. Required: id.
- **List all Clio Grow inbox leads** (List). List inbox leads. Returns a paginated list of inbox leads filtered by state. Required: state. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Create a Clio Grow location** (Create). Create a location. Creates a new location for the account. Required: data.
- **Get single Clio Grow location by ID** (Get). Get a location. Returns a single location by ID. Required: id.
- **List all Clio Grow locations** (List). List locations. Returns a paginated list of the account's locations. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Get single Clio Grow marketing campaign by ID** (Get). Get a marketing campaign. Returns a single marketing campaign by ID. Required: id.
- **List all Clio Grow marketing campaigns** (List). List marketing campaigns. Returns a paginated list of the account's marketing campaigns. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Create a Clio Grow matter note** (Create). Create a matter note. Creates a new note for a matter. Required: matter_id, data.
- **List all Clio Grow matter notes** (List). List matter notes. Returns a paginated list of notes for a matter. Required: matter_id. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Create a Clio Grow matter type** (Create). Create a matter type. Creates a new matter type for the account. Required: data.
- **Get single Clio Grow matter type by ID** (Get). Get a matter type. Returns a single matter type by ID. Required: id.
- **List all Clio Grow matter types** (List). List matter types. Returns a paginated list of the account's matter types. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Get single Clio Grow matter by ID** (Get). Get a matter. Returns a single matter by ID. Required: id.
- **List all Clio Grow matters** (List). List matters. Returns a paginated list of matters. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
- **Create a Clio Grow source** (Create). Create a lead source. Creates a new lead source for the account. Required: data. Clio documents no OAuth scope for Sources; the app's permissions decide access.
- **List all Clio Grow sources** (List). List lead sources. Returns a paginated list of the account's lead sources. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2. Clio documents no OAuth scope for Sources; the app's permissions decide access.
- **List all Clio Grow users** (List). List users. Returns a paginated list of users in the current account. The connector pages through all results (Clio returns up to 200 a page). ids filters by record ids (up to 50), sent as ids[]=1&ids[]=2.
