OpenClaw

Wire OpenClaw to agentry so the OpenClaw agent can create sandboxes, write files, run commands, and ship apps on your server — using a sandbox as the isolated machine it works in over MCP.

You'll need

• The agentry CLI installed and signed in. See Quick start, step 1–2.
• OpenClaw installed.
• ~3 minutes.

Add agentry as an MCP server

OpenClaw reads MCP servers from its config under an mcp.servers block. agentry runs as a local stdio server (command + args):

{
  mcp: {
    servers: {
      agentry: {
        command: "agentry",
        args: ["mcp"],
      },
    },
  },
}

Add that to your OpenClaw config (gateway-level ~/.openclaw/openclaw.json to share it across every agent, or a workspace-level .mcp.json to scope it to one). Configured servers are exposed as tools under OpenClaw's MCP plugin.

Zero-config install with mcporter

OpenClaw ships mcporter, a zero-config MCP installer that writes the config entry for you and discovers the server's tools automatically. Pointing it at the agentry mcp command saves you editing JSON by hand.

Verify

Restart OpenClaw (or reload its config) and ask:

Which agentry tools do you have?

You should see tools like sandbox_create, app_probe, command_run, file_write, port_wait. If they show up, you're wired.

Sandboxed sessions

If you run OpenClaw with its own sandboxing on, make sure the MCP plugin is on the tool allowlist so the agentry tools are reachable — otherwise the agent sees zero tools. See OpenClaw's tools/allowlist config.

If tools still don't appear, see MCP wiring troubleshooting.

Try it

Use agentry to create a sandbox and build a hello-world homepage that says "Hello from OpenClaw". Start the dev server and tell me the port.

OpenClaw should call sandbox_create, scaffold the page, run the dev server, and report the port. Open the sandbox in the dashboard and click Share for a *.agentry.live preview URL.

Pin a server

agentry mcp uses your current server (agentry server use <name>). Pin one OpenClaw config to a specific server by passing --server:

{
  mcp: {
    servers: {
      agentry: {
        command: "agentry",
        args: ["mcp", "--server", "homelab"],
      },
    },
  },
}

Path issues

If OpenClaw can't find agentry, use the absolute path from which agentry as the command. This is the most common cause of "OpenClaw lists 0 agentry tools".

Next

• Prompting — get OpenClaw to follow the right patterns.
• Ship an app — go from prototype to production URL.