Axint MCP Server

Proof and repair for Apple coding agents: validate Swift, run Xcode evidence, repair failures, and generate inspectable Apple-native capabilities.

Remote serverstreamable-httpPython

What is the Axint MCP server?

Most developer tooling work still happens through a UI a human drives. Axint MCP server moves it into the conversation instead. Proof and repair for Apple coding agents: validate Swift, run Xcode evidence, repair failures, and generate inspectable Apple-native capabilities.

The short version

The tools it exposes

The server publishes 11 tools. What each one is for:

  • Confirmed — Deterministic analysis or matching compiler, build, or test evidence supports the finding
  • Probable — Strong static evidence identifies a likely problem, but decisive Apple-tooling evidence is incomplete
  • Advisory — A heuristic identifies a quality, accessibility, privacy, interaction, design, or runtime concern for review
  • Suppressed — Stronger evidence or a project-local review contradicts the finding; it remains in the receipt without blocking the result
  • Mode — Role in the proof loop
  • Check — Validate generated or existing Swift with evidence-aware diagnostics and appropriate abstention
  • Run — Orchestrate resumable build, test, runtime, and .xcresult evidence on a local or your own Mac runner
  • Generate — Compile smaller contracts into inspectable App Intents, SwiftUI views, widgets, Live Activities, app shells, metadata, and tests
  • Team — Preserve project context, sessions, file claims, repair packets, and handoffs across agents
  • Cloud — Run hosted checks and preserve shared proof history when local Apple tooling is unavailable
  • Surface — Use it for

What it needs from you

The JavaScript package follows the Node.js engine declared in package.json. Swift generation runs anywhere Node runs. Xcode build, test, simulator, and runtime proof require macOS with a compatible Xcode toolchain. Axint is Apache-2.0 licensed. Fork it, extend it, and ship with it. The Axint name and visual identity remain protected; see NOTICE and

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Axint's toolset — Confirmed, Probable, Advisory and 8 more — is a fair guide to whether it matches your workflow. It is maintained by agenticempire; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Axint.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
ConfirmedDeterministic analysis or matching compiler, build, or test evidence supports the finding.
ProbableStrong static evidence identifies a likely problem, but decisive Apple-tooling evidence is incomplete.
AdvisoryA heuristic identifies a quality, accessibility, privacy, interaction, design, or runtime concern for review.
SuppressedStronger evidence or a project-local review contradicts the finding; it remains in the receipt without blocking the result.
ModeRole in the proof loop
CheckValidate generated or existing Swift with evidence-aware diagnostics and appropriate abstention.
RunOrchestrate resumable build, test, runtime, and .xcresult evidence on a local or your own Mac runner.
GenerateCompile smaller contracts into inspectable App Intents, SwiftUI views, widgets, Live Activities, app shells, metadata, and tests.
TeamPreserve project context, sessions, file claims, repair packets, and handoffs across agents.
CloudRun hosted checks and preserve shared proof history when local Apple tooling is unavailable.
SurfaceUse it for

How to install the Axint MCP server

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

Configuration as documented by the project. Restart the client after saving.

Configuration

The JavaScript package follows the Node.js engine declared in package.json. Swift generation runs anywhere Node runs. Xcode build, test, simulator, and runtime proof require macOS with a compatible Xcode toolchain. Axint is Apache-2.0 licensed. Fork it, extend it, and ship with it. The Axint name and visual identity remain protected; see NOTICE and

Example prompts to try

  • Use Axint to Confirmed.
  • Use Axint to Probable.
  • Use Axint to Advisory.

Frequently asked questions

It connects Axint to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (Confirmed, Probable, Advisory, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Axint directly.