Apple Doc MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_technologiesB | Explore and filter available Apple technologies/frameworks before choosing one |
| choose_technologyB | Select the framework/technology to scope all subsequent searches and documentation lookups |
| current_technologyB | Report the currently selected technology and how to change it |
| get_documentationB | Get detailed documentation for specific symbols within the selected technology. Use this for known symbol names (e.g., "View", "Button", "GridItem"). Accepts relative symbol names. |
| search_symbolsA | Search and discover symbols within the currently selected technology. Use this for exploration and finding symbols by keywords. Supports wildcards (* and ?). For specific known symbols, use get_documentation instead. |
| get_versionB | Get the current version information of the Apple Doc MCP server |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity. The descriptions explicitly differentiate between tools like 'search_symbols' for exploration and 'get_documentation' for known symbols, and 'choose_technology' versus 'current_technology' versus 'discover_technologies' serve separate functions in the technology selection workflow.
All tool names follow a consistent verb_noun pattern in snake_case, such as 'choose_technology', 'get_documentation', and 'search_symbols'. There are no deviations in naming conventions, making the set predictable and readable.
With 6 tools, the count is well-scoped for the server's purpose of accessing Apple documentation. Each tool earns its place by covering distinct aspects like technology selection, symbol search, documentation retrieval, and version checking, without being overly sparse or bloated.
The tool surface provides complete coverage for the domain of Apple documentation access. It includes technology discovery and selection, symbol exploration and retrieval, detailed documentation lookup, and version information, with no obvious gaps or dead ends in the workflow.