Skip to content
Axint

MCP server

Axint ships an MCP (Model Context Protocol) server alongside the CLI. Any AI assistant that speaks MCP — Claude Code, Cursor, Windsurf, and a growing list of others — can call Axint directly to scaffold, compile, validate, and browse templates without leaving the editor.

Available tools

ToolWhat it does
axint_scaffoldGenerate a complete starter intent from a name, description, domain, and parameter list
axint_compileCompile a TypeScript intent source string to Swift (+ optional Info.plist / entitlements fragments)
axint_validateParse + validate without generating Swift (faster for live linting)
axint_list_templatesList all bundled reference templates
axint_templateFetch the source of a named reference template

Setup

Pick your assistant:

The .vscode/mcp.json file

When you run axint init, the scaffolder drops a pre-wired config at .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "axint": {
      "command": "npx",
      "args": ["-y", "@axint/compiler", "mcp"]
    }
  }
}

Cursor and Windsurf pick this up automatically. Claude Code reads it if you launch it from the project root or configure it in ~/.config/claude-code/mcp.json.

Why MCP-first matters

The vast majority of App Intent authoring happens inside an AI assistant today. Developers describe what they want in natural language, the assistant drafts the Swift, and then everybody argues with the compiler for an hour.

Axint’s MCP tools short-circuit that loop. Instead of the assistant guessing at the App Intents SDK shape, it calls axint_scaffold with structured params and gets back a guaranteed-compilable file on the first try. If you tweak the file, axint_compile verifies the change in ~10ms.

On a Mac with Swift installed, the assistant can also call axint_compile with sandbox: true to get real swift build output — not just a guess at whether the code is valid, but proof it compiles under the Swift toolchain.