Axint
About
Open-source TypeScript → native Swift compiler for Apple platforms. Compile App Intents, SwiftUI views, WidgetKit widgets, and full apps from TypeScript. AI agents write 5–15× less code. Includes MCP server with tools for compiling, validating, scaffolding, and templating Swift p
Details
- Author
- agenticempire
- Downloads
- 268
- Categories
- Developer Tools, Other, AI
Jump to
- Compile TypeScript to Swift for Apple frameworks
- Compile Swift from a JSON schema definition
- Validate TypeScript source before compilation
- Scaffold Xcode-ready Swift projects from compiled output
- Generate starter TypeScript files from built-in templates
- List all available templates with descriptions
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
AxintCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install globally via npm install -g axint. Add to your MCP config with the command axint-mcp and no arguments. Use the six provided tools (e.g., axint_compile, axint_scaffold) to compile, validate, and generate Swift projects.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"axint": {
"axint": {
"command": "axint-mcp",
"args": []
}
}
}
}McpServers
{
"axint": {
"command": "axint-mcp",
"args": []
}
}Agents can write Swift. Axint makes them prove it.
The proof and repair layer for Apple coding agents.
Axint checks the Swift your agent wrote, runs the real Xcode build and tests,
reconciles findings with Apple tooling, and returns signed proof with the exact repairs to make next.
No project rewrite. No source upload.
Prove a project·Try Cloud Preview·Connect an agent·Docs·Examples·Contribute
Local by default. Open source. Ordinary Swift.
Apple software is a graph of contracts. SwiftUI state, App Intents, Siri and Shortcuts metadata, widgets, entitlements, privacy declarations, concurrency, build settings, tests, and runtime behavior all have to agree. Code that looks right can still fail to compile, miss an interaction, or violate a platform contract.
Axint puts static analysis and Apple tooling into one repair loop. Static checks identify leads; Xcode build and test output can confirm, contextualize, or suppress them. The result stays compact enough for the next agent turn while full logs and artifacts remain on disk.
npx -y -p @axint/compiler axint prove --dir /path/to/MyApp
Axint discovers the Xcode project and scheme, checks existing Swift, runs the available build and tests, reconciles the findings, and writes proof under.axint/proof.
The default local run requires no account or configuration. It does not change Swift, upload source, install project instructions, install memory or MCP configuration, apply fixes, or rewrite the project.
When a failure needs another turn, Axint returns aFix Packet: a compact repair artifact with the finding, likely files, exact next action, and rerun command. It also writes asource-free receipt: a signed proof file containing evidence, results, hashes, and repair information without project source.
axint prove --dir /path/to/MyApp --fix axint receipt verify /path/to/MyApp/.axint/proof/latest.proof.json
--fixopts into supported deterministic rewrites and reruns the proof loop. Receipt verification checks payload integrity and the embedded Ed25519 signer. A locally signed receipt does not establish an externally trusted identity unless CI or the receiving team pins the signer fingerprint or a managed signing key.
Generate, Check, Run, Team, and Cloud are different entry points into the same contract: verdict, evidence, findings, next actions, and artifact paths.
Generation is optional for existing projects. When a feature is easier to describe as a smaller contract, Axint can emit ordinary Swift and the companion metadata required by the selected Apple surface.
import { defineIntent, param } from "@axint/compiler"; export default defineIntent({ name: "CreateCalendarEvent", title: "Create Calendar Event", description: "Creates a calendar event for the user.", domain: "productivity", params: { title: param.string("Event title"), date: param.date("Event date"), duration: param.duration("Event duration"), location: param.string("Location", { required: false }), }, perform: async ({ title, date }) => ({ success: true, message: Created ${title} on ${date}, }), });
axint compile create-calendar-event.ts --out ios/Intents/
TypeScript, Python, JSON IR, and the experimental.axintauthoring surface lower into inspectable Apple-native output. The TypeScript pipeline also supports views, widgets, apps, Live Activities, App Enums, UnionValue schemas, App Shortcuts, and extension scaffolds; see thecoverage mapfor the implementation and proof boundary of each surface.
Axint ships an MCP server for standards-compatible hosts:
{ "mcpServers": { "axint": { "command": "npx", "args": ["-y", "-p", "@axint/compiler", "axint-mcp"] } } }
Start a fresh tool session, then callaxint.statusandaxint.activateto verify that the server and compiler are connected.
The hosted endpoint athttps://mcp.axint.ai/mcpsupports both established MCP clients and the current stateless protocol generation. Compatibility is continuously checked with official SDK clients; see theprotocol compatibility contract.
For orchestrators that delegate durable work between agents, Axint also ships an authenticatedA2A server. MCP exposes individual tools; A2A exposes complete check, diagnosis, proof, and repair-planning tasks with status, streaming updates, cancellation, and source-free result artifacts.
npx -y -p @axint/compiler axint-a2a --project-root /path/to/MyApp
The Agent Card is served at/.well-known/agent-card.json. Loopback use works without setup; non-loopback deployments require bearer authentication by default.
axint.status·axint.activate·axint.upgrade·axint.doctor·axint.session.start·axint.context.memory·axint.context.docs·axint.workflow.check
axint.feature·axint.project.pack·axint.project.index·axint.project.syncVersion·axint.suggest·axint.registry.search·axint.scaffold·axint.compile·axint.validate·axint.tokens.ingest·axint.schema.compile·axint.templates.list·axint.templates.get
axint.xcode.guard·axint.xcode.write·axint.fix-packet·axint.cloud.check·axint.repair·axint.feedback.create·axint.swift.validate·axint.swift.fix
axint.agent.install·axint.agent.advice·axint.agent.claim·axint.agent.release·axint.run·axint.run.status·axint.run.cancel
axint.quick-start·axint.project-start·axint.context-recovery·axint.create-widget·axint.create-intent
- Live product metricsare regenerated from the codebase.
- The real, CI-gatedbrownfield benchmarkpublishes labeled precision, recall, and abstention cases.
- Coveragemaps supported surfaces to implementation, tests, and proof boundaries.
- Apple platform compatibilitytracks current Xcode, Swift, Siri, App Intents, Foundation Models, SwiftUI, UIKit, and App Store changes against implemented checks and canaries.
- Accessibility-label proofturns common-task accessibility evidence into a reviewable App Store readiness report.
- MCP compatibilitydocuments the hosted server's dual-era transport contract and verification path.
- A2Adocuments durable agent-to-agent proof delegation, authentication, task isolation, and the local execution boundary.
- Architectureexplains the compiler, proof, MCP, A2A, Python, and runtime boundaries.
- Release notesrecord shipped behavior and compatibility changes.
- Securitydocuments reporting, supported releases, telemetry, and dependency policy.
The highest-value contributions improve existing-project precision, Xcode evidence, repair quality, Apple API coverage, and reproducible examples.
- Start with agood first issue.
- Pick up ahelp wantedproblem.
- Read thecontribution guide.
- Ask, propose, or show your work inDiscussions.
The JavaScript package follows the Node.js engine declared inpackage.json. Swift generation runs anywhere Node runs. Xcode build, test, simulator, and runtime proof require macOS with a compatible Xcode toolchain.
Axint isApache-2.0 licensed. Fork it, extend it, and ship with it. The Axint name and visual identity remain protected; seeNOTICEandTRADEMARKS.md.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
Instead of direct calling MCP tools, mcpcode server transforms MCP tool calls into TypeScript programs, enabling smarter, lower-latency orchestration by LLMs.
Supercharge your Agent with Semantic Code Intelligence and save 💰 in the process!
AI-to-AI code review platform — Claude, Codex, and Gemini cross-check each other via MCP, REST API, and CLI for consensus-based results.
A code sandbox for AI assistants to safely execute arbitrary code. Requires a 302AI API key for authentication.
Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.
MCP server to dynamically load Claude Code skills into AI agents
MCP bridge that lets Claude Code delegate heavy tasks to the Antigravity CLI (agy) — purpose-built tools, model routing with fallback, session continuity, and output truncation to save Claude's context and tokens.
Exposes local execution of Aider commands as a detached process using MCP.
An MCP server for offloading AI coding tasks to Aider, enhancing development efficiency and flexibility.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
