# Docketwise MCP connector

The Docketwise connector brings your immigration firm's matters, contacts, documents, charges and invoices to Claude, ChatGPT, Cursor and Microsoft Copilot, so each person can ask about cases and update records inside their own Docketwise access.

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

## Facts

| | |
| --- | --- |
| Application | Docketwise |
| Category | CRM |
| AI tools | 30 |
| 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 Docketwise is connected

- List open matters for Maria Lopez with their current status.
- Draft an invoice for the Chen matter from this month's charges.
- Which invoices are still unpaid, and which matters are they on?

## Connect Docketwise in Elaichi

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

1. Open Connections, choose Add connection, and pick Docketwise.
2. Optionally set Share with, then press Connect.
3. Supply your own Docketwise app, then approve. Docketwise 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 Docketwise tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

## Docketwise 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`.

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

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

## Docketwise 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 Docketwise 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 Docketwise 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 Docketwise through Elaichi

### Open a matter the moment a consult ends

Intake. Add the new client as a Docketwise contact and create the matter with the right matter type while the details are still fresh. Nobody retypes the notes into Docketwise later.

### See where every case stands

Paralegals. Ask which matters are in a given status, which ones have a document on file, and which are missing one. Get a plain list instead of clicking through each matter.

### Pull the client file before a call

Attorneys. Get the contact, their open matters and the documents attached to each, summarized in a few lines. Walk into the call knowing what was filed and when.

### Turn logged charges into an invoice

Billing. List the charges on a matter, check them, and create the Docketwise invoice from them. Correct a charge or an invoice amount without leaving the conversation.

### Chase the invoices that are still unpaid

Finance. List invoices and matter receipts to see what has been paid and what has not. Ask for the matters with an outstanding balance and start from there.

### Keep contact details current

Operations. Update a client's address, phone or country of citizenship in Docketwise when they tell you it changed. Remove duplicate contacts that crept in from old intake forms.

## Elaichi vs Zapier MCP vs Composio for Docketwise

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

Connect Docketwise in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Docketwise connects over OAuth, but it requires an OAuth application registered inside Docketwise itself, so one person at your firm brings a client ID and secret once when setting up the connection. After that, everyone signs in to Docketwise with their own login and nobody else touches a key.

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

Yes. Once Docketwise 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 Docketwise once, not once per client.

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

It can look up contacts and matters, tell you a matter's status and type, list the documents on a case and fetch a document, and create new contacts, matters and documents. It can also list, create and update charges and invoices in Docketwise and show matter receipts, so billing questions get a direct answer. Short, specific asks such as "list open matters for this contact" work better than long paragraphs.

### Does connecting Docketwise give the AI everything in my firm's account?

No. Every call runs as the person who signed in to Docketwise, so the agent sees exactly the matters, contacts and invoices that person already sees, and nothing more. Elaichi can narrow that further with roles and restrictions, but it can never widen what Docketwise itself allows.

### Can my team share one Docketwise connection?

Yes. One person connects Docketwise in Elaichi and shares the connection with a team, so nobody else handles the client ID or secret. Each teammate still signs in as themselves, so every matter created or invoice updated is logged under their own name.

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

Yes. Restrictions in Elaichi work per action, so you can restrict deleting contacts or charges in Docketwise, or updating invoices, 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 no matter how the prompt is worded.

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

Offboarding a person in Elaichi ends their access to Docketwise through every client at once. A shared Docketwise connection keeps working for everyone else on the team. If you disconnect Docketwise in Elaichi, it disappears from Claude, ChatGPT, Cursor and every other client in one step.

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

Yes. Docketwise 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 Docketwise?

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

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

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

## All 30 Docketwise tools

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

- **List all Docketwise charges** (List). Lists an invoice's charges. Required: invoice_id. The connector pages through every page (200 records a page) by the X-Pagination header.
- **Create a Docketwise charge** (Create). Creates a charge on an invoice. Send the fields inside the charge root key: {"charge": {...}}. Required: invoice_id, charge, charge.amount, charge.status, charge.date.
- **Update a Docketwise charge by ID** (Update). Updates a charge. Send the fields inside the charge root key. Required: id, charge.
- **Delete a Docketwise charge by ID** (Delete). Deletes a charge. Required: id.
- **List all Docketwise contacts** (List). Lists the firm's contacts (people and institutions). The connector pages through every page (200 records a page) by the X-Pagination header.
- **Create a Docketwise contact** (Create). Creates a contact. Send the fields inside the contact root key: {"contact": {...}}; addresses_attributes and phone_numbers_attributes take a list of {"data": {...}}. Required: contact.
- **Get single Docketwise contact by ID** (Get). Returns a contact with its physical address and notes. Required: id.
- **Update a Docketwise contact by ID** (Update). Updates a contact. Send the fields inside the contact root key; to change an existing address or phone number, include its id in data. Required: id, contact.
- **Delete a Docketwise contact by ID** (Delete). Deletes a contact. Required: id.
- **List all Docketwise countries** (List). Lists the countries Docketwise knows. The connector pages through every page (200 records a page) by the X-Pagination header.
- **Get single Docketwise document download URL by ID** (Get). Returns a public download URL for the document, valid for 1 hour: {"url": "..."}. Required: id.
- **List all Docketwise documents** (List). Lists the firm's documents. The connector pages through every page (200 records a page) by the X-Pagination header.
- **Create a Docketwise document** (Create). Uploads a document. Send the fields inside the document root key: {"document": {...}}, with the file as strict base64 in base64_data and its name (with the extension) in filename. Required: document.
- **Get single Docketwise document by ID** (Get). Returns a document's details (title, size, client, doc_url). Required: id.
- **List all Docketwise invoices** (List). Lists the firm's invoices. The connector pages through every page (200 records a page) by the X-Pagination header.
- **Create a Docketwise invoice** (Create). Creates an invoice. Send the fields inside the invoice root key: {"invoice": {...}}. Required: invoice, invoice.contact_id.
- **Get single Docketwise invoice by ID** (Get). Returns an invoice with its invoice_matters. Required: id.
- **Update a Docketwise invoice by ID** (Update). Updates an invoice. Send the fields inside the invoice root key; Docketwise requires contact_id on updates too. Required: id, invoice, invoice.contact_id.
- **List all Docketwise matter receipts** (List). Lists a matter's receipts (immigration receipt numbers). Required: matter_id.
- **List all Docketwise matter statuses** (List). Lists the firm's matter statuses. The connector pages through every page (200 records a page) by the X-Pagination header.
- **List all Docketwise matter types** (List). Lists the firm's matter types, each with its matter statuses. The connector pages through every page (200 records a page) by the X-Pagination header.
- **List all Docketwise matters** (List). Lists the firm's matters (cases). The connector pages through every page (200 records a page) by the X-Pagination header.
- **Create a Docketwise matter** (Create). Creates a matter. Send the fields inside the matter root key: {"matter": {...}}. Required: matter, matter.client_id.
- **Get single Docketwise matter by ID** (Get). Returns a matter with its user_ids, receipts, client and notes. Required: id.
- **Update a Docketwise matter by ID** (Update). Updates a matter. Send the fields inside the matter root key; Docketwise requires client_id on updates too. Required: id, matter, matter.client_id.
- **Delete a Docketwise matter by ID** (Delete). Deletes a matter. Required: id.
- **Create a Docketwise note** (Create). Creates a note on a matter or a contact (matter_id or client_id is required). The body is bare (no root key).
- **Update a Docketwise note by ID** (Update). Updates a note (matter_id or client_id is required). The body is bare (no root key); Docketwise answers {"success": "Note updated successfully."}. Required: id.
- **Delete a Docketwise note by ID** (Delete). Deletes a note. Required: id.
- **List all Docketwise users** (List). Lists the firm's users (with their attorney profile). The connector pages through every page (200 records a page) by the X-Pagination header.
