One connection to every tool server you use.
Most agents need several tool servers: one for your code history, one for your cluster, one for a browser. Without help, each one is another entry to set up in every app you use. MCP Registry is the single front door. Your agent connects to it once, and the registry connects to the rest and shows all their tools in one list.
Each tool is labelled with the server it belongs to, so you can distinguish similarly named tools before choosing one. And because the agent can add, check and restart servers itself, you stay in the conversation instead of editing settings files.
What you gain over one entry per server.
Every extra tool server means another entry in every app and a longer list for the agent to read. When one breaks or needs a login, you usually find out when a request fails.
One entry for everything
Adding a server is one request, not an edit in every app
- Typical alternative
- A separate entry for each server, in every app
- Here
- Your apps know only the registry; new servers are added by asking the agent
Distinct qualified names
The returned name identifies the intended backend
- Typical alternative
- Similar tools from different servers get confused
- Here
- Every tool carries the name of its server, and the registry passes the call to the right one
A short list to read
The agent carries the tools it uses, not the whole catalog
- Typical alternative
- Every tool of every server loaded up front
- Here
- Rarely used tools stay out of sight until the agent looks for one and switches it on for the current conversation
The whole fleet at a glance
One question tells you which server needs attention
- Typical alternative
- Finding out a server is down when a request fails
- Here
- The agent can list every server with its health and show recent problems
Logins that wait for you
A server that needs you is told apart from a broken one
- Typical alternative
- A refused connection retried again and again
- Here
- A recognized authorization refusal pauses retries until credentials or configuration are repaired
One file you can review
A new machine gets the same servers from one file
- Typical alternative
- Settings copied by hand between apps
- Here
- The whole set of servers can be saved to one file and loaded on another machine or app
Ready in the image, one entry to add.
The registry comes with the MAIT image and updates with it (mait-image). You add one entry to your agent's app, then configure and verify the backends needed for your task. Until you add servers, the agent sees only the registry's own management tools.
You can keep the registry private to one app or share it between apps on the same machine. Admit only clients you trust with full fleet administration, and keep the registry private.
Where it sits in the MAIT toolkit.
The registry sits between your agent and the tool servers it uses.
Where to read on.
- Get started, Use cases and Tools