mait.sh1.132.1

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

Install and configure mcp-aide

Check that MCP AIDE and AIDE are there, connect the server to your agent, and read the host setup and diagnostics before you change anything.

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
Steps

Four steps from a check to your first read.

MCP AIDE connects an MCP client to AIDE development-cluster operations. Check what is installed, register the server with your client, make one read-only request, and then continue or disconnect.

  1. bash
    mcp-aide version
aide version
    Step 1 of 4

    Prepare the environment

    Use the Linux MAIT environment. Runs on Linux (amd64, arm64). On macOS and Windows, MCP AIDE runs in the managed Linux environment that AIDC Launch provides. Connect to the server inside that environment.

    Check the installed programs from the account that will run the MCP server:

    Record both versions; they need not match. Obtain missing programs through your environment provider. Cluster and route operations need AIDE credentials with the cluster feature enabled; follow AIDE authentication.

    What you get

    Two version lines, and a clear idea of which credentials the cluster operations need.

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

    Connect the client

    Add the entry to your MCP client's configuration and restart its connection:

    Use an absolute server path when the client has a different PATH. If AIDE is elsewhere, append "--aide-binary", "/path/to/aide" to args. A registry can provide this connection using its configured backend; use the tool names it actually lists. See registry setup.

    Request tools/list and confirm the five tools in Tools appear. Tool discovery alone does not test AIDE or prepare a cluster.

    What you get

    The five tools listed by your client.

  3. json
    {"action":"setup","projectDir":"/workspace/example"}
    Step 3 of 4

    Make the first read

    Call aide_query with:

    Replace the directory with an existing directory in the server's environment. This checks installed prerequisites without applying host setup. Have the environment owner address missing prerequisites and repeat the check. Then call the same tool with action:"doctor" and read every finding, including warnings after exit zero. Neither report guarantees a later change will succeed.

    Completed commands return JSON text inside MCP content. Read isError, then decode that text for exitCode, stdout, stderr and truncated. Failure messages can instead be plain text. Troubleshooting explains the distinctions.

    What you get

    A setup report and a diagnostic report, with no change made to your host or any cluster.

  4. Step 4 of 4

    Continue or disconnect

    Use absolute projectDir and, when needed, projectFile on every project operation. Continue with the cluster tutorial only after prerequisites and authority are clear. To end this inspection exercise, disconnect through your client. Disconnecting does not stop existing clusters or remove their data. Getting started covers replacement and removal of the server connection.

    What you get

    A connected server whose target is explicit on every request.