MCP server de apple-docs
Commit 14 oct 2026Permite que un cliente de IA busque y recupere la documentación para desarrolladores de Apple, sesiones de WWDC y las Human Interface Guidelines en formato Markdown limpio.
También conocido como zmscode/apple-docs-mcp
- Stars
- 2
- Herramientas
- 5
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 14 oct 2026
- Licencia
- MIT
¿Qué es apple-docs MCP?
Permite que un cliente de IA busque y recupere la documentación para desarrolladores de Apple, sesiones de WWDC y las Human Interface Guidelines en formato Markdown limpio. Expone 5 herramientas, como search_docs, get_doc, browse_framework.
Resumen generado a partir del README del proyecto
Acerca del MCP server de apple-docs
Los desarrolladores que crean aplicaciones para macOS, iOS u otras plataformas de Apple pueden acceder a la documentación técnica oficial directamente a través de su cliente de IA. Este servidor basado en Swift recupera contenido de developer.apple.com, incluyendo SwiftUI, AppKit, UIKit, Foundation y SwiftData. Convierte la documentación compleja en Markdown limpio, lo que facilita que los modelos la procesen y la utilicen en tareas de programación.
Los usuarios pueden realizar búsquedas de texto completo para símbolos, artículos y código de ejemplo, o explorar árboles de símbolos de frameworks completos usando la herramienta browse_framework. El servidor también gestiona contenido de video de WWDC, proporcionando acceso a descripciones, resúmenes de capítulos y transcripciones con marcas de tiempo mediante la herramienta get_video. Soporta tanto la instalación local en macOS 13 o posterior como la integración con clientes como Claude Desktop o Claude Code.
Más allá de la documentación estándar, el servidor ofrece acceso a las Human Interface Guidelines y permite vistas específicas para Objective-C. Gestiona los datos de manera eficiente mediante el almacenamiento en caché de respuestas en memoria durante seis horas e incluye lógica de reintento integrada para mayor estabilidad de red.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Herramientas de apple-docs MCP 5
Detectado desde el READMEsearch_docsget_docbrowse_frameworkget_videolist_frameworks
| search_docs | — | |
| get_doc | — | |
| browse_framework | — | |
| get_video | — | |
| list_frameworks | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblezmscode/apple-docs-mcp is public and reachablegithub.com/zmscode/apple-docs-mcp ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-10-14github.com/zmscode/apple-docs-mcp ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo5 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo tool named like delete, drop or execAprobado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubapple-docs-mcp
An MCP server, written in Swift, for Apple developer documentation: SwiftUI, AppKit, UIKit, Foundation, SwiftData, the Human Interface Guidelines, and every other framework on developer.apple.com. Pages come back as clean Markdown.
Tools
| Tool | What it does |
|---|---|
search_docs |
Full-text search of developer.apple.com: symbols, articles, sample code, and WWDC videos. Filters: framework (also adds exact symbol-name matches from that framework's index), type (documentation, sample_code, video), and platform (for example "macOS 14"). |
get_doc |
Fetches a page as Markdown: declaration, availability, overview, parameters, code samples, topics, relationships, and sample code download links. Accepts a URL, a path (swiftui/view), a doc:// id, or a dotted name (AppKit.NSWindow). Options: language: "objc", topics (compact, full, none), section (for example "Overview" or a Topics group like "Handling Mouse Events"), hide_deprecated, and offset/max_chars for paging through long pages. |
browse_framework |
Searches or outlines a framework's whole symbol tree, for example every NSTableView* in AppKit. Works for the Human Interface Guidelines ("HIG"). Filters: query, kind, path, depth, language, hide_deprecated, hide_beta. |
get_video |
Fetches a WWDC session: description, chapter summaries, and code snippet titles by default. Use include: "code" for the code, "transcript" for the timestamped transcript, or "all". Accepts a URL or an id like wwdc2025-256. |
list_frameworks |
Lists all of Apple's documented technologies. |
Every tool returns Markdown for the model plus structured content that matches its declared outputSchema, for clients that use it.
Resources
Pages can also be attached as MCP resources:
| URI | Content |
|---|---|
apple-docs://doc/{path} |
A documentation page, e.g. apple-docs://doc/swiftui/navigationstack. Add ?language=objc for Objective-C. |
apple-docs://video/{id} |
A WWDC session, e.g. apple-docs://video/wwdc2025-256. Add ?include=transcript, code, or all. |
apple-docs://framework/{name} |
A framework's table of contents, e.g. apple-docs://framework/appkit or apple-docs://framework/hig. |
developer.apple.com URLs work as resource URIs too. The server lists the SwiftUI, AppKit, UIKit, Foundation, SwiftData, Observation, Swift, and HIG landing pages as ready-made resources.
Install
Requires macOS 13 or later and Swift 6 (Xcode or the Command Line Tools).
git clone https://github.com/zmscode/apple-docs-mcp.git
cd apple-docs-mcp
make install
This builds a release binary and installs it to ~/.local/bin/apple-docs-mcp. Set PREFIX to install somewhere else. Run it again after any change. Then restart Claude Desktop (⌘Q) and start a new Claude Code session to pick up the update.
Claude Code
claude mcp add --scope user apple-docs -- ~/.local/bin/apple-docs-mcp
Claude Desktop or another client
{
"mcpServers": {
"apple-docs": { "command": "/Users/you/.local/bin/apple-docs-mcp" }
}
}
For Claude Desktop, this goes in ~/Library/Application Support/Claude/claude_desktop_config.json.
Development
| Command | What it does |
|---|---|
make test |
Unit and end-to-end tests against saved fixtures. The first run downloads the fixtures and records the snapshots; after that, no network is needed. |
make test-live |
Checks the real developer.apple.com, to catch format changes the fixtures can't. |
make fixtures |
Re-downloads the fixtures. Follow with make snapshots and review the snapshot diff, which shows how Apple's format changed. |
make snapshots |
Re-records the Markdown snapshots in Tests/AppleDocsKitTests/Fixtures/Snapshots after an intentional rendering change. |
The fixtures are copies of Apple's pages, so they aren't checked in. Snapshots are rendered from them, so they're recorded locally too: they catch changes from your own edits, and from Apple's format after a make fixtures.
Use make test rather than plain swift test. With the Command Line Tools (no Xcode), SwiftPM passes the testing macro plugin path in a form the compiler can't use, so incremental test builds fail with "plugin for module 'TestingMacros' not found". The Makefile works around it.
The code lives in the AppleDocsKit library. Sources/AppleDocsMCP/main.swift just starts the server.
| File | Contents |
|---|---|
Server.swift |
Server setup, plus resources |
Tools.swift |
Tool definitions, search_docs, get_doc, list_frameworks, and pagination |
Browse.swift |
browse_framework, and loading framework trees |
Videos.swift |
get_video, and parsing video pages |
Renderer.swift |
Converts DocC JSON to Markdown, and applies Objective-C variants |
DocsClient.swift |
Networking, retries, caching, and search stream parsing |
Output.swift |
Structured output types and their JSON Schemas |
Configuration
| Environment variable | Purpose |
|---|---|
APPLE_DOCS_SEARCH_URL |
Overrides the search endpoint if Apple moves it. The current value is in the SEARCH_CONFIG script on developer.apple.com/search. |
How it works
- Pages are fetched as DocC render JSON from
developer.apple.com/tutorials/data/<path>.jsonand converted to Markdown. - Framework trees come from
developer.apple.com/tutorials/data/index/<framework>. Content without an index, like the Human Interface Guidelines, is outlined by following topic sections from its landing page. - Objective-C pages are produced by applying the page's
variantOverridespatches. - Video pages are HTML only, so
get_videodepends on the page's class names (supplement summary,transcript-content, and so on).make test-livewill flag it if Apple redesigns them. - Search uses the same backend as developer.apple.com/search. Apple doesn't document this endpoint, so it could change. If it fails,
search_docsfalls back to title matches from framework symbol lists (the named framework, or SwiftUI, AppKit, UIKit, and Foundation), and says so in its output. - Requests time out after 20 seconds. Timeouts, dropped connections, 429s, and 5xx responses are retried with backoff. Concurrent requests for the same URL share one download.
- Responses are cached in memory for 6 hours, up to 48 MB in total, evicting the least recently used first.
License
MIT. This project isn't affiliated with Apple; documentation content is fetched from developer.apple.com at run time and belongs to Apple.
Preguntas sobre apple-docs MCP
¿Qué herramientas proporciona apple-docs MCP?
Expone 5 herramientas, incluidas search_docs, get_doc, browse_framework, get_video, list_frameworks.
¿Qué frameworks de Apple están soportados?
El servidor es compatible con SwiftUI, AppKit, UIKit, Foundation, SwiftData, Observation, Swift y las Human Interface Guidelines.
¿Cómo puedo obtener las transcripciones de las sesiones de WWDC?
Puedes usar la herramienta get_video y establecer el parámetro include en 'transcript' para obtener la transcripción con marcas de tiempo.
¿Cuáles son los requisitos del sistema para la instalación?
Necesitas macOS 13 o posterior y Swift 6, que puedes obtener a través de Xcode o las Command Line Tools.
¿El servidor soporta documentación de Objective-C?
Sí, puedes obtener las variantes en Objective-C de las páginas usando la opción de lenguaje o añadiendo un parámetro de lenguaje a los URIs de los recursos.