Third-party MCP server for searching Apple Developer Documentation, framework APIs, Swift and Objective-C references, sample code, platform compatibility, documentation updates, and WWDC session data.
This is a third-party MCP server, not an official Apple project., The server retrieves public documentation and metadata, but user queries can still reveal private project context to the MCP client, model provider, logs, and network services., Documentation answers should be checked against the live Apple documentation before shipping platform-specific, beta, deprecated, or compatibility-sensitive code., Use `@latest` intentionally when you want the newest package; pin a version when reproducible builds or locked team tooling are required.
Privacy notes
Prompts and tool calls may include framework names, API choices, platform targets, WWDC interests, sample-code requests, app architecture details, feature plans, and compatibility constraints., MCP client logs and model transcripts can retain documentation queries and returned API text outside Apple's documentation site., Avoid sending proprietary source code, unreleased product names, customer requirements, private bundle identifiers, or internal roadmap details when a public documentation lookup is enough.
Author
kimsungwhee
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
4 safety and 3 privacy notes across 4 risk areas. Review closely: network access, third-party handling.
4 areas
SafetyThird-party handlingThis is a third-party MCP server, not an official Apple project.
SafetyNetwork accessThe server retrieves public documentation and metadata, but user queries can still reveal private project context to the MCP client, model provider, logs, and network services.
SafetyGeneralDocumentation answers should be checked against the live Apple documentation before shipping platform-specific, beta, deprecated, or compatibility-sensitive code.
SafetyGeneralUse `@latest` intentionally when you want the newest package; pin a version when reproducible builds or locked team tooling are required.
PrivacyNetwork accessPrompts and tool calls may include framework names, API choices, platform targets, WWDC interests, sample-code requests, app architecture details, feature plans, and compatibility constraints.
PrivacyExecution & processesMCP client logs and model transcripts can retain documentation queries and returned API text outside Apple's documentation site.
PrivacyGeneralAvoid sending proprietary source code, unreleased product names, customer requirements, private bundle identifiers, or internal roadmap details when a public documentation lookup is enough.
Safety notes
This is a third-party MCP server, not an official Apple project.
The server retrieves public documentation and metadata, but user queries can still reveal private project context to the MCP client, model provider, logs, and network services.
Documentation answers should be checked against the live Apple documentation before shipping platform-specific, beta, deprecated, or compatibility-sensitive code.
Use `@latest` intentionally when you want the newest package; pin a version when reproducible builds or locked team tooling are required.
Privacy notes
Prompts and tool calls may include framework names, API choices, platform targets, WWDC interests, sample-code requests, app architecture details, feature plans, and compatibility constraints.
MCP client logs and model transcripts can retain documentation queries and returned API text outside Apple's documentation site.
Avoid sending proprietary source code, unreleased product names, customer requirements, private bundle identifiers, or internal roadmap details when a public documentation lookup is enough.
Prerequisites
Node.js and npx available for running the npm package.
An MCP client that supports stdio servers, such as Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed, or Cline.
Network access to retrieve public Apple Developer Documentation, sample-code, and WWDC metadata.
Agreement on whether user prompts may include private project names, unreleased app details, or proprietary API usage questions.
Apple Docs MCP Server is a third-party MCP server for querying Apple Developer
Documentation from Claude and other MCP clients. It can search framework
symbols, fetch documentation pages, retrieve sample code references, summarize
documentation updates, inspect platform compatibility, explore technology
overviews, and search WWDC session metadata.
Use it when an Apple-platform task needs current API context without manually
opening multiple Apple documentation pages. It is especially useful for Swift,
SwiftUI, UIKit, macOS, iOS, watchOS, tvOS, visionOS, sample-code, and WWDC
research prompts.
These sources were reviewed on 2026-06-05. Prefer the live repository,
README, package metadata, license, server entrypoint, tool definitions, doc
fetcher, sample-code tool, updates tool, technology overview tool, framework
symbol search, WWDC handlers, WWDC data, and npm registry metadata for current
installation and tool behavior.
Features
Search Apple Developer Documentation with natural language prompts.
Search framework symbols for SwiftUI, UIKit, Foundation, and other Apple APIs.
Fetch detailed API documentation and related references.
List technologies and retrieve technology overviews.
Retrieve platform compatibility information for APIs and frameworks.
Search sample-code references.
Retrieve documentation update information.
Search WWDC sessions and video metadata.
Run as a stdio MCP server through npx.
Installation
Add the package to Claude Code:
claude mcp add apple-docs -- npx -y @kimsungwhee/apple-docs-mcp@latest
Ask Claude to find SwiftUI APIs for a UI behavior.
Compare UIKit, SwiftUI, and framework documentation while implementing a feature.
Look up platform availability before using an Apple API.
Find sample-code projects related to a framework.
Search WWDC sessions for a topic before implementing a new capability.
Check documentation update notes for platform changes.
Explore Apple technology overviews before scoping an app feature.
Safety and Privacy
This server is for public documentation lookup, but prompts can still leak
private development context. Keep proprietary code, unreleased app plans,
customer requirements, internal project names, private bundle identifiers, and
roadmap details out of documentation prompts unless that disclosure is approved.
Documentation can change, and beta or deprecated APIs need extra care. Verify
compatibility-sensitive guidance against the live Apple documentation before
shipping platform code.
Duplicate Check
No kimsungwhee/apple-docs-mcp entry, Apple Docs MCP entry, or matching source
URL was found in content/mcp.
Show that Apple Docs MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/apple-docs-mcp-server)
How it compares
Apple Docs MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Third-party MCP server for searching Apple Developer Documentation, framework APIs, Swift and Objective-C references, sample code, platform compatibility, documentation updates, and WWDC session data.
PostgreSQL documentation and best-practice MCP server from Timescale that gives Claude semantic and keyword search across PostgreSQL, TimescaleDB, and PostGIS docs.
Official MCP server for agent-device, Callstack's device automation CLI for inspecting, controlling, debugging, recording, and collecting evidence from iOS, Android, TV, macOS, Linux, React Native, Expo, Flutter, and native apps.
✓This is a third-party MCP server, not an official Apple project.
The server retrieves public documentation and metadata, but user queries can still reveal private project context to the MCP client, model provider, logs, and network services.
Documentation answers should be checked against the live Apple documentation before shipping platform-specific, beta, deprecated, or compatibility-sensitive code.
Use `@latest` intentionally when you want the newest package; pin a version when reproducible builds or locked team tooling are required.
✓The hosted MCP endpoint is documentation-focused and read-only, but generated SQL and migration advice still needs human review before execution.
Documentation search results can influence schema design, indexes, retention policies, and extension setup, so test generated SQL in development first.
Self-hosted deployments need database credentials and embedding configuration; keep those scoped to the docs database, not production application data.
The package can expose stdio and HTTP transports; bind local HTTP deployments only where intended and protect any non-local endpoint.
✓Agent Device MCP exposes structured tools backed by `AgentDeviceClient`; the docs state it does not expose generic shell execution over MCP.
Tools and CLI workflows can open apps, inspect UI, tap, type, scroll, perform gestures, wait, assert state, handle alerts, and close sessions.
Evidence workflows can capture screenshots, recordings, logs, traces, network traffic, performance samples, crash context, React profiles, and replay files.
Mutating commands should run serially against one session, and separate sessions or devices should be used for parallel work.
Prefer dedicated test devices or simulators, and require approval before entering credentials, submitting forms, changing settings, installing apps, sending messages, or touching production accounts.
✓AI Game Developer can create, move, copy, modify, and delete Unity assets, scenes, GameObjects, components, scripts, packages, and generated project files.
Tools include dynamic C# script execution, C# reflection method lookup and calls, package installation/removal, Unity test execution, editor state changes, play mode control, screenshots, and profiler access.
The MCP server supports streamable HTTP and stdio; HTTP deployments should require a bearer token and stay bound to trusted interfaces.
Server variables include optional authorization and webhook settings; webhook endpoints can receive tool, prompt, resource, connection, and authorization events.
Unity runtime connections can expose compiled game state or in-game behavior to an MCP client, not just editor-only project data.
Use source control, backups, tool filtering, and explicit review before allowing destructive tools such as asset deletion, package removal, script execution, or reflection calls.
Privacy notes
✓Prompts and tool calls may include framework names, API choices, platform targets, WWDC interests, sample-code requests, app architecture details, feature plans, and compatibility constraints.
MCP client logs and model transcripts can retain documentation queries and returned API text outside Apple's documentation site.
Avoid sending proprietary source code, unreleased product names, customer requirements, private bundle identifiers, or internal roadmap details when a public documentation lookup is enough.
✓Queries sent to the hosted MCP endpoint may reveal database names, schema intent, performance problems, product plans, or internal architecture details.
Self-hosted semantic search can send queries or documentation chunks to the configured embedding provider unless a local compatible endpoint is used.
Tool outputs can contain excerpts from PostgreSQL, TimescaleDB, Tiger Cloud, or PostGIS documentation that are then included in the model context.
Do not include customer data, credentials, production connection strings, or private incident details when a generalized documentation query is enough.
✓Screenshots, recordings, traces, logs, network dumps, replay files, reports, UI snapshots, typed input, and React profiles can contain private UI state, tokens, request data, customer information, or credentials.
macOS, iOS, Android, and TV automation can expose local app state, notifications, device names, package identifiers, app content, system dialogs, and permission prompts.
Network inspection artifacts may include headers, payloads, session identifiers, URLs, and API data; review before sharing or committing.
Interactive CLI runs may check npm for newer package versions unless `AGENT_DEVICE_NO_UPDATE_NOTIFIER=1` is set.
✓Tool calls may expose Unity project paths, asset names, scene hierarchy, serialized object data, scripts, logs, screenshots, profiler metrics, test output, package metadata, and runtime state.
MCP config files and Unity plugin config can contain server URLs, connection modes, bearer tokens, authorization settings, enabled tool IDs, and cloud or local endpoint details.
Optional webhooks can receive tool, prompt, resource, connection, authorization, and token-bearing request data.
Screenshots from Game View, Scene View, cameras, or isolated GameObjects may include proprietary artwork, level design, UI, debug overlays, or unreleased game content.
Generated skills and AI-client configuration files can reveal available tools, project structure, installed packages, and local workflow assumptions.
Prerequisites
Node.js and npx available for running the npm package.
An MCP client that supports stdio servers, such as Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed, or Cline.
Network access to retrieve public Apple Developer Documentation, sample-code, and WWDC metadata.
Agreement on whether user prompts may include private project names, unreleased app details, or proprietary API usage questions.
An MCP-compatible client that supports remote HTTP MCP servers.
Network access to `mcp.tigerdata.com`.
PostgreSQL, TimescaleDB, Tiger Cloud, or PostGIS questions where documentation grounding is useful.
Optional self-hosting dependencies if running the package locally, including a populated Postgres docs database and embedding provider key.
Node.js 22 or newer and `agent-device` installed globally or project-locally.
Xcode tooling for iOS, tvOS, or macOS targets, or Android SDK and ADB for Android targets.
Device, simulator, emulator, TV, macOS, or Linux desktop target that the agent is allowed to automate.
Required local permissions such as Android device trust, iOS Developer Mode, macOS Accessibility, and Screen Recording where applicable.
Unity project using Unity 2022.3 or newer for the current package metadata.
Unity Hub or a local Unity Editor installation.
Node.js 20.19 or newer, or Node.js 22.12 or newer, for `unity-mcp-cli`.
An MCP client such as Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, GitHub Copilot, Cline, or another supported client.
Install
claude mcp add apple-docs -- npx -y @kimsungwhee/apple-docs-mcp@latest
claude mcp add --transport http pg-aiguide https://mcp.tigerdata.com/docs
claude mcp add --transport stdio --scope user agent-device -- agent-device mcp