You can point your AI assistant at Quilia and have it work with your firm's data the same way you would. Send a message to a client. Pull up the latest case notes. Schedule an appointment. Ask "what does my week look like" and get an answer that's actually about your week.
This is not a copy-paste workflow. There is no API key to manage. You sign in once with the same Quilia account you already use, and the assistant is connected. Your firm administrator can revoke access at any time.
Connect in one click
Pick your assistant. The buttons below open the right place in each app, with Quilia's address pre-filled where the assistant supports it.
Heads up: your browser must be signed in to the same Anthropic account as Claude Desktop, or you’ll see “Account mismatch” after Connect.
claude mcp add --transport http quilia https://mcp.quilia.dev/Every option signs you in with your existing Quilia account. No API keys, no copy-paste credentials.
If a button does not work in your browser, or your assistant is not on this list, the step-by-step instructions below cover the same setup manually. The Quilia address is https://mcp.quilia.dev/ for any assistant that asks.
Before connecting an assistant, please review Section 8 of our Terms of Service. It covers your firm's responsibilities for data sent to third-party AI providers, and what is and is not Quilia's responsibility once data leaves our systems. Check with your firm administrator that the assistant you choose is approved for use with privileged client data.
How it works
Quilia speaks a protocol called MCP (Model Context Protocol). Any AI assistant that supports MCP can connect to Quilia by pointing at a single address and going through a sign-in screen.
When you sign in, the assistant gets a scoped credential that is only good for your firm and only good for the things your role lets you do at Quilia. An attorney sees what an attorney sees in the portal. A staff member sees what a staff member sees. Nothing is broader than what you can already do yourself.
The address your assistant connects to is https://mcp.quilia.dev/.
Before you start
You need three things.
- An active Quilia account with your firm.
- An AI assistant that supports MCP. The list below covers the ones we have tested.
- About 30 seconds.
You do not need a developer. You do not need an API key. You do not need to copy anything between windows.
Claude Desktop
Open Claude Desktop and go to Settings, then Connectors. Add a new connector. The URL is https://mcp.quilia.dev/. Save.
Claude Desktop will open a browser tab to Quilia. Sign in with your Quilia account if you are not already signed in, then approve the connection. The tab will close on its own. Your assistant is now connected.
To test it, ask Claude something like: "Look up my cases" or "Send a reminder to my next client about their treatment update." If everything is connected, the assistant will read or write through Quilia and tell you what it did.
Cursor
In Cursor, open settings and find the MCP section. Add a new MCP server. Set the URL to https://mcp.quilia.dev/. Save and let Cursor open the sign-in tab.
Same sign-in flow. Same scope. The tools become available to chat right away.
Claude Code
Run this in your terminal:
claude mcp add --transport http quilia https://mcp.quilia.dev/
Claude Code will print a one-time URL. Open it in a browser, sign in to Quilia, approve the connection, and you are done. The next time you start a Claude Code session, the Quilia tools are available.
ChatGPT
ChatGPT support for third-party MCP connectors is rolling out gradually inside the consumer apps and is already available in some enterprise configurations. If your ChatGPT account exposes an MCP connector setting, point it at https://mcp.quilia.dev/. If you do not see the option yet, check back in a few weeks.
Try these first
Once you are connected, here are a few prompts that confirm everything is working and show you the shape of what the assistant can do. The expected result is listed next to each one.
- "What cases do I have open right now?" The assistant lists your firm's open cases, scoped to what you can already see in the portal.
- "Find the client Jane Doe and show me their case." The assistant looks the client up by name and pulls up the matching case and contact details.
- "Send a message to my next client reminding them to bring their insurance card to their appointment." The assistant drafts and sends the message to the client, attributed to you, the same as if you sent it from the portal.
- "What does my week look like?" The assistant reads your upcoming appointments and summarizes the days ahead.
If the assistant reads or sends something through Quilia and tells you what it did, you are connected correctly. If it says it cannot do something, that usually means the action needs a role you do not have, which is covered in the troubleshooting section below.
What your assistant can do today
Once connected, your assistant can do all of the following on your behalf.
- Identify you. The assistant knows your name, your role, and your firm. It does not need to ask you who you are.
- Find a client or staff member by name or email.
- Look up cases, contacts, and appointments.
- Send a message to a client or to a case thread, attributed to you.
- Create a new case, optionally with a new client.
- Send a request template to a client (intake form, medical records release, and so on).
- Search and read Quilia's help center articles to answer questions about how the product works.
The assistant only sees what you would see in the portal. If you cannot see a case, neither can the assistant. Cross-firm visibility is reserved for users who already have it via the portal.
How to revoke access
If you want to disconnect your assistant from Quilia, you can do it from inside the assistant or from inside Quilia.
From inside the assistant (Claude Desktop, Cursor, Claude Code, ChatGPT), open the same connector settings panel where you added Quilia and remove the connection.
From inside Quilia, go to Settings and then Connected Apps. You will see every assistant that is currently connected to your account, with a date and a one-click Revoke button. Revoking on the Quilia side takes effect immediately and works even if the assistant is offline or you no longer have access to it.
Your firm administrator can also revoke any connection from any user in the firm at any time.
Common issues
My assistant says it can connect but the sign-in tab is blank. Almost always a popup blocker or a browser that intercepted the redirect. Re-try with the popup permission enabled for mcp.quilia.dev.
I signed in but the assistant says my session expired right after. Your assistant got an old session that was issued to a different firm. Disconnect and reconnect from the assistant's settings. The new session will be issued for whichever firm you are currently active in.
I changed firms and the assistant is still pulling data from my old firm. Same fix. Disconnect and reconnect. The connection is bound to whichever firm you were on at the moment you signed in.
The assistant offered to do something and it failed with a permission error. The action requires a role you do not have at this firm. Ask your firm administrator to grant the role, or escalate the action to someone who has it.
I do not see Quilia in my assistant's connector list at all. Your assistant version does not support MCP yet. Update to the latest version. If the option still is not there, the assistant does not yet support MCP and we cannot work around that from our side.
Privacy and security
Quilia uses the same sign-in flow your portal uses. No long-lived API key sits on your laptop. No browser extension is involved. The credential the assistant gets is short-lived, scoped to your firm, and revocable from either side. Every action the assistant takes is logged against your user, the same as an action you took yourself.
If your firm has any compliance requirement that needs the connection turned off across the firm, your administrator can disable AI assistant access in firm settings.
For the full detail on how Quilia collects, uses, and protects your data, see our Privacy Policy. For your firm's responsibilities when sending privileged client data to a third-party AI provider, see Section 8 of our Terms of Service.
Get help
Stuck on a step? Email support@quilia.com with a quick description of what assistant you are using and where you got stuck. We will get you connected.