apple-docs
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPLE_DOCS_CACHE_DIR | No | Cache location. | ~/.cache/apple-docs-mcp |
| APPLE_DOCS_CACHE_TTL_HOURS | No | How long fetched indexes and pages are cached, in hours. | 72 |
| APPLE_DOCS_DEFAULT_FRAMEWORKS | No | Comma-separated slugs searched when `frameworks` isn't given. Defaults to SwiftUI, FamilyControls, ManagedSettings, ManagedSettingsUI, DeviceActivity, SwiftData, Observation, Foundation, UIKit, WidgetKit, ActivityKit, AppIntents, UserNotifications, StoreKit and Swift. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_apple_docsA | Search Apple API symbols (types, methods, properties, articles) by name. Runs over Apple's official per-framework documentation index. Without |
| get_apple_docA | 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". |
| list_apple_frameworksA | List Apple frameworks/technologies with their slugs (used by search_apple_docs |
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 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.