mait.sh1.142.0

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

MCP AIDE

Lets your AI agent check, create and run a development cluster on your machine, point a service at the code you are working on, and delete a cluster only after you confirm.

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

Beta
OverviewGet startedUse casesToolsProblems and fixesAll components
What it does

Operate development clusters through your agent.

MCP AIDE lets your MCP client inspect an AIDE environment, prepare a project, create or operate a cluster, redirect an existing Service to a development backend and review cleanup. It uses the installed AIDE under the account running the connection. An MCP client supporting stdio and an installed AIDE environment are prerequisites.

Inspecttarget andprerequisitesRequestintendedoperationCheck reportandapplication behaviorReviewcleanupseparately123Inspect target andprerequisitesRequest intended operationCheck report andapplication behaviorReview cleanup separately123
  1. Step 1: Inspect target and prerequisites to Request intended operation.
  2. Step 2: Request intended operation to Check report and application behavior.
  3. Step 3: Check report and application behavior to Review cleanup separately.
Why use it

What you gain over running each step by hand.

Use it when an agent needs the same development-cluster tasks you perform through AIDE. It suits a disposable project cluster and an existing application whose backend you temporarily redirect. Creating the cluster does not deploy your application or create its Service.

The delete reminder runs no command and is not an inspected plan. The MCP client must obtain the user's approval for the exact target before sending confirmation; a boolean field does not itself prove a human reviewed it.

Reliability

Know the host is ready

Problems surface before you provision anything

Typical alternative
Reading setup notes and guessing what is missing
Here
Setup and diagnostic reports your agent reads for you; you resolve missing prerequisites and read every finding, including warnings
Speed

Run a project cluster from the conversation

One conversation covers the whole cluster routine

Typical alternative
Typing initialize, create, start and stop commands yourself
Here
Your agent initializes the project, creates, starts or stops its cluster and queries status
Experience

Try a development backend

You test your code behind a real Service, then return to normal routing

Typical alternative
Editing cluster routing by hand and remembering to undo it
Here
External or internal routing that your agent applies and resets for an existing Service; compare the baseline, redirected and restored responses
Usability

Switch the default cluster

The default changes without touching the project target

Typical alternative
Looking up context names and switching them yourself
Here
Select a registered running cluster; explicit project operations still use their project file
Security

Finish work with approval

Nothing is deleted or purged without an explicit, separate confirmation

Typical alternative
Deleting a cluster and hoping the data policy was followed
Here
Cluster deletion needs a confirmation, and volume purge needs a separate one; inspect the remaining cluster and retained data afterwards
Out of the box

Plan permissions, connectivity and retained data.

Runs on Linux (amd64, arm64). On macOS and Windows, MCP AIDE runs in the managed Linux environment that AIDC Launch provides. The MAIT image supplies the server and AIDE; configuring the client connection remains a separate step. Server and AIDE versions can differ and are updated separately by the environment owner.

The connection is local stdio with no remote server address of its own. AIDE operations can require network access, valid credentials, runtime permissions and host preparation. Setup inspection and project initialization need no sign-in; cluster, route and project-guidance actions require the cluster feature. A diagnostic report can describe credential problems without preventing the rest of the report.

Every operation uses the server account's permissions and files. Project configuration, clusters, routes and volumes remain after disconnection. Lifecycle operations can affect local name resolution and HTTPS trust. Agree those changes with the environment owner. If you will stop and start the cluster, supply your own CA files rather than generateCa; see the tools reference.

Each command has a 30-minute wait and returns a prefix of at most 16 KiB from each output stream. A timeout does not undo a change; inspect current state before retrying. A successful report is not proof that an application works or all cleanup succeeded.

AIDE can refresh credentials and check for updates when it runs a report. Use the account and network access intended for the work.

Where it fits

Where it sits in the MAIT toolkit.

Installed bymait-image ships the server and AIDE
RunsThe installed AIDE under the account that runs the connection (aide-cli)
Reached throughAn MCP client over local stdio, or MCP Registry when one entry should reach all your tool servers
Alternative toRunning the AIDE command line yourself, when you want your agent to carry out the same steps
Learn more

Where to read on.

  • Get started connects the installed programs and makes a first read. Use cases guides the operating choices and Tools describes the request surface.