Does Quillio work with MCP (Model Context Protocol)?
Yes. Quillio provides an MCP (Model Context Protocol) server that exposes selected matter operations to MCP-aware clients like Claude Desktop, cursor-based IDEs, or custom agents. Access is scoped to the authenticated user's matters and follows the same permission model as the Quillio UI.
What MCP exposes
The Quillio MCP server exposes matter search, document retrieval, prompt execution, and chronology build operations. Write operations (create, edit, delete) require specific scoped tokens and are disabled by default. This keeps MCP integrations low-risk by default.
Authentication
MCP clients authenticate with a Quillio personal access token generated in your profile. The token inherits your matter permissions — you cannot access matters through MCP that you cannot access in the UI.
Use cases
Common uses include summarising matter state from Claude Desktop during client calls, using IDE-based AI agents to draft documents with matter context, and building custom internal agents that use Quillio matter data as grounding.
Common issues
- MCP tokens should be treated as confidential — store in secret managers, not in config files
- Firm admin can disable MCP per-user for high-risk matters
- MCP protocol evolves — we version the server and maintain backward compatibility
Try Quillio on a real matter.
The fastest way to know if Quillio fits your practice is to use it on your own work. The free trial requires no credit card and no sales call.
Start your free trial