Codex

Codex works best with Axint when the MCP server is always available in your global config. That gives Codex direct access to the same compile, validate, feature-generation, and template tools used everywhere else in the stack.

Quick start

codex mcp add axint -- npx -y @axint/compiler axint-mcp

Axint will show up in Codex as an MCP server named axint. The server is configured through ~/.codex/config.toml.

Manual local config

{
  "mcpServers": {
    "axint": {
      "command": "npx",
      "args": [
        "-y",
        "@axint/compiler",
        "axint-mcp"
      ]
    }
  }
}

Remote MCP fallback

Use the hosted endpoint when you want Codex to talk to Axint over HTTP instead of spawning the local CLI:

codex mcp add axint --transport http https://mcp.axint.ai/mcp

If you need a full JSON shape instead of a CLI command:

{
  "mcpServers": {
    "axint": {
      "url": "https://mcp.axint.ai/mcp"
    }
  }
}

Best workflow

1. Ask Codex to scaffold or generate a feature with axint.feature.
2. Let Codex compile with axint.compile or validate with axint.validate.
3. If you are on a Mac, enable sandbox validation so Codex can prove the Swift actually builds.
4. Use axint-examples when you want a full working repo instead of a one-file demo.

Notes

• The canonical local package is @axint/compiler.
• Legacy names like @axintai/compiler are deprecated and should be replaced everywhere.
• The hosted remote endpoint is https://mcp.axint.ai/mcp.