Axiom MCP Server by Charles Wiltgen: Setup for Claude, Cursor and Other Apps

• Lists the Axiom skills by category

  Shows every Axiom skill grouped by category, such as UI and Design. You can narrow it to one category or ask for a one-line blurb per skill. It is the starting point for finding what exists.

  Try: “Show me the Axiom skill catalog for concurrency.”

  Read · axiom_get_catalog

• Searches skills by keyword

  Ranks skills against your keywords and shows the matching section names. You can filter by skill type, category or source and cap the number of results (default 10).

  Try: “Search the Axiom skills for "swift 6 data race".”

  Read · axiom_search_skills

• Reads a skill, or just parts of it

  Returns the text of up to 10 skills per call. For a large skill it sends the section list first, so the assistant can ask for only the sections it needs, or force the whole text.

  Try: “Read the navigation section of axiom-swiftui.”

  Read · axiom_read_skill

• Fetches an agent's instructions

  Returns the full instructions for one Axiom agent, such as build-fixer or accessibility-auditor. The assistant then follows them itself; the server does not run the agent.

  Try: “Get the build-fixer agent and follow it for my failing build.”

  Read · axiom_get_agent

• Launches a simulator app and records its console

  Starts an app in the iOS Simulator by bundle id and captures everything it prints or logs, as JSON. It stops after the time or line limit you set. Per the README it ends and relaunches the app if it is already running, and it can also save the capture to a file.

  Try: “Launch com.example.MyApp in the simulator and capture 30 seconds of logs.”

  Runs code · axiom_xclog_launch

• Reads logs from a running simulator app

  Attaches to a simulator process by name or pid and collects its os_log, NSLog and Logger output as JSON. It does not see print or debugPrint output. A time or line limit ends it.

  Try: “Attach to MyApp and show me the Logger output for one minute.”

  Read · axiom_xclog_attach

• Shows recent logs after a crash

  Pulls recent logs for a process from the simulator or a connected device, going back 5 minutes by default. It reads only.

  Try: “Show the last 10 minutes of logs for MyApp from my iPhone.”

  Read · axiom_xclog_show

• Lists apps installed on a simulator

  Returns the apps installed on a simulator as JSON, so you can find the bundle id to use with the launch tool.

  Try: “List the apps installed on the booted simulator.”

  Read · axiom_xclog_list

• Turns a crash file into a readable report

  Reads a crash file (.ips, MetricKit JSON, old .crash or .xccrashpoint), finds the matching debug symbols, translates addresses into function names and guesses the cause. A cache of symbol locations is kept between runs unless you turn it off.

  Try: “Symbolicate ~/Downloads/MyApp-2026-10-30.ips and tell me the cause.”

  Runs code · axiom_xcsym_crash

• Checks debug symbols match a crash

  Compares the debug symbol files it can find against each library in a crash file by ID and chip type. Use it when a crash report stays unreadable.

  Try: “Check whether my dSYMs match this crash file.”

  Runs code · axiom_xcsym_verify

• Looks up addresses in a symbol file

  Turns one or more memory addresses into function names using a given dSYM and load address.

  Try: “Resolve 0x100abc000 against MyApp.dSYM with load address 0x100a00000.”

  Runs code · axiom_xcsym_resolve

• Finds a dSYM by its ID

  Searches the cache, Xcode folders and Spotlight for the debug symbol file with a given UUID.

  Try: “Find the dSYM with UUID 4C2B7F10-0000-0000-0000-000000000000.”

  Files · axiom_xcsym_find_dsym

• Lists dSYMs on your Mac

  Lists the debug symbol files it knows about in Archives, DerivedData, Downloads, toolchains and any folders you configured.

  Try: “List the dSYMs I have in Archives.”

  Files · axiom_xcsym_list_dsyms

• Groups many crashes by root cause

  Takes a file of crash reports, one per line, and sorts them into families with likely causes, flagging noise. It works offline and needs a file path, not piped input.

  Try: “Triage crashes.jsonl for the 3.2 release and group them.”

  Files · axiom_xcsym_triage

• Strips personal data from a crash file

  Removes paths, device names and identifiers from a crash file so you can share it. It returns the clean copy, or writes it to a path you give. The original is not changed.

  Try: “Anonymize this crash file so I can attach it to a bug report.”

  Write · axiom_xcsym_anonymize

• Checks the profiling setup

  Confirms that Apple's xctrace is available and counts the Instruments templates and connected devices. Run it first if profiling fails.

  Try: “Check whether profiling works on this Mac.”

  Runs code · axiom_xcprof_doctor

• Finds slow spots in a profiling trace

  Reads an existing .trace file and reports CPU use, main-thread stalls (over 250 ms by default) and heavy call stacks, with your own code called out.

  Try: “Analyze launch.trace and list the main-thread hangs.”

  Runs code · axiom_xcprof_analyze

• Compares two traces for regressions

  Diffs a baseline trace against a new one and reports how each function's share of CPU changed. A regression counts at a 5 point rise by default.

  Try: “Compare baseline.trace with current.trace and flag regressions.”

  Runs code · axiom_xcprof_compare

• Records a new performance trace

  Records an Instruments trace by attaching to a running process, and writes it to disk. It can also start a command you give it or record the whole system, but only when the call sets allowLaunch or allowAllProcesses. Recordings stop at 60 seconds by default.

  Try: “Record a 20 second CPU trace of MyApp.”

  Runs code · axiom_xcprof_record

Watch out for

• Profiling can start any command you name

  axiom_xcprof_record launches a command you name when the call sets allowLaunch to true, and the assistant chooses that value. System-wide capture works the same way through allowAllProcesses. Approve each call by hand and read the command first. github.com

• It can restart your simulator app

  axiom_xclog_launch ends and relaunches the app in the simulator, so unsaved state in that app is lost. github.com

• It writes files to your disk

  Recording saves a .trace file, and the log capture and anonymize tools can save output to a path you give. The crash tool keeps a cache of symbol locations unless the call turns it off. github.com

• It scans folders for debug symbols

  The crash tools search Archives, DerivedData, Downloads and Spotlight for dSYM files. Keep unrelated sensitive builds out of those folders. github.com

Security advisories