[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Clio MCP server: Let your AI agent keep your Clio matters moving.

> Yes to both (checked 6 Nov 2026). Clio has a REST API, the Clio Manage API v4, with OAuth 2.0 and webhooks. Clio also hosts an MCP server at mcp.api.clio.com/mcp, listed in Claude's directory since October 2026, for people with a Clio Work license. Cotlet adds 13 Clio tools hosted, with no developer app, no API key from Clio and no Clio Work license.

Your agent finds matters, logs time and chases tasks in Clio Manage. You sign in once, with no developer app, no OAuth code and no server to host. It works inside the ChatGPT and Claude apps.

- Free 7-day trial, no card
- Unofficial, not affiliated with Clio
- Page: https://cotlet.dev/integrations/clio-api-mcp-server

## What can your AI agent do in Clio?

- Log time from your day notes
- Digest what is due per matter
- Chase overdue tasks
- Check time logged before billing
- Set up the file for a new matter
- Put court dates on the calendar

## Does Clio have an MCP server or an API?

- The API needs a developer application, OAuth 2.0 and a client you write and host. Clio's docs say private apps need a paid Clio account and that apps and integrations are not available on the EasyStart tier.
- The API allows 50 requests a minute per token during peak hours and 200 results a page. Clio has no sandbox: the 7-day trial account is the test account.
- Clio's MCP server signs you in with your Clio Identity login and read and write scopes. A third-party write-up of Clio's help article (2 Nov 2026) lists matter status, parties, deadlines, tasks, calendar and time logging, next to legal research with Vincent.

| What you need | Clio API v4 | Clio MCP (Clio Work) | Cotlet |
|---|---|---|---|
| Search matters, contacts and time entries | Yes, you code it | Matter status and parties | Yes |
| Log a time entry | Yes, you code it | Yes, with approval | Yes, after your OK |
| Create tasks, notes and calendar entries | Yes, you code it | Tasks and calendar: review | Yes, after your OK |
| Change a matter's status | Yes, you code it | Not listed | Yes, after your OK |
| No developer app or Clio Work license | Developer app | Clio Work license | Yes, your own sign-in |
| Runs in the ChatGPT and Claude apps, 24/7 | You build it | Claude and Codex | Yes, hosted |

Checked 6 Nov 2026. Sources: [Clio Developers: Clio Manage API](https://docs.developers.clio.com/api-docs/clio-manage/), [Clio Developers: Rate limits](https://docs.developers.clio.com/api-docs/clio-manage/rate-limits/), [Clio Developers: Webhooks guide](https://docs.developers.clio.com/guides/clio-manage/webhooks/), [Clio Developers: Building private apps](https://docs.developers.clio.com/handbook/getting-started/building-private-apps/), [Clio MCP server: OAuth metadata](https://mcp.api.clio.com/.well-known/oauth-protected-resource), [eSEOspace: Clio MCP server (2 Nov 2026)](https://eseospace.com/blog/clio-mcp-server/)

## How does the Clio MCP server work?

1. **Sign in to Clio.** Use your own login.
2. **Connect your AI agent.** Paste one Cotlet address.
3. **Ask in plain words.** Your agent works the matters.

We never keep your Clio password, and no time entry, task or note is saved until you approve it.

## How to connect Clio to your AI agent

Use MCP with your AI agent, or the same tools over REST in n8n, Make and scripts.

1. **Add the Cotlet address.** Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent.
2. **Enable Clio for agents.** Sign up, log in to Clio in its Cloud Browser, then press Enable for agents.
3. **Approve the connection.** Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console.

One shared address, `https://cotlet.dev/mcp/v1`, also carries Clio next to your other apps, whichever app you open first. If you enable Clio after connecting, refresh the connector so the new tools show up.

Claude:

```
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-clio \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

ChatGPT:

```
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
```

Cursor:

```
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-clio": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
```

Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet-clio]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

n8n:

```
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: clio_read
```

Make, Zapier:

```
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: clio_write
```

## All 13 Clio MCP tools

### Matters and contacts

Statuses are the three Clio uses: open, pending and closed. Find the client first, then the matter, and pass its ID to the other tools.

- **Search matters** (`search_matters`, read): Matters of your firm with status, client and responsible attorney.
- **Get matter** (`get_matter`, read): One matter with its status, dates, practice area and the people on it.
- **Search contacts** (`search_contacts`, read): People and companies in your Clio contacts.
- **Update matter status** (`update_matter_status`, write, asks first): Sets a matter to open, pending or closed.

### Time and bills

Hours are in hours, for example 1.5. Bills are read only: generating a bill stays in Clio.

- **List time entries** (`list_time_entries`, read): Time entries of a matter or a person, newest first.
- **List bills** (`list_bills`, read): Bills of a matter or client with date and total.
- **Create time entry** (`create_time_entry`, write, asks first): Logs time on a matter.

### Tasks, notes and calendar

A new task needs a name and an assignee. A task is reopened in Clio, not with these tools.

- **List tasks** (`list_tasks`, read): Tasks with due date, assignee and matter.
- **Create task** (`create_task`, write, asks first): Adds a task, with an assignee and a due date, to a matter.
- **Complete task** (`complete_task`, write, asks first): Marks a task as complete.
- **Create matter note** (`create_matter_note`, write, asks first): Adds a note to a matter.
- **List calendar entries** (`list_calendar_entries`, read): Calendar entries in a date range, with matter and location.
- **Create calendar entry** (`create_calendar_entry`, write, asks first): Adds a calendar entry, optionally on a matter.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/clio-api-mcp-server#tools

## Who can see my Clio session, and how do I revoke it?

- **What we store.** Your logged-in Clio profile, encrypted with AES-256-GCM, in Finland. Not the password.
- **What your agent gets.** The 13 Clio tools. Never the cookie or your login.
- **What the session sees.** What your Clio role sees: matters, contacts, time, tasks, bills.
- **What no tool touches.** Generating bills, trust accounting, users, settings and deleting.
- **If Clio asks you to sign in.** You sign in again in your own browser, with your two-step verification. We never type it.
- **How to cut access.** Disable for agents, reset the browser, or sign out in Clio.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)).

## What can the agent do in my Clio?

You sign in with your own Clio login, so the agent sees and changes only what that login can. Clio's docs say a user can only see matters their role and permissions allow (Matters guide, 6 Nov 2026). A matter you cannot open fails with a permission error.

Time entries, tasks, notes and calendar entries show up in Clio the way your own do, under your name. Writes that others will see wait for your OK.

How your Clio stays in your hands:

- Your own login and two-step verification, signed in by you
- The agent works inside your Clio role
- Time, tasks, notes and calendar entries wait for your OK by default
- No tool deletes a matter, entry, task or note
- You can switch the wait off per tool for a scheduled run

## What happens when Clio changes?

- **12 h** between tests of the Clio tools
- **$0** for a call to a Clio tool paused for repair

When a Clio screen moves or a field is renamed, the fix happens on our side and your prompts keep working. [status.cotlet.dev](https://status.cotlet.dev) watches the site, console and API every 3 minutes.

## Approvals, undo and mistakes

1. **Finds the matter.** By client or number. Two matches stop the run and ask you.
2. **Prepares the entry.** Date, hours and a description in your own words.
3. **Waits for your OK.** The entry shows up in your Cotlet console first.
4. **Reports the result.** Matter, entry ID, time of saving.

| Action | Undo |
|---|---|
| Log a time entry | Fix it in Clio; no Cotlet tool deletes it |
| Create a task | Fix it in Clio; the assignee already sees it |
| Complete a task | Reopen it in Clio, not with this tool |
| Add a matter note | Fix it in Clio; everyone with access to the matter sees it |
| Create a calendar entry | Fix it in Clio; attendees you added already see it |
| Change a matter status | Set the old status again with the same tool |

All 6 write tools ask first: create_time_entry, create_task, complete_task, create_matter_note, create_calendar_entry, update_matter_status. Reads reach nobody and run at once. Switch the wait off per tool for a scheduled run.

> Clio records the open, pending or close date when a status changes, so check the date before you let the agent move matters.

MCP call:

```
{
  "name": "create_time_entry",
  "arguments": {
    "matter_id": 1042871,
    "date": "2026-11-05",
    "hours": 1.5,
    "description": "Call with opposing counsel"
  }
}
```

REST:

```
curl -X POST https://cotlet.dev/api/v1/clio/matters/1042871/time-entries \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-11-05","hours":1.5,"description":"Call with opposing counsel"}'
```

Tool output:

```
{
  "id": 7730455,
  "matter_id": 1042871,
  "date": "2026-11-05",
  "hours": 1.5,
  "description": "Call with opposing counsel",
  "user": "Dana Cole"
}
```

Scripts and cron jobs reach the same tools over REST at `/api/v1/clio`, with the same key and price. A write over REST waits for your OK too and answers 202 until you approve it. A failed call costs nothing. The tools table lists the REST path of each tool.

## How much does the Clio MCP server cost?

**About $20 a month** for one lawyer with one Clio login, 3,440 credits. Your Clio plan is billed by Clio as before.

| Job | Calls | Credits |
|---|---|---|
| Log time from day notes, daily | 5 × 20 | 1,000 |
| Overdue tasks, daily | 2 × 20 | 400 |
| Digest of open matters, weekly | 3 × 4 | 120 |
| Time check before billing, 4 matters | 3 × 4 | 120 |
| File setup for a new matter | 6 × 3 | 180 |
| Court date on the calendar | 2 × 6 | 120 |
| Cloud Browser, 30 days |  | 1,500 |
| Total |  | 3,440 |

- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No Clio developer app and no Clio Work license to buy

The month is our example: 20 working days and about 4 time entries a day. Clio projects the average lawyer's billable time at 42.2% of an eight-hour day in 2026, about 3.4 hours (Above the Law on Clio's 2026 Legal Trends Report, 6 Nov 2026). No public figure for matters or tasks per lawyer exists, so those counts are our assumption. Dollars at the $29 pack rate.

## Clio MCP server on GitHub, Zapier or hosted: which to use

| Option | What it does | Where it stops |
|---|---|---|
| [oktopeak/clio-mcp](https://github.com/oktopeak/clio-mcp) | MIT, Node. 37 tools per its README, 12 of them writes, with a read-only switch. 27 stars, last commit 3 Nov 2026. The vendor also deploys it for a firm, $300 a month. | You register your own Clio developer app and run it, on your computer by default. |
| [lawyered0/clio-mcp](https://github.com/lawyered0/clio-mcp) | MIT, Python. 10 tools: contacts, matters, flat-fee matter setup, activities. 8 stars, last commit 5 Nov 2026. | Your own developer app. No tasks or calendar tools. |
| [ToddHebebrand/ClioMCP](https://github.com/ToddHebebrand/ClioMCP) | About 46 tools in seven groups per its README. 0 stars, last commit 12 Aug 2026. | No license file. You host it with your own OAuth setup. |
| [Zapier MCP for Clio](https://zapier.com/mcp/clio) | Hosted. Actions such as create time entry, create task, create matter, update matter and create matter note, plus instant triggers in the Zapier app. | Zapier's list of actions and fields, and a Zapier account. |
| [Elaichi](https://elaichi.ai/connectors/clio/) | Hosted MCP with 304 Clio Manage tools per its page, for Claude, ChatGPT, Cursor and Copilot. $15 per user per month on its Gold plan, 14-day trial. | Priced per user and built for company teams with admin controls. |
| [Clio's own MCP server](https://mcp.api.clio.com/.well-known/oauth-protected-resource) | Hosted by Clio at mcp.api.clio.com/mcp with Clio Identity sign-in. Legal research with Vincent plus matter records. | Needs a Clio Work license. Claude and Codex, per the write-up of 2 Nov 2026. |

Clio's own server fits a firm that already has Clio Work and wants research and drafting. The GitHub servers fit someone who is happy to register a developer app and run one. Cotlet is for the lawyer or firm admin who wants the same matter jobs inside ChatGPT or Claude, under their own login, with no developer app, no Clio Work license and one account for the other apps they use.

## Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), working since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Clio tools.

## Clio MCP server: questions

### How do I connect Clio to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Clio once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Clio account through Cotlet, in their phone apps too.

### What can ChatGPT do in Clio?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Clio: log time from your day notes; send a weekly status digest per matter; chase overdue tasks. You ask in plain words, and anything that reaches other people waits for your OK first.

### Does Clio have an official MCP server?

Yes (checked 6 Nov 2026). Clio hosts one at mcp.api.clio.com/mcp, with Clio Identity sign-in and read and write scopes, and a third-party write-up of Clio's help article (2 Nov 2026) says it needs a Clio Work license and is listed in Claude's directory since October 2026. Its focus is legal research with Vincent, plus matter status, tasks, calendar and time.

### How do I get access?

Create a free account at https://cotlet.dev, open Clio under Integrations in the console and log in to Clio in its Cloud Browser. The trial starts with your first app, no card asked.

### How do I connect Clio to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Clio once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Clio account through Cotlet, in their phone apps too.

### What can ChatGPT do in Clio?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Clio: log time from your day notes; send a weekly status digest per matter; chase overdue tasks. You ask in plain words, and anything that reaches other people waits for your OK first.

### Do I need a Clio developer app or a Clio Work license?

No. Cotlet works through your own Clio login, so you register no developer application and need no Clio Work license. Clio's API needs a developer application with OAuth 2.0 (Clio Developers), and Clio's MCP plugin is for Vincent and Clio Work customers (Clio press, 17 Sep 2026).

### Does my agent see every matter in the firm?

No. What your agent sees follows the role and permissions of the Clio account you sign in with. Clio's own API limits results the same way (Clio Developers, Matters guide). A call on a matter you cannot open fails with APP_PERMISSION_DENIED.

### Does Clio have webhooks?

Yes, in the API (Clio Developers, 6 Nov 2026): matters, tasks, activities, bills, calendar entries and more can send created, updated and deleted events. The Cotlet tools do not receive them. Run your agent on a schedule instead, for example a daily list_tasks pass.

### Does it work with Claude and ChatGPT in the browser or on my phone?

Yes. Cotlet is hosted, so the chat apps reach it by the shared address. Nothing runs on your computer.

### Can I use it without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n or Make with your Cotlet key. The same tools, inputs and price as MCP.

### Is Cotlet affiliated with Clio?

No. Cotlet is independent and not affiliated with Clio or Themis Solutions Inc.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
