mait.sh1.132.1

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

Install and configure mcp-aic

Check MCP AIC, name the folders sessions may use, connect it to your agent, and have the agent open one session, send it a task and read the answer.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
Steps

Five steps from install to your first delegated task.

MCP AIC is an MCP tool: you check it is installed, tell it which folders sessions may work in, point your agent at it, and then ask in plain language. A local client can connect without exposing a network service. The provider still needs its normal account access and connectivity, and nested mode needs an operator-prepared Docker environment.

  1. Capturedmcp-aic 0.2.0
    Check the version
    $ mcp-aic version
    mcp-aic 0.2.0
    Step 1 of 5

    Check that it arrived

    The MAIT image ships mcp-aic from release 1.8.0 and updates it with the image. Runs on Linux (amd64, arm64). On macOS and Windows, MCP AIC runs in the managed Linux environment that AIDC Launch provides. Check what you have.

    What you get

    The program answers with its version.

  2. Step 2 of 5

    Make sure a provider program is installed and signed in

    A session runs one provider's own command-line program on the same machine: Claude, Codex, Cursor or Kimi. Install the one you want (for example with aidc) and sign in to it as you normally would. Prepare account access before opening the session; MCP AIC does not perform an interactive sign-in for you.

    What you get

    A provider program that works when you start it by hand.

  3. mcpServers entry (illustrative paths)
    {
  "mcpServers": {
    "agents": {
      "command": "/usr/local/bin/mcp-aic",
      "args": ["serve"],
      "env": {
        "MCP_AIC_WORKSPACE_ROOTS": "/workspace/projects",
        "MCP_STUB_SERVER": "/path/to/your/registry.sock"
      }
    }
  }
}
    Step 3 of 5

    Connect it to your agent

    Any client that accepts an mcpServers launch entry uses this shape. MCP_AIC_WORKSPACE_ROOTS is required: a colon-separated list of absolute folders, and a session can open only inside one of them; that limit does not confine every possible provider action. MCP_STUB_SERVER is the socket or address of a running MCP Registry; it decides which tools a session can use (to give sessions Docker tools, add the docker backend to that registry).

    Start the registry and add the backends the task needs (see MCP Registry get started), and check the installed provider’s support for the default restricted-tool setting. If you reach your tools through the registry, mcp-aic can be one of its backends too.

    What you get

    A client that starts the server, and a server that knows where sessions may work.

  4. Capturedmcp-aic 0.2.0
    aic_capabilities, server block only
    {"limits":{"idle_timeout_secs":{"default":1800,"max":1800,"min":60},
 "max_sessions":16,"max_sessions_per_client":4},
 "modes":{"host":{"available":true,"isolation":"container"},
 "nested":{"available":false,"image":"mcp-aic-nested:1","reason":"the image is not present locally; ..."}}}
    Step 4 of 5

    Ask what the server offers

    Ask your agent to call aic_capabilities. It lists the providers it found, what each supports, and a server block with the modes and limits. This capture ran in a container with no provider installed, so every provider reads as not installed.

    What you get

    Reported provider capabilities and server limits to check before opening; they do not establish account or task readiness. On a machine that is not a container, host reports not available until the operator accepts full host access (see Safety and limits).

  5. Illustrative conversation
    YouAsk a Claude session in /workspace/projects/app to list the open TODO comments, then tell me what it found.
    Tool callaic_session_open { "provider": "claude", "workspace": "/workspace/projects/app" }
    What happensA session opens and returns its session_id and state idle.
    Tool callaic_message_send { "session_id": "<id>", "text": "List the TODO comments in this project.", "await_ms": 5000 }
    What happensThe turn starts. If it ends within five seconds the answer comes back at once; otherwise the state is running.
    Tool callaic_session_read { "session_id": "<id>", "turn_id": "<turn-id>", "since": 0, "await_ms": 5000 }
    What happensRead this turn using its returned reference. While turn_state is running, repeat with next_since; then inspect the final outcome and actual project result before closing.
    Tool callaic_session_close { "session_ids": ["<id>"] }
    AgentThe session found four TODO comments, in two files, and is closed.
    Step 5 of 5

    Delegate a task and read the answer

    What you get

    A finished task from a second agent, read from the stored record, and a closed session. Without purge, stored events remain subject to the age policy and shared storage budget; this is not a guaranteed holding period. Retain important results elsewhere, and add purge only when the saved record is no longer needed.

Result

A server your agent can delegate through.

MCP AIC is connected and your agent can open sessions in the folders you allowed. Keep the limits in mind: 16 live sessions per server, four per client by default. Next, read Safety and limits before you give a session more than the default.

Next

Where to go next.