mait.sh1.132.1

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

Install and configure mcp-aidc

Check that MCP AIDC and AIDC are there, connect the server to your agent, and read the diagnostics and the project's current selection before you change anything.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
Steps

Four steps from install to a first read.

MCP AIDC is an MCP tool: you check that it and AIDC are installed, point your agent at it, and then ask in plain language. Runs on Linux (amd64, arm64). On macOS and Windows, MCP AIDC runs in the managed Linux environment that AIDC Launch provides.

  1. Illustrative
    Check the versions
    $ mcp-aidc version
    mcp-aidc X.Y.Z
    $ aidc version
    aidc X.Y.Z
    Step 1 of 4

    Check that both programs are there

    The MAIT image ships both mcp-aidc and aidc. Check that each answers.

    If either is missing, get the matching installation from whoever supplies your environment. See mait-image.

    What you get

    Both programs run, so the server has something to delegate to.

  2. mcpServers entry
    {
  "mcpServers": {
    "aidc": {
      "command": "mcp-aidc",
      "args": ["serve"]
    }
  }
}
    Step 2 of 4

    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.

    If aidc is not on the PATH your client uses, add "--aidc-binary", "/path/to/aidc" to the arguments. Through MCP Registry the same server is added once with mcp_registry_add, and its tools carry the aidc__ prefix.

    What you get

    A client that starts the server on its own, and an agent that can call the five AIDC tools.

  3. Illustrative conversation
    YouCheck that the toolchain manager is healthy.
    Tool callaidc_query { "action": "doctor" }
    What happensA diagnostic report describes the applicable checks and their findings.
    AgentI will review each reported finding and separately check the tools this task requires.
    Step 3 of 4

    Run the diagnostics

    Connecting proves the server runs, not that AIDC works. Ask for the diagnostic report, which reports applicable tool-data, project, credential, update and connection findings.

    Read the findings as well as the exit code: a report can succeed and still show warnings.

    What you get

    Findings to address before a change. A completed diagnostic report does not guarantee that every required tool, download or credential will work.

  4. Illustrative conversation
    YouWhich tool versions does this project use?
    Tool callaidc_query { "action": "current" }
    What happensOne line per tool with its declared version, such as nodejs 26.10.0, kubectl 1.37.1 and helm 4.3.0, followed by the system packages the project declares.
    AgentThe project is on Node.js 26.10.0, kubectl 1.37.1 and helm 4.3.0, among others, plus its declared system packages.
    Step 4 of 4

    See what the project uses

    Ask for the current selection. It only reads.

    This call named no projectDir, so it read the project in the server's own directory. Pass an absolute projectDir to read another project.

    What you get

    The declared project selection. Check installed presence with aidc_query list, and run each required tool's own version command in the project's shell, before a build or test.

Result

A server that reads before it changes.

MCP AIDC is installed, connected and has read your toolchain. Installation and activation run immediately, with no preview. Upgrades and removals have a preview or a confirmation; see Tools for which is which.

Next

Where to go next.