Skip to content
Axint

Xcode

Axint does not replace Xcode’s own workspace/build/test tools. It sits alongside xcrun mcpbridge so your agent can generate Apple-native code, then use Xcode’s tools to write files, build, preview, and test.

One-step setup

npx -y -p @axint/compiler axint xcode setup

This is the fastest way to configure the local agent side of the loop.

Remote MCP for agent workflows

If you want the hosted HTTP endpoint instead of local stdio:

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

Canonical remote endpoint: https://mcp.axint.ai/mcp

  1. Use Axint tools to scaffold or compile the Apple-native surface.
  2. Use xcrun mcpbridge tools to write files into the Xcode project.
  3. Build and preview inside Xcode to confirm the output behaves correctly.

Also useful

  • The SPM build plugin remains the right option when you want compile-time generation on every build.
  • Xcode happy path → is the shortest install → build → check → packet → rerun walkthrough.
  • Fix Packets → explains the repair contract that the plugin and Xcode helpers both read.
  • axint-examples gives you starter repos that are easier to test in Xcode than isolated snippets.