This is a bigger update than usual, so it is worth going through properly. Four things changed: ModulawAI can now be driven by other AI assistants, there is a REST API for building your own integrations, the app has moved to a new address, and there is a full help centre where before there was very little.
Connect an AI assistant to your workspace
The headline change. ModulawAI now runs a Model Context Protocol server, which is the emerging standard for letting an AI assistant work with an outside system. In practice that means you can point Claude, or any other MCP-capable client, at your ModulawAI workspace and it will work with your real matters instead of guessing.
The difference is worth being concrete about. Without this, asking an assistant about a case means pasting context in by hand and hoping you included the right bits. With it, the assistant can look the matter up itself.
What it can reach
Twelve areas of your workspace are exposed:
- Cases and tasks, for looking up matters and the work outstanding on them
- Clients and intake, covering your roster and incoming enquiries
- Documents and notes, so an assistant can read what is on a file
- Calendar, for court dates and deadlines
- Financials, covering invoicing, expenses and time
- Forms and processes, for the structured work your firm runs on
- Workspace administration
- Legal research, which reaches the same case law corpus the in-app assistant uses
That last one is the one people tend to underestimate. It means an assistant working in your own tooling can search Nigerian case law directly, rather than falling back on whatever it happens to remember.
How the security works
Connecting an outside tool to a system holding privileged client material deserves scrutiny, so here is exactly how it is constrained.
- Standard OAuth, not a shared secret. Connections use OAuth 2.1. You approve a connection through a normal consent screen, and no credential is ever pasted into a third-party tool.
- Bound to one workspace. A token is issued against the workspace you approved it for and cannot reach into another.
- Read by default, write only if you say so. Write access is granted per credential, and you choose whether to grant it at all.
- Destructive actions are confirmed. Anything that deletes or irreversibly changes data requires an explicit confirmation rather than proceeding silently.
- Revocation actually revokes. Every connected app and agent is listed in your profile. Disconnecting one invalidates its access immediately.
Command-line clients that cannot open a browser are supported too, through the device authorization flow, so you get a short code to approve rather than being locked out.
A REST API for your own systems
If your firm runs its own software, or you want to automate something specific, there is now a REST API rather than an assistant sitting in the middle.
Create a key from Profile, then API access. Each key is:
- Scoped. Grant read, or read and write, per key. A reporting script never needs write access, so do not give it any.
- Optionally pinned to one workspace. Useful if you run several and want an integration confined to one.
- Rate limited individually. Limits apply per key, so a runaway script cannot degrade everyone else’s access.
- Independently revocable. Kill one key without disturbing the others.
One thing to know before you plan around it: programmatic access requires an active subscription and is not available during a trial. If you are evaluating ModulawAI and want to test an integration, talk to us and we will sort something out.
The API and the MCP connector share the same permission model underneath, so a scope means the same thing in both. There is no second set of rules to learn.
And ModulawAI can connect out to other tools too
The connector works in both directions, which is easy to miss. As well as letting an outside assistant into your workspace, ModulawAI can now connect out to other MCP servers and use their tools inside your chat.
Open the + button in the chat composer and you will find connections there, alongside Zoho, Google Calendar and your cloud storage. Add an MCP server by URL and its tools become available to the assistant while you work.
In practice that means if a service your firm relies on exposes an MCP server, whether that is a research provider, an internal system or something you have built yourself, the assistant can use it without us having to build a bespoke integration first. Both the modern streamable HTTP transport and the older SSE transport are supported, and credentials are encrypted at rest.
More models to choose from
Separately, the model picker has grown. Alongside the existing options you can now select:
- GLM 5.2, a frontier open-weight model with strong reasoning and a very long context window, useful when you are working across a lot of material at once
- Kimi K2.6, reliable at tool use and structured output, with strong reasoning. It takes slightly longer to produce its first words because it thinks before it answers
- MiniMax M3, frontier reasoning with a long context and native image understanding, so it is the one to reach for with scanned exhibits or photographed documents
These three sit on the Professional plan and above, and consume credits at twice the standard rate. That is a reflection of what they cost to run rather than a judgement about when you should use them, but it is worth knowing before you make one your default. The full picture, including which model suits which task, is in Choosing an AI Model and What Credits Cost.
The app has moved to app.modulaw.ai
ModulawAI now lives at app.modulaw.ai. The main modulaw.ai address becomes our public site, covering the product, pricing and the help centre.
Existing bookmarks continue to work and will send you to the right place, so nothing breaks if you do nothing. Still worth updating them when you get a moment. Your account, your workspaces and your data are entirely unaffected. Only the address changed.
A help centre worth reading
We have published a proper help centre, organised into collections rather than a single undifferentiated list. It currently covers:
- Getting started, including creating an account, signing in and a tour of the interface
- Legal Assistant, covering your first question, uploading documents, drafting, voice mode, choosing a model, and the limits of what the assistant can and cannot do
- Case and matter management, covering creating cases, notes, tasks and deadlines
- Workflows and automation, including what workflows can and cannot do
- Team chat and collaboration, covering channels, direct messages, and bringing the assistant into a channel
- Documents and connecting your email
Two of these are worth singling out. What the Assistant Can and Can’t Do is deliberately blunt about the limits, including what it will not do and where you must check its work. Understanding AI Answers and Citations explains how to read a citation, what the verification badge actually means, and why it means something slightly different depending on the jurisdiction. If you rely on this tool for research, read that one.
More guides are on the way, including the client portal and the CRM.
A rebuilt foundation
Less visible, but the reason several of the above were possible. We have moved ModulawAI’s infrastructure onto AWS: the servers running the application, the caching layer, document storage, document text recognition, and the AI models handling research and drafting.
You should not have noticed this happening, which was the goal. What you should notice is that responses come back faster and the platform holds up better when a lot of people are using it at once.
Getting started
If you want to try the assistant connection or the API, go to Profile, then API access in app.modulaw.ai. The connect instructions for MCP clients are on that page, along with a link to the developer documentation.
If you build something interesting with it, we would genuinely like to hear about it.