AI Native Lang

MCP host integrations (OpenClaw, ZeroClaw, Hermes Agent, …)

Single entry point for wiring AINL into agent stacks that consume stdio ainl-mcp: upgrade ainlmcp from PyPI, merge mcp.servers.ainl (or YAML mcpservers.ainl on Hermes), install ainl-run under the host’s config tree, and

MCP host integrations (OpenClaw, ZeroClaw, Hermes Agent, …)

Single entry point for wiring AINL into agent stacks that consume stdio ainl-mcp: upgrade ainl[mcp] from PyPI, merge mcp.servers.ainl (or YAML mcp_servers.ainl on Hermes), install ainl-run under the host’s config tree, and suggest shell PATH updates.

Current PyPI release: ainativelang v1.3.3.

Two-step pattern (every host)

  1. Install and onboard the agent runtime using that product’s official docs (e.g. OpenClaw → openclaw.ai · Hermes Agent → github.com/NousResearch/hermes-agent).
  2. Add AINL using either:
    • Skill folder: copy skills/host/ from this repo, then chmod +x install.sh && ./install.sh, or
    • CLI: pip install 'ainativelang[mcp]' then ainl install-mcp --host openclaw, zeroclaw, or hermes (see ainl install-mcp --list-hosts).

Legacy per-host commands remain aliases:

| Host | Unified CLI | Legacy alias | |------|-------------|----------------| | OpenClaw | ainl install-mcp --host openclaw | ainl install-openclaw | | ZeroClaw | ainl install-mcp --host zeroclaw | ainl install-zeroclaw | | Hermes Agent | ainl install-mcp --host hermes | ainl hermes-install |

List supported ids: ainl install-mcp --list-hosts.

Optional ainl run adapters (e.g. code_context): MCP install wires ainl-mcp and ainl-run; it does not enable optional adapters. Workflows that call R code_context.* (tiered repo index, dependencies, impact, COMPRESS_CONTEXT) must pass --enable-adapter code_context to ainl run or the host ainl-run shim (args forward). Guide: docs/adapters/CODE_CONTEXT.md.

Older ainl wheels may only expose install-openclaw / install-zeroclaw; those are equivalent—upgrade PyPI when you want install-mcp.

Adding a new host (maintainers)

  1. Add a McpHostProfile entry in tooling/mcp_host_install.py (PROFILES): dot-directory, JSON config filename, PATH line, success tip.
  2. If the host needs extra files (like ZeroClaw’s repo bridge), branch on host_id in run_install_mcp_host or call a small helper module (see tooling/zeroclaw_bridge.py).
  3. Add skills/host/ mirroring skills/openclaw/ ( SKILL.md, README.md, install.sh ) and a doc docs/<HOST>_INTEGRATION.md.
  4. Register a thin install-<host> subcommand in cli/main.py if you want a stable alias without typing --host.

Deep dives