Axiom MCP Server

MCP server for Axiom — Apple-platform development skills, agents, and tools

Local serverstdio

What is the Axiom MCP server?

Most monitoring and observability work still happens through a UI a human drives. Axiom MCP server moves it into the conversation instead. MCP server for Axiom — Apple-platform development skills, agents, and tools.

The short version

Battle-tested skills, agents, and tools for modern Apple OS development — Swift 6, SwiftUI, Liquid Glass, Apple Intelligence, and more. Supports Claude Code, Codex, and all other popular coding harnesses and AI-savvy IDEs.

Axiom gives AI coding assistants deep Apple OS development expertise — the kind that prevents data loss from bad migrations, catches memory leaks before users complain, and stops you from spending 30 minutes debugging a zombie xcodebuild process.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

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

  • xclog — a built-in console capture tool that gives AI assistants access to simulator and device logs
  • xcsym — a built-in crash symbolication tool for .ips, MetricKit, and Apple's legacy .crash text crashes, with automatic dSYM discovery and pattern
  • xcui — a built-in tool to drive and validate the simulator UI and accessibility (tap by accessibility ID, dump the accessibility tree, check VoiceOver and
  • xcprof — a built-in tool to record and analyze CPU/performance traces (xctrace) without opening Instruments

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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Axiom's toolset — xclog, xcsym, xcui and 1 more — is a fair guide to whether it matches your workflow. It is maintained by charleswiltgen; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
xcloga built-in console capture tool that gives AI assistants access to simulator and device logs
xcsyma built-in crash symbolication tool for .ips, MetricKit, and Apple's legacy .crash text crashes, with automatic dSYM discovery and pattern categorization
xcuia built-in tool to drive and validate the simulator UI and accessibility (tap by accessibility ID, dump the accessibility tree, check VoiceOver and Dynamic Type)
xcprofa built-in tool to record and analyze CPU/performance traces (xctrace) without opening Instruments

Example prompts to try

  • Use Axiom to xclog.
  • Use Axiom to xcsym.
  • Use Axiom to xcui.

Frequently asked questions

It connects Axiom to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (xclog, xcsym, xcui, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Axiom directly.