MCP stands for Model Context Protocol, the open standard that plugs an AI assistant into the systems your firm already runs: email, calendar, case files, CRM, billing. Most connectors are one-click setups inside Claude, no code, under 15 minutes each.
Here’s why that matters. The problem with AI at most law firms is that the AI can’t see anything.
It can’t see your email. It can’t see your calendar. It can’t see the case files sitting in Drive or the client record in your CRM. A chatbot without access to your systems is a smart intern locked in a closet. Brilliant, and useless, because every piece of context has to be copy-pasted through the door.
MCPs fix that. The spec is open and lives at modelcontextprotocol.io. Once Gmail is connected, “summarize every email from opposing counsel on the Martinez matter” is a 10-second task instead of an hour of scrolling and pasting. That single query is what converts most skeptics at my firms.
I own 10 law firms. My flagship, CPLG, handles lemon law in all 50 states with 62 staff, and MCPs are the reason our AI setup does real work instead of party tricks. This page lists the free connectors worth plugging in first.
How to connect one (no code, under 15 minutes)
In Claude, open Settings, then Connectors. You’ll see a directory of available MCPs. Click the one you want, log into that service, approve the access screen. That’s the whole setup for most of them. OAuth handles the authentication, nothing gets installed, and you can disconnect any of them with one click later.
Fifteen minutes is the ceiling, not the average. Gmail took me about four.
The free MCP list for law firms
| Connector | Best for |
|---|---|
| Gmail | Inbox triage, drafting, full matter email history |
| Google Drive | Finding and summarizing case files |
| Google Calendar | Deadline and conflict checks |
| Slack | Channel digests, catching up fast |
| Notion | Answers from your actual SOPs |
| Zapier MCP | The 8,000+ apps with no native connector |
| Clio | Matters, contacts, tasks, billing |
Start with your core three
Gmail is the highest-value connector for almost every lawyer. Triage the inbox, draft replies in your voice, find every thread touching a matter across months of mail. My intake team uses it to pull a client’s full email history before a call.
Google Drive turns “where is that repair order” into a question you ask instead of a folder you dig through. Claude can search case files by description, summarize a 40-page contract you point it at, and retrieve documents you half-remember the name of.
Google Calendar covers deadline checks and scheduling. “What’s on my calendar the week of the Rodriguez deposition, and does anything conflict with the filing deadline” is one sentence now.
Firm operations
Slack connects your internal comms. Channel digests, catching up on a thread you missed, routing an escalation to the right person. At CPLG we run 62 people through Slack, and being able to ask “what happened in intake this week” beats reading 400 messages.
Notion is where our SOPs live. Connected, it becomes a firm knowledge base Claude can actually answer from: “what’s our process when a client’s registration is expired” pulls the real procedure, not a guess.
HubSpot, or whatever CRM you run, opens up pipeline questions. How many leads came in this week, which signed, which went cold. If you’re rebuilding intake with AI, this connector is where the numbers live. If your CRM has a native MCP, connect it; if not, the bridges below cover it.
Todoist (or your task manager) means tasks get created from conversations instead of transcribed later. “Add a task for Stephanie to send the retainer” happens mid-thought.
Stripe answers money questions. Payments received this month, failed charges, revenue by week. Read-only access is enough for all of it.
The bridges: when there’s no native MCP
Zapier MCP is the workhorse. One connector, and behind it sit 8,000+ apps Zapier already talks to. If your practice management tool, phone system, or e-signature platform has no native MCP, this is usually the answer.
Pipedream (mcp.pipedream.com) is the developer-grade version of the same idea: thousands of app connections with more control over exactly what the AI can do. If you have anyone technical at your firm, or you’re the technical one, start here for the odd cases.
A tip from Fabio, my AI manager: if a system offers both a native MCP and a Zapier connection, connect both. Claude sometimes files or fetches better through one than the other, and having both costs nothing.
Specialized connectors worth knowing
Plaud (mcp.plaud.ai/mcp) pulls your AI voice recorder’s notes and transcripts straight into Claude. Record a client meeting, then ask Claude to draft the follow-up email from the actual transcript instead of your memory of it. The same logic applies to any AI notetaker that offers a connector.
Facebook Ads (mcp.facebook.com/ads) matters if your firm runs paid intake. Ad account analysis, spend by campaign, cost per lead, all queryable in plain English. We check ours daily this way.
Clio has an MCP too, and for firms running their practice on it, this is the big one: matters, contacts, calendars, and billing become things Claude can see. The full setup guide is tomorrow’s resource at /clio-mcp.
Security notes, because you’re a lawyer
Your bar’s confidentiality duties apply to an MCP the same way they apply to any vendor with access to client data. Four habits keep this clean. Connect read-only where the option exists; most query use cases never need write access. Start with non-confidential systems like Calendar and Todoist while you build trust. Read the permission screen before you click approve, because scopes vary and you should know what you granted. And check your AI provider’s data terms: paid Claude plans don’t train on your data, which is the baseline you want.
None of this is exotic. It’s the same diligence you’d run on a new document management vendor, compressed into 20 minutes of reading.
Do this today
Connect Gmail and Google Drive. Run one real query against a real matter, something you’d otherwise spend 30 minutes on. Then add one connector a week until the list above is done. Connected systems are also the foundation for AI agents that work across them without you.
If you’re earlier in your AI adoption, the roadmap puts this step in context. If you’re further along and want to build tools no connector covers, that’s Claude Code. Tomorrow: the full Clio MCP walkthrough.