Airmcp MCP Server

Apple-native MCP server - 272 tools across 29 modules. HITL, audit log, rate limits. macOS only.

Local serverstdio

What is the Airmcp MCP server?

Most developer tooling work still happens through a UI a human drives. Airmcp MCP server moves it into the conversation instead. Apple-native MCP server - 272 tools across 29 modules. HITL, audit log, rate limits. macOS only.

The short version

Then ask your client. Works with Claude, Codex, Cursor, Raycast, Xcode agents, and any other MCP client. Nothing reads or changes a client's settings until you opt in.

The tools it exposes

The server publishes 9 tools. What each one is for:

  • Profiles — starter, communications-safe, productivity, full, or
  • Opt — in network modules**: webhooks and powerautomate stay off in every
  • Per — call human approval** for destructive and sensitive actions at the
  • HMAC — chained audit log** at ~/.airmcp/audit.jsonl, with tamper detection
  • FoundationModels — backed Apple Intelligence preview requires macOS 26+, Apple
  • Platform — Status
  • macOS — Available
  • visionOS — Roadmap
  • watchOS — Roadmap

Getting it running

The server ships on npm as airmcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: AIRMCP_CODEX_CONFIG_PATH, AIRMCP_HTTP_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • macOS for the server runtime. - Node.js 20 or newer. - macOS Automation, Accessibility, Full Disk Access, Location, Bluetooth, or Photos permissions as required by the modules you enable. - The self-contained AirMCP.app distribution embeds its fixed Node runtime and the normal Swift bridge. The npm package and .mcpb do not embed the Swift binary; users of those artifacts build it from source

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Airmcp's toolset — Profiles, Opt, Per and 6 more — is a fair guide to whether it matches your workflow. It is maintained by heznpc; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Airmcp.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Profilesstarter, communications-safe, productivity, full, or
Optin network modules**: webhooks and powerautomate stay off in every
Percall human approval** for destructive and sensitive actions at the
HMACchained audit log** at ~/.airmcp/audit.jsonl, with tamper detection
FoundationModelsbacked Apple Intelligence preview requires macOS 26+, Apple
PlatformStatus
macOSAvailable
visionOSRoadmap
watchOSRoadmap

How to install the Airmcp MCP server

{
  "mcpServers": {
    "airmcp": {
      "command": "npx",
      "args": ["-y", "airmcp"],
      "env": {
        "AIRMCP_CODEX_CONFIG_PATH": "your-value",
        "AIRMCP_HTTP_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • macOS for the server runtime. - Node.js 20 or newer. - macOS Automation, Accessibility, Full Disk Access, Location, Bluetooth, or Photos permissions as required by the modules you enable. - The self-contained AirMCP.app distribution embeds its fixed Node runtime and the normal Swift bridge. The npm package and .mcpb do not embed the Swift binary; users of those artifacts build it from source
VariableDescriptionRequired
AIRMCP_CODEX_CONFIG_PATHFilesystem location the server is allowed to use.Optional
AIRMCP_HTTP_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Airmcp to Profiles.
  • Use Airmcp to Opt.
  • Use Airmcp to Per.

Frequently asked questions

It connects Airmcp to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (Profiles, Opt, Per, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Airmcp directly.