Connect Filevine to Claude Code

Let Claude update matters and post case notes in Filevine. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Filevine to Claude Code?

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

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

Full read-write Filevine access lets Claude update project fields, post notes to the activity feed, create and assign tasks, add calendar deadlines, and draft documents from collected data. The status updates and intake work that used to mean tabbing between screens happen where the matter already lives.

Update project or matter fields after a status change
Post a note or activity-feed entry summarizing a call or update
Create and assign tasks to team members on a matter
Add a deadline or hearing date to a project's calendar
Draft a document from collected project data for review
Find every matter 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 Filevine 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 Filevine API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Filevine 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 Filevine 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 Filevine 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 Filevine 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 Filevine'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 Filevine?

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

More on the Filevine connector

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