Legal · MCP connections through the gateway

An AI package for the whole legal team

Document management, contracts and legal sources are connected once in the gateway. After that lawyers ask in their own words, every answer shows the source it rests on, and the legal judgement stays with a human.

Your toolsThe Walma gatewayThe modelsYour own agents
149MCP servers we have surveyed
86official, straight from the vendor
19ready to connect for legal
1login for the team
Why Walma

Why go through Walma instead of straight to the model?

One account is fine for one person. The difference shows up when a whole team uses AI, and when somebody asks what it cost or where the data went.

Everyone on their own

Everyone signs up separately. Nobody knows what it costs, who has access, or what has been shared.

With Walma

One way in to every model. One login, one invoice, and you can see what is actually happening.

01 · Freedom

Do not marry one model

Claude today, something else next year. With Walma you use all of them and switch when it suits you, without redoing the work.

  • The same connections whichever model you run
  • Switch model without rebuilding anything
  • Run two models on the same task and compare
02 · Ready

The connections are already built

We have done the groundwork: ready-made connections to the tools you already use, with proven skills and instructions, so the team actually gets going instead of just trying it out.

  • Ready connections to the tools you already use
  • Skills and instructions other teams already run in earnest
  • Nothing for the team to install
03 · Control

You see exactly what the AI does

If you want visibility, you get it: everything the agent does is visible, you get feedback on how the work could be better, and you can put a stop to things it should not do.

  • Every call logged, with person, tool and timestamp
  • Feedback on how the team could use it better
  • Guardrails for what the agent must not touch
How the AI Hub works

Three steps, and then it is running

Walma AI Hub is a layer between your tools and the models. Here is what that means in practice.

01Step 1

Connections are approved once, centrally

IT approves an MCP server once. After that the tool appears for the people who should have it, with the right permissions. Nobody on the team touches an API key.

  • One allowlist instead of config files on every laptop
  • Read or write permissions per role, set in the gateway
  • Revoke access in one place when someone leaves
02Step 2

Every model behind the same key

Claude, GPT, Gemini and the open models all reach the same connections. You pick the model per task instead of locking yourself in, and if you switch next year the tools come along.

  • One login for the user, whichever model runs
  • Budgets and spend caps per team, not per person
  • One log for model calls and tool calls alike
03Step 3

Your own agents on top, built by us

When the off-the-shelf tools run out, we build. RAG over your own material, bespoke agent flows, and narrow MCP servers for systems the vendor has not covered, all running inside the same gateway and the same log.

  • RAG over your documents, contracts and product data
  • Agent flows that follow your process, not a template
  • Custom MCP servers for systems the vendor has not covered
Your material
Documents and contracts
Product and customer data
Internal systems
The agent we build
Walma agentRAG · tools · your process
Answers in Claude, Teams or Slack, where people already work
Connections

What the legal team gets to connect

Document and contract systems are furthest ahead: iManage, NetDocuments, Ironclad and Sweden's Scrive have their own servers. For the Nordic legal databases we build the connection.

Ready to connect

The vendor's own server. Switched on and running the same day.

Needs review first

Community-built. We review the tool descriptions and pin the version before approving.

In progress: we build the connection

These we build ourselves, as narrow read-only servers in your tenant. Tell us which you need first.

See the full MCP directory →

In practice

What you actually ask it

Questions lawyers already ask, minus hunting for the right folder first.

  • → Which of our supplier contracts expire or renew automatically in the next six months?
  • → Compare the limitation of liability in this draft with our standard template.
  • → What does the GDPR say about retention periods for this kind of data? Cite the article.
  • → Have we signed a similar NDA with another client before, and what was negotiated away?
  • → Which contracts are still waiting for signature in Scrive?
  • → Summarise the changes to this act since last year, with a link to the source.
How it fits together

It all runs in the EU, with a log

The gateway runs in your own Azure tenant in an EU region. Every call is logged with user, tool and arguments. That is the answer when your data protection officer asks where the data goes.

Security

Built for European requirements from day one. Details, subprocessors and policies live in our Trust Center.

Open the Trust Center
  • GDPR
  • EU data residency
  • Encrypted at rest & in transit
  • No training on your data
  • Tenant isolation
  • SSO & SCIM
  • SOC 2 Type IIin progress
  • ISO 27001in progress
  • Custom user roles
FAQ

What lawyers ask first

Can we use AI on privileged or confidential documents?+

That is your call, but the technology should not be what stops it. The gateway runs in your own Azure tenant in an EU region, the models are reached through EU data zones and the data is not used for training. Permissions follow the role, and iManage keeps its own permissions and ethical walls when the agent reads from it. Every call is logged, so you can show who asked about which matter.

Does the AI make up case law?+

A language model answering from memory can, which is why the connections exist. When the agent pulls from Westlaw through CoCounsel, from statute text or from EUR-Lex, the answer rests on the actual source and shows where it is, so the lawyer can check. We do not promise a model is never wrong. The setup makes it easy to see when it is, and a lawyer always makes the call.

Can we connect Karnov and JUNO?+

Karnov and JUNO have AI features of their own inside their services, and we build the connection to the gateway. In the meantime the team reaches Swedish statute text through the Riksdag's open data and EU law through EUR-Lex, both via community servers that we review before they are approved.

Which contract and e-signing tools can we connect?+

Scrive has its own server with BankID signing, DocuSign has its in beta, and Ironclad offers read-only contract search with its own EU endpoint. Juro has its own server too. Oneflow and Dropbox Sign are reached through community servers we review, and for Penneo and Assently we build the connection.

Is this the same thing as Legora or Harvey?+

No. Legora and Harvey are AI products built for lawyers. Walma is the platform that gives the whole company the models and the connections, with shared governance and a log, and the legal team is one department on it. If you already have a legal AI tool it can stay, and the gateway governs the rest of the organisation's AI use, including the contracts and documents the lawyers themselves have to keep track of.

Connections

See it on your own contracts

Twenty minutes with an engineer. We connect your document or contract system, read-only, and show what the lawyers can ask the next day.