mait.sh1.132.1

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

Install and configure mcp-aiom

Check that MCP AIOM is there, read the framework from the command line, connect the server to your agent and read the same document through it.

Beta
Steps

Four steps from install to your first document.

MCP AIOM is an MCP tool: you check that it is installed, read a document yourself, point your agent at it, and then ask in plain language. It only reads, so nothing here changes your workspace.

  1. Capturedmcp-aiom 0.5.10
    Check the version and the content
    $ mcp-aiom --version
    mcp-aiom 0.5.10
    $ mcp-aiom info
    mcp-aiom
     
    Version: 0.5.10
    Framework version: 0.21.0
    Content source: embedded
    Corpus: 20 embedded file(s)
    Specifications: 12
    Skills: 1
    Scripts: 2
    Templates: 2
    Step 1 of 4

    Check that it arrived

    The MAIT image ships mcp-aiom and updates it with the image. Check that it runs and what content it carries; the application version and the framework version are two different numbers.

    The captured output was recorded with MCP AIOM 0.5.10; your version and counts depend on your installation. See mait-image.

    What you get

    The program runs, and it carries its guidance inside, ready to read.

  2. List and read the framework
    $ mcp-aiom list --kind framework
    $ mcp-aiom show --kind framework --name framework
    Step 2 of 4

    Read a document yourself

    List the framework and read it. The listing should include framework at aiom://framework/framework.

    What you get

    The framework instructions on your screen. Reading them does not install anything or perform what they describe.

  3. mcpServers entry
    {
      "mcpServers": {
        "aiom": {
          "command": "mcp-aiom",
          "args": ["serve"]
        }
      }
    }
    Step 3 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.

    Standard output carries the protocol, so do not wrap the command in a script that prints a banner. Through MCP Registry the same server is added once with mcp_registry_add, and its tools carry the aiom__ prefix.

    What you get

    A client that starts the server on its own, and an agent that can call the aiom tools and read its prompt and resources.

  4. Capturedmcp-aiom 0.5.10
    YouWhat AIOM framework content can you read?
    Tool callaiom_list_content { "kind": "framework" }
    What happensOne document is listed: framework, at aiom://framework/framework.
    AgentThere is one framework document, aiom://framework/framework. I can also list the specifications, the skills, the scripts and the workspace templates.
    Step 4 of 4

    List the same content through the agent

    Ask what framework content the agent can read. The agent lists it under the same names and addresses you saw yourself.

    Connecting is not the same as reading: ask for the named document once and check that it comes back before relying on it.

    What you get

    Proof that the agent sees the same collection you read yourself.

Result

Rules your agent can fetch on demand.

MCP AIOM is installed, connected and lists the framework you read yourself. Next, follow the loading routine: read the workspace's own declarations first, then the framework, then only the specifications that apply. See Use cases.

Next

Where to go next.