| name | apple-docs |
| description | Local, searchable Apple developer documentation via the apple-docs CLI and MCP server (DocC, Human Interface Guidelines, App Store Review Guidelines, Swift Evolution, Swift Book, WWDC sessions, sample code, SF Symbols). Use whenever an answer depends on exact Apple API behavior, availability, HIG/review-guideline wording, or WWDC content — before trusting training memory. Also use to set up the tooling: detect whether the MCP server or CLI is available and propose installation if not.
|
| allowed-tools | ["Read","Glob","Grep","Bash"] |
Apple Docs (CLI + MCP)
Primary-source verification beats memory. When a claim about an Apple API,
HIG rule, or review guideline is load-bearing, verify it against the
documentation corpus — offline-first via
apple-docs.
Step 0: Detect What's Available
- MCP server: are
mcp__apple-docs__* tools available in this session
(search_docs, read_doc, list_frameworks, browse, list_taxonomy,
search_sf_symbols, render_sf_symbol, …)? Use them directly.
- CLI:
command -v apple-docs — if present, use the CLI.
- Neither → propose installation (below). Never silently fall back to
memory for version-sensitive claims; say what could not be verified.
Usage Patterns
MCP (preferred when available)
search_docs first (tiered search), then read_doc on the best hit.list_frameworks / browse to orient in an unfamiliar framework.search_sf_symbols / render_sf_symbol for symbol availability and names.
CLI
apple-docs search "NavigationStack"
apple-docs search "Swift Testing" --source wwdc --year 2024
apple-docs search "privacy" --framework app-store-review --read
apple-docs read swiftui/view --section Overview
apple-docs read View --framework swiftui
apple-docs frameworks
apple-docs browse swiftui
apple-docs status
apple-docs --help
Query discipline
Queries are keyword-based, not natural language. Search the exact symbol,
API, or feature name ("NavigationStack", "swipeActions"), not questions
("how do I make a list swipe"). Be precise and concise; refine with
--framework/--source filters rather than longer prose.
Verification workflow
- Search the exact symbol/feature name.
- Read the matched document (prefer
--section to limit output).
- Quote availability and behavior from the doc; cite the doc key
(e.g.,
swiftui/view).
- If docs and observed compiler/runtime behavior conflict, say so explicitly.
- Last-resort fallback: if the corpus has no answer, inspect the SDK
directly —
.swiftinterface and header files inside
Xcode.app/Contents/Developer/Platforms/.../SDKs/ are ground truth for
what actually ships.
Installation (propose, don't impose)
Installing downloads a ~1.5 GB snapshot (3–8.6 GB on disk depending on
profile) — ask the user before installing, and let them pick a profile.
Full install (CLI + MCP + local website; requires Bun 1.1+)
git clone https://github.com/g-cqd/apple-docs.git
cd apple-docs
bun run dev:setup
apple-docs setup --compact
Then verify: apple-docs search "NavigationStack" (works offline).
MCP wiring
apple-docs mcp install
claude mcp add -s user apple-docs -- apple-docs mcp start
No-install fallback (public instance; best-effort, no SLA)
claude mcp add -s user --transport http apple-docs https://apple-docs-mcp.everest.mt/mcp
For production/team use, self-host instead of relying on the public instance.
Guardrails
- Ask before downloading the snapshot or writing MCP config.
- Treat corpus age as part of the answer:
apple-docs status; suggest
apple-docs sync when the corpus predates the SDK under discussion.
- Quote documentation rather than paraphrasing when wording matters
(App Store Review Guidelines, HIG).
Related Skills
| Need | Skill |
|---|
| iOS 26-era API references (curated) | apple-platforms |
| SDK 27 SwiftUI deltas | swiftui-whats-new-27 |
| Build/test/run workflows | xcode-agentic |
