mait.sh1.132.1

Private beta: features and content may change. No warranty; use at your own risk.

Install and configure mcp-registry

Add the registry to your agent, register your first tool server and make a first call through it.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
MCP Registry

Names, counts and diagnostics vary with the installed release and your fleet; use the tool definitions your client returns before a call.

Steps

Five steps from install to your first call through the registry.

MCP Registry is an MCP tool: you add one entry to your client, then register backends from inside the session. For a local stdio setup, use your normal account and approved installed backends. Remote backends need their configured connectivity and credentials; individual backend operations can require additional permissions.

  1. Capturedmcp-registry 0.8.5
    Check the version
    $ mcp-registry version
    mcp-registry 0.8.5
    Step 1 of 5

    Check that it arrived

    The MAIT image ships mcp-registry and updates it with the image. mcp-registry is a Linux program. On macOS and Windows, mcp-registry runs in the managed Linux environment that AIDC Launch provides. Run the version command.

    What you get

    The program answers with its version.

  2. mcpServers entry
    {
  "mcpServers": {
    "tooling": {
      "command": "mcp-registry",
      "args": ["serve"]
    }
  }
}
    Step 2 of 5

    Connect it to your agent

    Any client that accepts an mcpServers launch entry uses this shape. Place it where your client keeps server configuration and restart the client.

    What you get

    A client that starts the registry on its own. With no backends registered it lists only the 16 mcp_registry_* tools.

  3. Capturedmcp-registry 0.8.5 · mcp-docs 2026.10.3
    YouAdd the documentation server as a backend called docs.
    Tool callmcp_registry_add { "name": "docs", "transport": "stdio", "command": "/usr/local/bin/mcp-docs", "args": ["serve"] }
    What happens{ "message": "server 'docs' added and started" }
    AgentThe docs backend is added and started.
    Step 3 of 5

    Add a backend

    Ask your agent to add one. It calls mcp_registry_add. The name becomes the prefix of every tool the backend exposes.

    What you get

    A running backend. Replace the path with your installed executable.

  4. Capturedmcp-registry 0.8.5
    YouWhat is registered?
    Tool callmcp_registry_list {}
    What happenscount 1: docs, state Connected, transport stdio, 3 tools, preload null, watch true.
    AgentOne backend, docs, is connected and exposes three tools.
    Step 4 of 5

    List the fleet

    mcp_registry_list shows each backend, its state and its tool count.

    A state of Error or NeedsAuth comes with a message; see Troubleshooting.

    What you get

    The state of every backend in one answer.

  5. Capturedmcp-registry 0.8.5 · mcp-docs 2026.10.3
    YouList the pages for MCP Git.
    Tool calldocs__docs_list { "prefix": "user/modules/mcp-git" }
    What happenscount 8 and eight paths under user/modules/mcp-git, the same as a direct call to MCP Docs.
    AgentThere are eight pages for MCP Git, including the commit and push tutorial.
    Step 5 of 5

    Call a tool by its prefixed name

    Use the <backend>__<tool> name. The registry removes the prefix and the backend receives its own tool name.

    What you get

    A tool call that went through the registry to the backend and back.

Result

One client entry that reaches every backend.

One client entry reaches a registered backend, and you can see its state and call its tools by prefixed name. Register more backends the same way, or keep them in a file you can review.

Next

Where to go next.