mait.sh1.142.0

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

MCP AIDC

Lets your AI agent see which tool versions a project uses, set up the ones it needs, switch versions, and upgrade or clean up old ones, with an upgrade preview and explicit confirmation for removal.

Start here: what it does, why use it, and how it fits.

Beta
What it does

Your agent looks after the project's tools for you.

MCP AIDC lets your agent look after the tools a project depends on, such as its programming languages and command-line helpers. It can see which versions are installed and which one the project uses, set up everything a fresh project needs, switch a project to another version, and tidy up versions you no longer want.

It works through AIDC, the MAIT tool manager, so your agent sees the same answers you would. Ask your agent to request an upgrade preview first, show you the intended version and obtain your approval before applying it. Removal requires a confirmed request; review the exact target and approve it before asking your agent to send that request.

Your agentMCP AIDCVerifyrequiredtools and usable versionsYou1asks2set up andverify3approveconfirmed changes through your agentYour agentMCP AIDCVerify required tools andusable versionsYou1asks2set up andverify3approveconfirmed changes through your agent
  1. Step 1: Your agent asks MCP AIDC.
  2. Step 2: MCP AIDC set up and verify Verify required tools and usable versions.
  3. Step 3: You approve confirmed changes through your agent Your agent.
Why use it

What you gain over installing tools by hand.

A project needs the right versions of its tools, and the wrong one fails in confusing ways. Use discovery to establish the project's declared versions and installed tools, then verify the actual version in the session that will build or test. A declaration alone does not establish that session's effective selection.

Reliability

The agent knows the real setup

Declared, installed and actually used versions can be checked separately

Typical alternative
It runs a tool and hopes the right version answers
Here
The agent checks installed tools, the project's declared versions and setup findings, then verifies actual use in the intended session
Speed

A fresh project set up in one request

A freshly copied project gets its tools from one request

Typical alternative
You install each needed tool by hand
Here
The agent reads the tools the project lists and installs them together
Usability

Different versions for different projects

Projects keep their own versions without clashing

Typical alternative
One global version for every project
Here
The agent picks a version for one project, for your account, or for a single working session
Reliability

Upgrades are shown first

You see the exact version before anything is replaced

Typical alternative
An upgrade runs the moment it is requested
Here
Ask the agent for a preview and review its exact target before approving an apply request; retain an available prior version when rollback matters
Reliability

Removal needs your yes

You can review the intended removal before your agent sends a confirmed request

Typical alternative
An uninstall removes versions at once
Here
Review the exact uninstall target before confirming; an unconfirmed uninstall returns a reminder rather than a computed removal list
Tokens

Short, bounded answers

The agent reads a brief report, not a full log

Typical alternative
A long install log fills the conversation
Here
The agent gets a short report of each step, with a note when it was shortened
Out of the box

Preinstalled in the image, one entry to connect.

The server and AIDC both come preinstalled in the MAIT image (mait-image), and the image keeps them up to date. The image does not connect the server to your agent for you, so you add one entry to your agent client, or connect it through MCP Registry so a single entry reaches all your tool servers. Get started shows how.

Runs on Linux (amd64, arm64). On macOS and Windows, MCP AIDC runs in the managed Linux environment that AIDC Launch provides. Tool operations need access to the configured services and download sources.

Where it fits

Where it sits in the MAIT toolkit.

Installed bymait-image ships both the server and AIDC
Delegates toAIDC, which installs and selects the tool versions
Reached throughMCP Registry, so one client entry reaches it
Used withMCP AIDE, which relies on the tools AIDC installs
Learn more

Where to read on.