Apple Docs 2.0 MCP

What it does

Apple Docs 2.0 MCP lets an agent read Apple's developer material before it writes Swift or Objective-C code. It covers API reference pages, articles, tutorials, sample code, the Human Interface Guidelines, App Store Connect Help and Apple's web-service APIs such as the App Store Connect API. Pages come back as Markdown with full declarations, inheritance, related APIs and per-platform availability. It also ships 1,700 WWDC sessions from 2014 to 2026, with transcripts for 1,416 and code for 715.

Version 3.0.0 has 7 tools. The 19 of earlier releases were folded into them: get_apple_doc_content takes a `view` for related APIs, alternatives, linked pages or availability, list_technologies picks between four Apple catalogs (frameworks, sample code, updates, technology overviews) with `catalog`, and the WWDC listing, examples and related-session lookups became views of the three WWDC tools. Search and page reads go to developer.apple.com live. The WWDC tools and `search_docs_map` work offline from data in the package, the latter over an index of 336,723 page titles.

The framework list returns 200 entries unless you raise `limit`, which goes up to 500 (constants.ts at v3.0.0). That is the same count the README blames the original for stopping at, so set it when you want the whole catalog.

This is a separately published fork of Apple Docs MCP by kimsungwhee, which we also list. Its search uses the service Apple's own site uses, because the original's search comes back empty since Apple changed its search page. The engines field asks for Node.js 22.22.2 or later in the 22 line, 24.15.0 or later in the 24 line, or 26 and up. It is not affiliated with Apple.

What it needs

Node.js with npx. package.json accepts ^22.22.2, ^24.15.0 or >=26.0.0, so Node 23 and 25 are outside the range. The documentation tools need network access to developer.apple.com. No API key or Apple account.

Limits

• Rate limit Searches run one at a time, 15 seconds apart, since Apple returns nothing to quicker ones, so several searches in a row are slow
• Rate limit All requests to Apple are held to 100 a minute, with a 2-minute timeout per attempt and up to 3 retries
• Limit Pages and the technologies list are cached for 30 minutes and framework sidebars for 1 hour, so recent changes on Apple's site can lag
• Size cap list_technologies returns 200 entries by default, up to 500 with limit; search_docs_map returns 10 matches by default, up to 200
• Not covered search_docs_map matches titles only, and pages Apple added after the bundled map's date are missing unless source is "index"
• Not covered WWDC data is a bundled snapshot: of 1,700 sessions, 1,416 have transcripts and 715 have code
• Limit The get_apple_doc_content views other than "page" read the Swift page only and refuse language "occ"
• Read only Reads public documentation only; it cannot build, run or edit Xcode projects or Swift packages

Searches are sent one at a time, 15 seconds apart, because Apple returns empty results to faster requests, so a run of searches is slow; all requests are capped at 100 a minute. Documentation pages are cached for 30 minutes and technology lists for up to 2 hours, so very recent changes on Apple's site can lag. WWDC data is a bundled snapshot; only 1,416 of the 1,700 sessions have transcripts and 715 have code. Searches are not cached.

Who it suits

Suits developers building for iOS, macOS and other Apple platforms who want an agent to read Apple's own reference, design guidance and WWDC code before writing code, with nothing to sign up for. It only reads public pages, so it is low-commitment to add. Over Apple Docs MCP (apple-docs-mcp), pick this one if search there returns empty results or you want offline page-name lookup. Anyone upgrading from 2.x should expect a shorter tool list, as the old tool names are now views and catalogs of seven tools. It is not an Apple product, and it does not control Xcode or Swift packages.