AXINT TOOLS

35 tools from the Axint MCP Server, categorised by risk level.

EXECUTE 15 tools
Execute axint.agent.advice Ask the local Axint project brain what this agent should do next. Reads project context, latest run proof, ... Execute axint.agent.claim Claim files before an agent edits them so other agents do not patch the same SwiftUI/App files concurrently... Execute axint.agent.release Release active local Axint file claims for this agent after finishing or abandoning a task. This keeps Code... Execute axint.cloud.check Run an agent-callable Cloud Check against Swift or Axint TypeScript source. Accepts inline source or a sour... Execute axint.context.memory Return the compact Axint operating memory that agents should reload at new chat start, after context compac... Execute axint.fix-packet Read the latest Fix Packet that Axint emitted locally after a compile or watch run. Returns the exact repai... Execute axint.project.pack Generate the Axint project-start pack for a new Apple app without writing files. Returns .mcp.json, AGENTS.... Execute axint.repair Plan a project-aware Apple repair for existing apps. Indexes the local project, classifies build/UI/runtime... Execute axint.run Run the enforced Axint Apple build loop outside the Xcode UI. Starts or refreshes the Axint session, valida... Execute axint.run.status Read the latest or selected Axint run job record, including active child process IDs. Use this when a long ... Execute axint.session.start Start an enforced Axint agent session. Writes .axint/session/current.json plus token-scoped session history... Execute axint.swift.validate Validate existing Swift source against 150 build-time rules (AX700–AX749) including Swift 6 concurrency and... Execute axint.upgrade Check the latest Axint package and optionally apply the upgrade while preserving the current agent thread. ... Execute axint.workflow.check Read-only agent workflow gate. Requires the current Axint session token from axint.session.start unless req... Execute axint.xcode.guard Guard an Xcode agent session against context compaction and Axint drift. Checks project memory files, activ...

The managed route: connect Axint through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @axintai/compiler
How many tools does the Axint MCP server have? +

The Axint MCP server exposes 35 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Axint tools? +

Route the Axint server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Axint tools fall into? +

Axint tools are categorised as Read (9), Write (10), Destructive (1), Execute (15). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.