Axint MCP Server

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

Tools

Last Updated

Jun 14, 2026

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.

1 2 3 4

1–10 of 35 tools

Customize Tools

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

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.