apple-docs
Provides tools for accessing current Apple Developer Documentation: searches Apple's per-framework DocC symbol indexes for types, methods, properties and articles, and reads full documentation pages (declaration, minimum OS availability, deprecation, discussion, parameters, code samples, topic links) as Markdown. Also lists available framework slugs so agents can search documentation for SwiftUI, UIKit, SwiftData, Foundation, StoreKit, WidgetKit and other Apple frameworks.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@apple-docs find the SwiftData @Model macro docs and show iOS availability"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
apple-docs-mcp
An MCP server that gives AI coding agents current Apple Developer Documentation: search API symbols and read full pages (declaration, availability, discussion, code samples) as Markdown.
It reads only the public DocC JSON that developer.apple.com itself loads, and searches locally over Apple's per-framework symbol indexes. It doesn't scrape Apple's search page, so it isn't affected when that page changes.
Not affiliated with or endorsed by Apple Inc. Apple, Swift, SwiftUI and other Apple marks are trademarks of Apple Inc. Documentation content is fetched from developer.apple.com at runtime and remains Apple's. This repository contains no Apple documentation.
Tools
Tool | What it does |
| Finds types, methods, properties and articles by name, ranked. |
| Returns one page as Markdown: declaration, min OS versions, deprecation, discussion, parameters, code samples, topic links. Accepts a path, a full URL, or |
| Lists framework slugs to use with |
Without frameworks, search covers SwiftUI, FamilyControls, ManagedSettings, ManagedSettingsUI, DeviceActivity, SwiftData, Observation, Foundation, UIKit, WidgetKit, ActivityKit, AppIntents, UserNotifications, StoreKit and Swift, plus any framework named in the query. Pass frameworks to search any other framework.
Example:
search_apple_docs("AuthorizationCenter")
→ AuthorizationCenter — /documentation/familycontrols/authorizationcenter (class)
→ func requestAuthorization(for: FamilyControlsMember) async throws — …/requestauthorization(for:) (method)
get_apple_doc("/documentation/familycontrols/authorizationcenter/requestauthorization(for:)")
→ # requestAuthorization(for:)
**Availability:** iOS 16.0+, iPadOS 16.0+
func requestAuthorization(for member: FamilyControlsMember) async throws
…Related MCP server: Apple RAG MCP
Install
Requires Node.js 20 or later.
Claude Code
git clone https://github.com/hyu758/apple-docs-mcp.git
cd apple-docs-mcp && npm install
claude mcp add apple-docs -- node "$(pwd)/server.mjs"Add --scope project to share it with a project through .mcp.json.
Other MCP clients (Cursor, Codex, Claude Desktop, …)
{
"mcpServers": {
"apple-docs": {
"command": "node",
"args": ["/absolute/path/to/apple-docs-mcp/server.mjs"]
}
}
}Tip: make your agent use it
Models often remember Apple APIs wrong, especially recent ones. Add a rule like this to your CLAUDE.md or AGENTS.md:
Before using an Apple API you haven't verified in this session, call `search_apple_docs`,
then `get_apple_doc`, and check availability against the deployment target. Don't write
Apple API code from memory.Configuration
Env var | Default | Meaning |
| see above | Comma-separated slugs searched when |
|
| How long fetched indexes and pages are cached. |
|
| Cache location. |
How it works
Endpoint (under | Used for |
| Framework list |
| Full symbol tree of a framework, flattened and searched locally |
| One page, rendered from DocC JSON to Markdown |
Responses are cached in memory and on disk. A search across the default frameworks takes about 0.3–1.5 s the first time and is near-instant afterwards.
Development
npm install
npm test # live smoke test against developer.apple.com
VERBOSE=1 npm test # also print tool outputCI runs the smoke test weekly. If it fails, Apple has probably changed the DocC JSON shape: adjust frameworkIndex (index shape) or getDoc / blocks (page shape) in server.mjs.
License
MIT
Available Tools
3 toolsget_apple_docGet Apple documentation pageA
Fetch one Apple documentation page as Markdown: declaration, availability (min iOS version, deprecation), discussion, code samples, parameters and topic links. Accepts a path like "/documentation/familycontrols/authorizationcenter", a full developer.apple.com URL, or "framework/symbol".
Inputs: path (required), include_topics, max_topics_per_section.
list_apple_frameworksList Apple frameworksA
List Apple frameworks/technologies with their slugs (used by search_apple_docs frameworks). Optional filter.
Inputs: filter.
search_apple_docsSearch Apple Developer DocumentationA
Search Apple API symbols (types, methods, properties, articles) by name. Runs over Apple's official per-framework documentation index. Without frameworks it searches a default set (SwiftUI, FamilyControls, ManagedSettings, DeviceActivity, SwiftData, Foundation, UIKit, WidgetKit, AppIntents, StoreKit, Swift, …) plus any framework named in the query. Use symbol names, e.g. "AuthorizationCenter", "ManagedSettingsStore shield", "NavigationStack". Then call get_apple_doc with a result path for full details.
Inputs: query (required), limit, frameworks.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The three tools map cleanly to a discover/fetch/enumerate pipeline: search_apple_docs finds symbol paths, get_apple_doc fetches a known path, list_apple_frameworks enumerates framework slugs used as a search filter. The only mild overlap (frameworks appearing in both search and list) is explicitly resolved by the descriptions telling the agent to use list for slugs and search for symbols.
All three follow a predictable verb_apple_noun pattern (search_apple_docs, get_apple_doc, list_apple_frameworks) with a shared product prefix. The singular/plural difference between 'doc' and 'docs' mirrors the single-vs-many semantics and reads naturally.
Three tools is the minimal complete surface for a documentation-lookup server: search, fetch, and enumerate frameworks. No tool is redundant and nothing feels padded or vague.
Core lifecycle is covered: find a symbol, then fetch its full page including declaration, availability, discussion, and topic links for navigation. Minor gaps remain, such as no bulk retrieval of multiple pages or explicit version/availability-scoped search, but agents can work around these with repeated calls.
Maintenance
Related MCP Connectors
Search and read Apple developer documentation, HIG, and WWDC transcripts as Markdown.
Apple developer docs and WWDC transcripts with RAG retrieval and Jev relevance ranking.
Versioned documentation registry and semantic search for AI tools and coding assistants.
Read-only search and Markdown pages from the OpenPlanr docs, for coding agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides access to Apple's official developer documentation, frameworks, APIs, and WWDC session transcripts across all Apple platforms. It enables AI assistants to search technical guides, sample code, and platform compatibility information using natural language queries.181,052 npm1,384MIT
- AlicenseNot gradedqualityBmaintenanceProvides access to Apple documentation and WWDC transcripts with semantic, keyword, and hybrid search capabilities, enabling developers to quickly find relevant code examples and technical information.121MIT
- AlicenseAqualityCmaintenanceEnables offline, real-time search of Apple Developer Documentation from Xcode's local index, returning full text, code examples, availability, and framework listings without network calls.31MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search and retrieve Apple Developer Documentation instantly with symbol search, wildcard matching, and optional semantic embeddings.61,287 npm2MIT