# agenticempire/axint [Health: Active]

**Category:** 🖥️ OS Automation  
**Repository:** https://github.com/agenticempire/axint  
**GitHub Stars:** 16  
**npm Downloads (last month):** 940  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/agenticempire-axint

## Description
Apple-native execution layer for AI agents. Compiles TypeScript to validated Swift — App Intents, SwiftUI views, WidgetKit widgets, and full apps. 13 MCP tools, 150 diagnostics, 500 tests.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "axint": {
    "command": "npx",
    "args": ["-y","-p"]
  }
}
```

## Documentation

## What agenticempire/axint MCP server does

The agenticempire/axint MCP server connects standards-compatible MCP hosts to Axint’s Apple development proof workflow. It is designed for projects that use Swift, Xcode, SwiftUI, App Intents, widgets, Live Activities, or related Apple surfaces. The server helps an agent move beyond source inspection by combining static analysis with evidence from Apple’s own build and test tooling.

Axint classifies findings as confirmed, probable, advisory, or suppressed. This distinction lets an agent separate compiler or test-backed failures from likely issues and review-oriented suggestions. Results are condensed for the next agent turn, while detailed logs and generated artifacts remain available on disk.

The workflow can also produce a Fix Packet containing the finding, likely files, a proposed next action, and a command for rerunning proof. A source-free receipt records evidence, results, hashes, and repair information without including project source.

## How it works

An MCP host starts the local server through the Axint compiler package. The agent can first call status and activation operations to confirm that the server and compiler are connected. Axint then discovers the Xcode project and scheme, checks the Swift code, runs available builds and tests, and reconciles static findings with Apple-tool output.

The same proof contract covers checking, running, generation, team context, and cloud execution. Existing projects do not need to use Axint’s generation features. When generation is useful, the compiler can lower TypeScript, Python, JSON IR, or experimental `.axint` definitions into inspectable Apple-native output, including selected intents, views, widgets, apps, metadata, and tests.

## Setup and configuration

Run the local MCP process with:

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

A local run requires no account or configuration. The project itself is supplied to Axint through its proof workflow rather than uploaded to a service. The hosted MCP endpoint is available at `https://mcp.axint.ai/mcp` for clients that use the hosted service.

## Tools and capabilities

The agenticempire/axint MCP server provides 13 MCP tools, including operations for:

- Checking server status and activating or upgrading the compiler.
- Diagnosing the local setup with a doctor operation.
- Starting sessions and accessing context memory.
- Connecting agent requests to Axint’s checking, proof, and repair workflow.

The compiler also exposes command-line operations for proving projects, compiling supported authoring inputs, applying supported deterministic fixes, and verifying receipt integrity. Receipt verification checks the payload and embedded Ed25519 signer. A locally signed receipt does not, by itself, prove an externally trusted identity.

## Limitations and notes

Axint does not automatically rewrite a project during a default proof run, install project instructions, install MCP configuration, apply fixes, or upload source. Deterministic rewrites require the explicit `--fix` option. Generated output and supported surfaces have an implementation and proof boundary, so coverage should be checked for the specific Apple feature being used.

Local execution depends on access to Apple tooling, including the project’s available Xcode build and test environment. Cloud execution exists for cases where local Apple tooling is unavailable, but the provided material does not specify cloud pricing or account requirements. Non-loopback A2A deployments require bearer authentication; this does not describe an authentication requirement for the default local MCP process.

_Full upstream README: https://allmcps.com/mcp/agenticempire-axint/readme_