Connect Clio to Claude Code

Make Claude open matters and log billable time in Clio. From the terminal, inside the sessions where you already work.

How do you connect Clio to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Clio, you add a Clio MCP server: a small hosted service that exposes Clio's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Clio account. No API keys pasted into config files.

claude mcp add --transport http clio https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Clio once connected?

Full read-write Clio access lets Claude open a matter, add a contact, create and assign tasks, log billable time against the right matter, and update activity notes after you approve. The intake and admin steps that usually mean tabbing through Clio happen inside the matter you are already working on.

Open a new matter and attach the relevant contact
Create and assign tasks with due dates against a matter
Log a billable time entry to the correct matter and activity
Add or update a contact record
Draft an activity note or matter update for your review
Create a calendar entry tied to a matter

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Clio access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Clio API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Clio changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Clio connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Clio connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Clio account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Clio's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Clio?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Clio account it signs in with. Revoking access is one click in Clio.

More on the Clio connector

Clio connector for claude.ai DocuSign + Claude Code Custom CRM + Claude Code Outlook + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us