One agent hands work to other agents.
MCP AIC lets one agent hand work to others. Your agent can start a helper session in a project folder, give it a task, follow what it does, stop it if it goes wrong, and close it when the job is done. The helpers are the agent programs you already have installed and signed in on the same machine: Claude, Codex, Cursor or Kimi.
By default MCP AIC requests removal or denial of the helper program’s built-in tools. Ask your agent for the capabilities report of the installed provider release, and give the helper only the registered tools needed for its task. Allowed folders and restricted-tool settings do not replace a suitable execution environment.
What you gain over doing it by hand.
Without it, a second agent means a second terminal, a copied prompt and a screen you have to read back yourself.
Hand a task to another agent
Delegating takes a moment, with no window switching
- Typical alternative
- You open another terminal and paste the task
- Here
- Your agent starts a helper and gives it the task from the conversation you are already in
Follow progress without the noise
Your agent reads short messages, not pages of output
- Typical alternative
- The helper's whole output scrolls past
- Here
- Your agent reads recorded messages and tool-status summaries without receiving raw tool-result bodies
Limit what the helper can touch
You choose the registered tools and project, then verify provider support and access before delegation
- Typical alternative
- The helper inherits a full shell
- Here
- The default requests restricted built-in tools and checks the chosen project folder
Several helpers at once
You run, check and stop helpers from one conversation
- Typical alternative
- One terminal per agent
- Here
- Your agent runs several helper sessions side by side, within limits you can see (by default 16 per server and four per client), and lists and stops them from one place
Stop a runaway job
You can request cancellation and inspect the stored partial result; earlier actions are not undone
- Typical alternative
- Closing a terminal and hoping
- Here
- Your agent requests a stop and follows the final state while retaining the available partial record
Learn the tools on the spot
The workflow is available before delegation
- Typical alternative
- Reading a README first
- Here
- A built-in guide tells your agent the workflow, the limits and the warnings about stored data
Included in the image, with prerequisites to prepare.
MCP AIC comes in the MAIT image from release 1.8.0 and updates with it (mait-image). Runs on Linux (amd64, arm64). On macOS and Windows, MCP AIC runs in the managed Linux environment that AIDC Launch provides. Your agent client starts it for you once you add it.
Prepare the allowed project folders and an installed, signed-in helper program, for example one that AIDC installed. Also prepare the running MCP Registry endpoint that supplies its tools. Ask the operator to verify the execution mode and access before the first task; a bundled executable alone does not establish those prerequisites. Get started shows the exact settings.
MCP AIC does not start that registry for helpers: you start it yourself and tell MCP AIC where to find it.