Connect MyCase to Claude Code

Make Claude log time and move matters forward in MyCase. From the terminal, inside the sessions where you already work.

How do you connect MyCase to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect MyCase, you add a MyCase MCP server: a small hosted service that exposes MyCase'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 MyCase account. No API keys pasted into config files.

claude mcp add --transport http mycase 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 MyCase once connected?

Full read-write MyCase access lets Claude log a time entry against the right matter, add a task or calendar event, attach a note, and update contact or matter fields once you approve. The case admin that used to mean re-keying between tabs happens inside the matter where the work already lives.

Create a time entry against a specific matter with description and duration
Add a task or deadline to a matter and assign it to a team member
Attach a note to a contact or matter to record what happened
Create a calendar event tied to a case
Update contact or matter fields after intake
Create a billable expense against a matter for your review

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 MyCase 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 MyCase API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when MyCase 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 MyCase 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 MyCase 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 MyCase 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 MyCase'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 MyCase?

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 MyCase account it signs in with. Revoking access is one click in MyCase.

More on the MyCase connector

MyCase connector for claude.ai PracticePanther + Claude Code Filevine + Claude Code Housecall Pro + 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