Matter status without a scavenger hunt
Ask what happened on a matter this week. The brain reads the case system, notes, tasks, and the last contact, and answers with sources.
FirmOps MCP
The FirmOps MCP is a remote server at https://mcp.firmops.io/mcp. Staff ask from the real case file. The brain drafts. A person at the firm releases. Sign in with Google or a one-time email code.
Server URL
https://mcp.firmops.io/mcpBy Jon Mahler · non-attorney founder and firm manager of Conduit Law, LLC (Colorado) · Updated November 16, 2026
What it does
MCP is a connection protocol. FirmOps uses it so a firm brain can call scoped tools on Clio, Filevine, or SmartAdvocate, mail, and files, instead of pasting secrets into a chat window. Least privilege, logging, and approvals are how FirmOps operates that connection. The protocol does not.
Ask what happened on a matter this week. The brain reads the case system, notes, tasks, and the last contact, and answers with sources.
Status letters, provider follow-ups, and handoff notes start from the record. A person edits and sends.
Case system, Gmail or Microsoft 365, documents, billing, and read-only call history. Staff stay in Claude or ChatGPT. FirmOps runs the plug.
Install
The address is the same for every firm. Go to the FirmOps app, sign in with Google or a one-time email code, and name the firm. Connect the case system. Then add this URL to the AI the team already uses.
Server URL
https://mcp.firmops.io/mcpWorks on claude.ai, Cowork, and Claude Desktop for Free, Pro, Max, Team, and Enterprise. Free is limited to one custom connector. On Team or Enterprise, an owner adds it once; each person then connects with their own sign-in.
Custom MCP servers are added as a plugin. Full MCP is for ChatGPT Business and Enterprise/Edu on the web. Pro can connect with read and fetch tools. There is no official one-click deep link; copy the URL.
Cursor talks to remote MCP servers over streamable HTTP and runs OAuth in the app. The Add to Cursor link writes the server into your MCP settings after you confirm.
Remote connectors on Claude Desktop use your Claude account, not a local JSON file. Anthropic’s cloud reaches mcp.firmops.io. Local claude_desktop_config.json is only for servers that run on the computer.
Writes are off during the trial. Once FirmOps onboards your firm, these become available. Each one shows a preview first, and nothing changes in the case system until the person confirms.
Sample prompts use fictional matters (Lopez, matter 01234), the same pattern as firmops-demo-firm test data. Do not paste a real client file into a chat window to try this.
FAQ
It is the public address of the firm brain: a remote Model Context Protocol server at mcp.firmops.io/mcp. Staff add it once to Claude, ChatGPT, Cursor, or Claude Desktop, sign in, and ask from the real file instead of pasting it. MCP is the plug. The Managed Firm Brain is the offer FirmOps builds and runs.
No. The case system stays the system of record. The MCP lets Claude or ChatGPT read it and stage updates for a person to approve.
Google or a one-time email code, using the same address your firm added on the Team page. Microsoft sign-in is not offered on this public connector. The sign-in decides which firm you reach. You never type a firm name into the AI.
No. The URL is public so a firm can add the connector. Using it requires a FirmOps account. Maintenance is on Pricing. Writes stay off until FirmOps onboards the firm.
No. The protocol does not enforce consent. Security comes from per-person sign-in, a short tool menu, an audit log, and a person at the firm on every send. See Security.
No. Drafts wait for a person. Live client calls stay with people. CallRail tools are read-only call history. A wide-open connector that sends unsupervised is a design failure, not a feature.
You signed in with an email the firm has not added. Ask the owner to add it on the Team page, or sign in with your firm address.
Help: hello@firmops.io. See also Security, Privacy, Terms, and Chrome extension privacy.
Notes
Connector menus move. Send your work email and we will tell you when the FirmOps MCP steps change. Same list as the rest of firmops.io. No new form.
Keep reading
Why the file belongs in the seat staff already use.
The plug. Not a product SKU.
FirmOps builds the brain and runs it.
Plans, connectors, and human review.
The same question for ChatGPT.
What stays in the firm, and what we do not claim.
Monthly maintenance of the firm brain.
Next step
In a 30-minute live demo we run a firm brain against one real job, map your stack, and confirm your systems have the APIs to connect.