Apple Contacts 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| contacts_statusA | Check Apple Contacts access and return aggregate counts without exposing contact values. |
| search_contactsB | Search Apple Contacts by name, organization, job title, email, or phone. |
| create_contactA | Create an Apple Contact. Dry-run by default; actual writes require dryRun=false and confirm=true. |
| update_contactA | Update an Apple Contact by contactId. Dry-run by default; actual writes require dryRun=false and confirm=true. |
| delete_contactA | Delete an Apple Contact by contactId. Dry-run by default and requires confirmPhrase='delete contact'. |
| test_roundtripA | Create, edit, verify, and delete one dummy contact. Requires confirm=true. |
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 targets a distinct operation: status check, create, delete, search, roundtrip test, and update. No overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_contact, search_contacts), with only 'contacts_status' varying slightly but still adhering to the pattern.
Six tools is an appropriate and focused set for managing Apple Contacts, covering core operations without unnecessary bloat.
The tool surface covers CRUD operations (create, search/read, update, delete) plus a status check and a roundtrip test for validation. No obvious gaps for the domain.