How Wix scaled AI-native work to 5,000 employees with Willow
Read More
Enterprise Connectors
Axint logo. Axint MCP server connector.

Axint MCP Server

Apple-native AI agent execution: 36 MCP tools, 5 prompts, compile, validate, repair, and prove.

ToolsTools
35
Last updatedLast Updated
CategoryCategory
All
✓Enterprise-grade security
✓SSO & authentication ready
✓Full governance & audit logs

What is the Axint MCP Server?

The Axint MCP server gives AI agents structured, permission-aware access to Axint through the Model Context Protocol. With 35 pre-built actions, agents can read, create, and update Axint data on behalf of authorized users.

Willow ships the Axint MCP server as part of an enterprise control plane. Every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to a full audit trail, and integrates with Splunk and Loki for SIEM visibility. Connect from Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, or any custom agent. Install once, distribute org-wide, and see exactly how Axint is being used by every AI agent in your stack.

Tools

axint.status

Report the exact running Axint MCP server version, package path, uptime, registered tool count, and same-thread MCP reload/update instructions. Use this as the first tool in a new Codex, Claude, or Xcode agent chat to prove which Axint... Use: call first or after an MCP reload to prove the connected server version; do not use as an npm/PyPI lookup. Effects: read-only; writes no files; no auth or network required.

axint.upgrade

Check the latest Axint package and optionally apply the upgrade while preserving the current agent thread. Returns exact install commands, optional Xcode MCP wiring refresh, .axint/upgrade/latest.*... Use: call when axint.status shows a stale server; not for app dependency upgrades. Effects: destructive when apply=true: can run package installs, refresh Xcode wiring, and write .axint/upgrade; may use npm network.

axint.doctor

Audit the current Axint runtime and project wiring: running MCP version, expected version, Node/npm/npx paths, project .mcp.json, AGENTS.md, CLAUDE.md, .axint/project.json, and Xcode Claude Agent registration. Use this when an agent might be connected... Use: call when MCP wiring, package paths, Xcode setup, or project memory may be stale. Effects: read-only inspection; writes no files; no auth or network required.

axint.xcode.guard

Guard an Xcode agent session against context compaction and Axint drift. Checks project memory files, active Axint session, latest Axint Run or guard proof, and long-task freshness. Writes... Use: call around long Xcode tasks, context recovery, broad Swift edits, or before claiming runtime proof. Effects: writes .axint/guard proof and may start a session; does not edit app source or use network.

axint.xcode.write

Write a file inside the Xcode project through the Axint guard path. For Swift files, runs axint.swift.validate and axint.cloud.check immediately, then records .axint/guard/latest.* proof. Use... Use: use only for guarded Xcode-project file writes; outside Xcode, patch normally and validate after. Effects: writes the requested file inside cwd, may create dirs, validates Swift, and may write guard/check artifacts.

axint.session.start

Start an enforced Axint agent session. Writes .axint/session/current.json plus token-scoped session history, refreshes .axint/AXINT_REHYDRATE.md, returns compact operating memory, docs context, a session token, and the exact axint.workflow.check... Use: call at the start of a tool-enabled agent session or after context compaction. Effects: writes .axint/session and rehydration artifacts; no auth or network required.

axint.feature

Generate a scaffolded Apple-native feature package from a description. Returns multiple files: compile-aware Swift source, companion widget/view, Info.plist fragments, entitlements, and XCTest scaffolds — all structured file-by-file so an Xcode agent can write each... Use: use for new Apple-native surfaces; not for repairing existing app bugs. Effects: read-only generated output; writes no files and uses no network.

axint.project.pack

Generate the Axint project-start pack for a new Apple app without writing files. Returns .mcp.json, AGENTS.md, CLAUDE.md, .axint/AXINT_MEMORY.md, .axint/project.json, and .axint/README.md so an Xcode/Codex/Claude agent can install the... Use: use to bootstrap an Apple project with Axint instructions; not to inspect an existing project. Effects: read-only generated file pack; writes no files and uses no network.

axint.project.index

Scan the local Apple project and write a compact .axint/context pack so Axint can reason over changed files, nearby SwiftUI surfaces, and interaction-risk files instead of only one source file at a time. Use: use before project-aware repair, multi-file SwiftUI work, or interaction-risk analysis. Effects: writes .axint/context unless dryRun=true; reads local project files only.

axint.project.syncVersion

Update Axint-owned project-pack version hints after an upgrade. Use this after axint.upgrade or npm/pip upgrades so .axint/project.json, AGENTS.md, CLAUDE.md, and Axint rehydration docs stop pointing agents at an older package version. Use: use after package upgrades so local project-pack hints stop naming old Axint versions. Effects: updates Axint-owned project instruction files unless dryRun=true; no network.

axint.context.memory

Return the compact Axint operating memory that agents should reload at new chat start, after context compaction, or after long coding drift. Use this to keep Axint top-of-mind without rereading the full docs. Use: use after compaction or session restart when the agent needs compact operating rules. Effects: read-only generated context; writes no files and uses no network.

axint.context.docs

Return the project-local Axint docs context that agents should reload after new chats or context compaction. This is the durable docs memory that keeps the agent using Axint instead of forgetting the workflow. Use: use after compaction when the agent needs workflow docs without rereading the whole site. Effects: read-only generated docs context; writes no files and uses no network.

axint.suggest

Suggest Apple-native features for an app based on its description. The domain is only a weak hint; the app description wins. Returns a ranked list of features with recommended surfaces (intent, widget, view,... Use: use before generation to choose Apple surfaces; not a substitute for registry search or validation. Effects: local mode is read-only; Pro mode may call Axint endpoint when credentials are configured.

axint.registry.search

Search the Axint Registry for already-published packages that match a natural-language query. Use this BEFORE calling axint.feature or axint.compile so the agent can install an existing package instead of... Use: use before generating code to find reusable packages; not for validating local Swift. Effects: read-only local registry search using AXINT_REGISTRY_PATH or sibling checkout; no network by default.

axint.workflow.check

Read-only agent workflow gate. Requires the current Axint session token from axint.session.start unless requireSession=false is explicitly set. Use this at session start, after context compaction, before planning, writing, building, or... Use: use at stage gates to prove Axint workflow coverage; not a final build/test substitute. Effects: read-only gate but may update tiny workflow freshness stamps; no network.

axint.scaffold

Generate a starter TypeScript intent file from a name and description. Returns a complete defineIntent() source string ready to save as a .ts file — no files are written, no network requests made. On invalid domain values, returns an error string.... Use: use to create a small TypeScript intent starter; use templates for richer examples. Effects: read-only generated TypeScript; writes no files and uses no network.

axint.compile

Compile TypeScript source (defineIntent() call) into native Swift App Intent code. Returns { swift, infoPlist?, entitlements? } as a string — no files written, no network requests. On validation failure, returns diagnostics... Use: use when TypeScript DSL source should become Swift; use validate for cheaper preflight only. Effects: read-only generated Swift/diagnostics; writes no files and uses no network.

axint.validate

Validate a TypeScript intent definition without generating Swift. Runs the full Axint validation pipeline (134 diagnostic rules) and returns a JSON array of diagnostics: { severity: 'error'|'warning', code: 'AXnnn', line: number, column: number,... Use: use for TypeScript DSL diagnostics before Swift output; use swift.validate for existing Swift. Effects: read-only diagnostics; writes no files and uses no network.

axint.fix-packet

Read the latest Fix Packet that Axint emitted locally after a compile or watch run. Returns the exact repair artifact that AI tools or Xcode helpers should consume next: verdict, top findings, full diagnostics, next steps, and an AI-ready fix prompt.... Use: use after a local compile/watch/check emitted a packet; not a new analysis pass. Effects: read-only local artifact read; writes no files and uses no network.

axint.cloud.check

Run an agent-callable Cloud Check against Swift or Axint TypeScript source. Accepts inline source or a sourcePath, then returns a Cloud-style verdict, Apple-specific findings, next... Use: use for Apple-aware source review and repair prompts; provide evidence for UI/runtime claims. Effects: read-only response from provided source/path; may use configured Cloud Check endpoint; no source is sent unless provided.

axint.repair

Plan a project-aware Apple repair for existing apps. Indexes the local project, classifies build/UI/runtime evidence, runs Cloud Check when source is provided, ranks likely SwiftUI/App files, returns a... Use: use for existing app bugs with logs, UI symptoms, or runtime evidence; not for greenfield generation. Effects: writes .axint/repair and privacy-safe .axint/feedback artifacts; reads local project files.

axint.feedback.create

Create or read a privacy-safe learning packet for Axint repair intelligence. Packets include project shape, diagnostic codes, issue class, redacted evidence, and likely product owner, but never include source code. Users... Use: use when Axint output was weak and you need a privacy-safe issue packet; not for sending source. Effects: writes or reads redacted .axint/feedback packets; never includes source by default.

axint.agent.install

Install the local Axint multi-agent project brain. Writes .axint/agent.json, .axint/context/latest.*, and .axint/coordination files so Codex, Claude, Cursor, Xcode, OpenClaw, and humans coordinate through the same local truth layer. Use: use once per project to create local multi-agent coordination; not needed for one-off compile. Effects: writes .axint/agent, context, and coordination files; no network.

axint.agent.advice

Ask the local Axint project brain what this agent should do next. Reads project context, latest run proof, latest repair plan, and active file claims, then returns host-specific guidance for Codex, Claude, Cursor, Xcode, or another agent lane. Use: use when multiple tools or agents need the next safest move from local proof. Effects: reads local Axint context/proof and may refresh advice artifacts; no network.

axint.agent.claim

Claim files before an agent edits them so other agents do not patch the same SwiftUI/App files concurrently. Claims are local, short-lived, and stored in .axint/coordination/claims.json. Use: use before editing shared files in parallel-agent work; release claims when done. Effects: writes local coordination claims under .axint/coordination; no network.

axint.agent.release

Release active local Axint file claims for this agent after finishing or abandoning a task. This keeps Codex, Claude, Cursor, and Xcode from blocking each other on stale claims. Use: use after finishing or abandoning claimed files so other agents are unblocked. Effects: updates local coordination claims under .axint/coordination; no network.

axint.run

Run the enforced Axint Apple build loop outside the Xcode UI. Starts or refreshes the Axint session, validates Swift, runs Cloud Check, executes xcodebuild build/test when a project or workspace... Use: use when the agent must prove Swift validation, Cloud Check, Xcode build/test, and runtime evidence. Effects: starts child processes, writes .axint/run artifacts, may run xcodebuild/tests, and may call Cloud Check.

axint.run.status

Read the latest or selected Axint run job record, including active child process IDs. Use this when a long xcodebuild run may still be active after an MCP timeout or client disconnect. Use: use after MCP timeouts or long builds to resume without guessing whether xcodebuild is still active. Effects: read-only local run/job inspection; writes no files and uses no network.

axint.run.cancel

Cancel the latest or selected Axint run by killing active child process groups. Use this when xcodebuild or a UI-test runner survived an MCP timeout or transport close. Use: use only to stop an active Axint run or stuck child process group. Effects: destructive: kills active Axint child process groups; no network.

axint.tokens.ingest

Ingest design tokens from JSON, JS/TS object exports, or CSS variables and return a SwiftUI token enum. Use this before generating Swarm-style views/components so agents can preserve exact brand colors, dimensions, radii, spacing, and typography. No files... Use: use before view/component generation when a design system should be preserved. Effects: read-only Swift token output; writes no files and uses no network.

axint.schema.compile

Compile a minimal JSON schema directly to Swift, bypassing the TypeScript DSL entirely. Supports intents, views, components, widgets, and full apps via the 'type' parameter. Uses ~20 input tokens vs hundreds for TypeScript — ideal for LLM agents... Use: use for token-light JSON-to-Swift generation; use compile for full TypeScript DSL control. Effects: read-only Swift generation; writes no files and uses no network.

axint.swift.validate

Validate existing Swift source against 150 build-time rules (AX700–AX749) including Swift 6 concurrency and Live Activities. Catches bugs Xcode buries behind generic 'type does not conform' errors: missing perform() on AppIntent, missing var... Use: use on generated or edited Swift before build; pair with swift.fix for mechanical repairs. Effects: read-only Swift diagnostics; writes no files and uses no network.

axint.swift.fix

Auto-fix mechanical Swift errors detected by axint.swift.validate. Handles 20+ fix rules: rewrites @State let → @State var, injects perform() into AppIntents, drops var body stubs into Widgets and Apps, adds let date: Date to TimelineEntry,... Use: use after swift.validate when errors are mechanical; inspect remaining diagnostics manually. Effects: read-only fixed-source output; writes no files and uses no network.

axint.templates.list

List all 26 bundled reference templates in the Axint SDK. Returns a JSON array of { id, name, description } objects — one per template. Templates cover messaging, productivity, health, finance, commerce, media, navigation, smart-home, and entity/query patterns. No input... Use: use to discover valid template ids before templates.get. Effects: read-only template metadata; writes no files and uses no network.

axint.templates.get

Retrieve the full TypeScript source code of a specific bundled template by id. Returns a complete, compilable defineIntent() file as a string — ready to save as .ts and compile with axint.compile. Includes perform() logic, parameter definitions, and... Use: use to fetch a complete reference template; edit before compiling into an app. Effects: read-only template source; writes no files and uses no network.

Customize tools

Customize Tools

Edit descriptions, modify arguments, select tools, or add new ones

ReviewEdit descriptions
ConfigureChange arguments
ApproveSelect tools
Create NewAdd tool

Set Up Your Axint MCP Server in Minutes

Add the following configuration to your MCP client. Authentication is handled via OAuth. Compatible with Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code, n8n, and any MCP-compatible agent.

Claude Desktop

claude_desktop_config.json
{
  "mcpServers": {
    "willow-axint": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/axint"
    }
  }
}

Cursor

.cursor/mcp.json
{
  "mcpServers": {
    "willow-axint": {
      "type": "http",
      "url": "https://<org>.mcp-s.com/mcp/mcp/axint"
    }
  }
}

Claude Code

CLI
claude mcp add willow-axint --transport http https://<org>.mcp-s.com/mcp/mcp/axint

n8n

HTTP Request Node
{
  "url": "https://<org>.mcp-s.com/mcp/mcp/axint",
  "method": "POST"
}

Or click "Install with Willow" above to set up automatically with SSO and RBAC preconfigured.

Enterprise Governance for Axint

Willow adds the layer Axint and every other SaaS doesn't ship out of the box: every call runs behind SSO (Okta, Azure AD), enforces RBAC and least-privilege at runtime, writes to full audit logs, and detects shadow AI usage across your stack. One MCP gateway. Any agent. Every tool.

Axint MCP Server FAQ

What is the Axint MCP server?

The Axint MCP server is a Model Context Protocol implementation that lets AI agents like Claude, Cursor, and ChatGPT read and write Axint data through a standardized interface. Willow hosts and governs this server so enterprises can roll it out without a security review backlog.

How is Willow's Axint MCP server different from the official one?

The official Axint MCP server is scoped to a single user's account and does not include enterprise governance. Willow's version adds SSO, RBAC, audit logging, shadow AI detection, and centralized control over which actions agents can take across the entire org.

Which AI clients work with the Axint MCP server?

Claude Desktop, Claude Code, Cursor, ChatGPT, VS Code with MCP support, n8n, and any custom agent built with OpenAI Agents SDK, LangChain, Vercel AI SDK, or Anthropic SDK.

Is the Axint MCP server secure? How does Willow handle authentication?

Every call runs behind your existing SSO (Okta, Azure AD). Per-user OAuth scopes the agent to exactly what that user can do in Axint, nothing more. No credentials reach the LLM. Every action writes to an audit trail.

Can I limit which Axint actions agents can take?

Yes. Willow lets you scope agents to specific actions, specific projects, or specific environments. Toggle actions on or off in the dashboard, or enforce policy via infrastructure-as-code through GitHub.

How do I detect shadow Axint MCP servers in my org?

Willow's browser extension and discovery service surface unmanaged MCP servers, skills, and AI agents across the org. If a developer installed an unapproved Axint MCP locally, you'll see it.

What does the Axint MCP server cost?

Pricing depends on org size and deployment model (SaaS, dedicated cloud, self-host). See withwillow.ai/pricing or contact sales for a quote.

How do I install the Axint MCP server with Willow?

Install via the Willow Connect Panel in one click, or paste the JSON snippet above into your Claude Desktop, Cursor, or Claude Code config. SSO and RBAC inherit from your existing Willow setup.

Compare Willow MCP Gateway

See how Willow stacks up against other MCP platforms on governance, security, and enterprise readiness.

Your agents are already in the wild.

Give them a Basecamp. Go from AI chaos to AI work, in minutes.