apple-docs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DEBUG | No | Set to `true` to enable debug logging. Default: off | |
| DISABLE_DNT | No | Set to `true` to drop the DNT header. Default: off | |
| JEV_GATEWAY_URL | No | URL for the `gateway` Jev provider. Default: none | |
| TYPESAFE_API_KEY | No | API key for the `typesafe` Jev provider. Default: none | |
| DISABLE_SEC_FETCH | No | Set to `true` to drop the Sec-Fetch-* headers. Default: off | |
| OPENROUTER_API_KEY | No | API key for the `openrouter` Jev provider. Default: none | |
| JEV_GATEWAY_API_KEY | No | API key for the `gateway` Jev provider. Default: none | |
| SIMPLE_HEADERS_MODE | No | Set to `true` to send minimal request headers. Default: off | |
| DEFAULT_ACCEPT_LANGUAGE | No | Accept-Language header sent to Apple servers. Default: en-US,en;q=0.9 | |
| APPLE_DOCS_MCP_CACHE_DIR | No | Directory for downloaded Apple Design files (and, when CLAUDE_PLUGIN_DATA is not set, for the WWDC data). Default: a temporary directory per server process (WWDC data: ~/.cache/apple-docs-mcp) | |
| APPLE_DOCS_MCP_JEV_RERANK | No | Set to `1` to turn on Jev semantic selection by default. Default: off | |
| DISABLE_LANGUAGE_ROTATION | No | Set to `true` to stop rotating the Accept-Language header. Default: off | |
| APPLE_DOCS_MCP_JEV_PROVIDER | No | Jev provider: `typesafe`, `openrouter` or `gateway`; required when Jev is enabled. Default: none | |
| APPLE_DOCS_MCP_WWDC_DATA_DIR | No | Directory with an already extracted WWDC data archive; nothing is downloaded when it is set. Default: unset, the data is downloaded on first use | |
| APPLE_DOCS_MCP_CACHE_MAX_BYTES | No | Size limit of the download cache, in bytes. Default: 1073741824 (1 GiB) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_apple_docsA | Search Apple Developer Documentation for APIs, frameworks, guides, and samples. Best for finding specific APIs, classes, or methods. Latency: typically 5-25 seconds (median about 10) because Apple streams the full result set; repeated identical queries are cached for 10 minutes. For browsing sample code projects, use get_sample_code. For WWDC videos, use the dedicated WWDC tools (list_wwdc_videos, search_wwdc_content). |
| get_apple_doc_contentA | Get detailed content from a specific Apple Developer Documentation page. Use this after search_apple_docs to get full documentation. Supports enhanced analysis options for comprehensive API understanding. Best for: reading API details, understanding usage, checking availability. |
| search_apple_design_docsA | Search Apple Design pages, Human Interface Guidelines JSON, and Design Resources catalog entries. Use this for HIG guidance, design resources, templates, fonts, product bezels, and Apple Design overview pages. |
| get_apple_design_contentA | Read Apple Design and Human Interface Guidelines URLs. HIG pages use Apple JSON data when available, and other /design/ pages use HTML parsing. |
| list_apple_design_resourcesB | List Apple Design Resources catalog entries with stable resource IDs, categories, platforms, formats, notes, preview image URLs, and download URLs. |
| download_apple_design_resourceA | Download a selected direct Apple Design resource into the local MCP cache and return MCP resource links. External Figma, Sketch web, and sketch:// links are reported as metadata and are not browser-authenticated downloads. |
| get_apple_design_examplesA | Return Apple Design visual examples as MCP image content blocks with base64 data and MIME type. Supports HIG images, resource thumbnails, and direct image asset URLs. |
| list_technologiesA | Browse all Apple technologies and frameworks by category. Essential for discovering available frameworks and understanding Apple's technology ecosystem. Use this when: exploring what's available, finding framework identifiers for search_framework_symbols, checking beta status. |
| search_framework_symbolsA | Browse and search symbols within a specific Apple framework. Perfect for exploring framework APIs, finding all views/controllers/delegates in a framework, or discovering available types. Use after list_technologies to get framework identifiers. |
| get_related_apisA | Analyze API relationships and discover related functionality. Shows inheritance, protocol conformances, and Apple's recommended alternatives. Essential for understanding how APIs work together. Use when: learning API hierarchy, finding protocol requirements, discovering related functionality. |
| resolve_references_batchA | Deep dive into all types and APIs referenced in a documentation page. Resolves all mentioned types, methods, and properties to understand dependencies. Use when: analyzing complex APIs, understanding type requirements, exploring API ecosystems. |
| get_platform_compatibilityA | Check API availability across Apple platforms and OS versions. Shows minimum deployment targets, deprecations, and platform-specific features. Critical for cross-platform development. Use when: planning app requirements, checking API availability, finding platform alternatives. |
| find_similar_apisA | Discover alternative and related APIs. Finds APIs with similar functionality, modern replacements for deprecated APIs, and platform-specific alternatives. Perfect when looking for better ways to implement functionality. |
| get_documentation_updatesA | Track latest Apple platform updates, new APIs, and changes. Shows WWDC announcements, framework updates, and release notes. Essential for staying current with Apple development. For detailed WWDC videos, use WWDC-specific tools. |
| get_technology_overviewsA | Access comprehensive guides and tutorials for Apple technologies. Includes getting started guides, architectural overviews, best practices, and implementation patterns. Perfect for learning new frameworks or understanding Apple's recommended approaches. |
| get_sample_codeA | Browse complete sample projects from Apple. Full working examples demonstrating best practices and implementation patterns. Different from search_apple_docs which returns code snippets. Use for learning by example. |
| list_wwdc_videosB | Browse WWDC session videos with full offline access to transcripts and code. Shows all available sessions with filtering options. Use this to discover WWDC content, find sessions by topic, or identify videos with code examples. |
| search_wwdc_contentA | Full-text search across all WWDC video transcripts and code examples. Find specific discussions, API mentions, or implementation examples. More powerful than list_wwdc_videos for finding specific content. |
| get_wwdc_videoA | Access complete WWDC session content including full transcript, code examples, and resources. Use after finding videos with list_wwdc_videos or search_wwdc_content. Provides offline access to entire session content. |
| get_wwdc_code_examplesA | Browse all code examples from WWDC sessions. Perfect for finding implementation patterns, seeing new API usage, or learning by example. Each result includes the code and its session context. |
| browse_wwdc_topicsA | List all WWDC topic categories with their IDs. Essential first step before using list_wwdc_videos with topic filtering. Returns topic IDs like "swiftui-ui-frameworks" that can be used in other tools. |
| find_related_wwdc_videosA | Discover WWDC sessions related to a specific video. Finds prerequisite sessions, follow-up content, and thematically similar talks. Essential for creating learning paths. |
| list_wwdc_yearsA | List all available WWDC years with video counts and statistics. Shows which years have content available and how many videos each year contains. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Most tools target distinct resources or actions, and domain separation (Apple Design, Developer Docs, API exploration, WWDC, samples) is clear. However, get_related_apis and find_similar_apis have overlapping purposes around discovering related APIs, which could cause confusion. A few pairs (e.g., get_wwdc_video and get_wwdc_code_examples) also have partial overlap.
All names use snake_case and follow a verb_noun pattern, which is highly consistent. Minor deviations include the selective 'apple' prefix (e.g., get_apple_doc_content vs. get_technology_overviews) and the extra '_batch' suffix in resolve_references_batch, but overall the convention is strongly predictable.
With 23 tools, the set is on the heavy side for a single MCP server, falling into the borderline range. While the breadth of domains (design, docs, APIs, WWDC) justifies many tools, some consolidation might improve usability and reduce cognitive load.
The surface covers core workflows: searching and retrieving docs, exploring APIs, accessing design resources, and browsing WWDC content including transcripts and code. Minor gaps exist, such as direct tools for release notes or cross-domain search, but agents can work around these with existing tools.