All servers / Developer / Axiom MCP server
Axiom MCP server
MCP server for Axiom — Apple-platform development skills, agents, and tools
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 27.8.1. Package: axiom-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (3.4 seconds including download)
- Tools offered: 19
- Last published: 2026-11-08
- Weekly downloads (npm): 688
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
axiom_get_catalog2 of 2 parameters describedBrowse the Axiom skill catalog grouped by category (names by default; set includeDescriptions for blurbs). Start here to see what exists.
axiom_search_skills5 of 5 parameters describedKeyword-search Axiom skills (BM25-ranked) with matching section names. Use to locate skills for a topic, e.g. "data race", "SwiftUI navigation".
axiom_read_skill2 of 2 parameters describedRead skill content, token-efficiently. An unscoped read of a large skill returns its section index (not the full text) so you can re-read only the sections you need (~3 KB/section vs ~26 KB full). Pass sections to filter, full:true to force the whole skill, or listSections for just the index. Up to 10 skills per call.
axiom_get_agent1 of 1 parameter describedGet an Axiom agent's full instructions and metadata (e.g. build-fixer, accessibility-auditor).
axiom_xcprof_doctorno parametersCheck the profiling environment: verifies xctrace is available and counts Instruments templates and connected devices. Run this first when profiling tools misbehave. macOS + Xcode only.
axiom_xcprof_analyze6 of 6 parameters describedAnalyze an existing .trace bundle and return structured CPU/hang/network findings as JSON. Use to find main-thread stalls, heavy stacks, and user-code attribution. macOS + Xcode only.
axiom_xcprof_compare5 of 5 parameters describedDiff two .trace bundles (baseline vs current) and return per-function CPU-share deltas as JSON. Use for before/after regression detection in CI. macOS + Xcode only.
axiom_xcprof_record15 of 15 parameters describedRecord a new .trace by attaching to a process (default), launching a command, or capturing system-wide. Launch and all-processes are blocked unless allowLaunch / allowAllProcesses is set. Always non-interactive. macOS + Xcode only.
axiom_xclog_launch7 of 7 parameters describedLaunch a simulator app by bundle id and capture all of its console output (print/debugPrint/NSLog/os_log/Logger) as JSON. Bounded by timeout/maxLines so it always returns. macOS + Xcode only.
axiom_xclog_attach6 of 6 parameters describedAttach to a running simulator process by name or pid and capture its os_log output (NSLog/os_log/Logger; not print/debugPrint) as JSON. Bounded by timeout/maxLines. macOS + Xcode only.
axiom_xclog_show7 of 7 parameters describedShow recent logs for a process (post-mortem) by name or pid, from the simulator or a physical device, as JSON. Read-only. macOS + Xcode only.
axiom_xclog_list1 of 1 parameter describedList the apps installed on a simulator as JSON. Read-only. macOS + Xcode only.
axiom_xcsym_crash11 of 11 parameters describedSymbolicate and categorize one crash file end-to-end: parse, discover dSYMs, run atos, classify the cause. Accepts .ips (v1/v2), MetricKit MXCrashDiagnostic JSON, legacy .crash, and .xccrashpoint bundles (auto-detected). Returns a JSON report. Exits 3, 4 and 7 mean symbolication was incomplete, not that the tool failed (3=UUID mismatch, 4=arch mismatch — on the main binary, or on another image when the main binary could not be checked — 7=other images missing, or mismatched while the main binary matched); 2 means the input is missing, unreadable or unsupported, or the main-binary dSYM is missing; 1 is a usage error, or a hang or non-fatal EXC_RESOURCE report rejected with JSON whose error field (hang_report, non_fatal_resource) says where to route it; 5, 6 and 8 are real failures (tool, timeout, output). When a report was written it is still returned, followed by the exit code. macOS + Xcode only.
axiom_xcsym_triage4 of 4 parameters describedTriage a corpus of NormalizedReport JSONL (one report per line): classify each, flag suspension/idle-runloop noise, and cluster into root-cause families. Returns a JSON TriageResult. Network-free (no symbolication or dSYM discovery). Requires a file path — stdin piping is not available over MCP. macOS only.
axiom_xcsym_resolve4 of 4 parameters describedResolve one or more runtime addresses to symbols against a specific dSYM at a given load address (atos). Returns JSON. macOS + Xcode only.
axiom_xcsym_find_dsym6 of 6 parameters describedLocate a dSYM by its Mach-O UUID across the cache, default roots, and Spotlight. Returns JSON. macOS + Xcode only.
axiom_xcsym_list_dsyms2 of 2 parameters describedInventory known dSYMs across Archives, DerivedData, Downloads, toolchains, frameworks, and env roots. Returns JSON. macOS + Xcode only.
axiom_xcsym_verify6 of 6 parameters describedVerify that the discoverable dSYMs match each image in a crash file by UUID and architecture. Returns JSON. Exits 3 (UUID mismatch), 4 (arch mismatch) and 7 (missing images) flag dSYM problems and still return the report; 2 means the input is missing, unreadable or unsupported; 1, 5, 6 and 8 are real failures (usage, tool, timeout, output). macOS + Xcode only.
axiom_xcsym_anonymize2 of 2 parameters describedStrip PII (paths, device names, identifiers) from a crash file to produce a shareable fixture. Returns the anonymized crash, or writes it to a path. Does not modify the source. macOS only.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.