Connect PracticePanther to Claude Code

Have Claude open matters, log time, and create tasks in PracticePanther. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect PracticePanther to Claude Code?

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

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

Full read-write PracticePanther access lets Claude open a new matter, link the right account, log a time entry against it, create follow-up tasks, and record an expense for the matter. The intake and billing prep that used to mean retyping between tabs happens where the matter already lives.

Open a new matter and link the relevant account
Log a time entry against a matter with description, rate, and duration
Create and assign tasks tied to a matter or deadline
Record an expense against a matter for billing prep
Add or update an account (contact) record from a conversation
Search open matters matching a query and propose batched updates

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

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

More on the PracticePanther connector

PracticePanther connector for claude.ai MyCase + 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