Apple Contacts MCP
MCP server for Apple Contacts on macOS.
Provides access to contacts for lookup, search, and recipient resolution. Use before sending messages to resolve names into phone numbers or email addresses.
When to use
- Contact-only workflows
- Recipient validation before messaging
- Contact lookup separated from the all-in-one server
What It Does
- List and search contacts
- Full contact detail lookup
- Message recipient resolution
- Tool discovery helpers
search_toolsandget_tool_infofor context-constrained clients - Create, update, and delete contacts
- Duplicate detection and merge-candidate suggestions (
contacts_find_duplicates,contacts_suggest_merge_candidates) - Phone number and email method editing with labels
- Directory resources and recipient-check prompts
- Health and permission checks:
contacts_health,contacts_permission_guide,contacts_recheck_permissions
Install On This Mac
Quick start (uvx, from PyPI)
With uv installed:
uvx apple-contacts-mcp
No clone, no venv management.
From a clone
git clone https://github.com/JonathanRReed/Apple-MCPs.git
cd Apple-MCPs
uv sync --all-packages
This builds one workspace environment with every server's entry point in .venv/bin (for example .venv/bin/apple-contacts-mcp). You can also point an MCP client at AppleContacts-MCP/start.sh, which prefers uv run and falls back to a plain venv bootstrap (Python 3.11+ required).
Install In AI Agents
Generic MCP client config
{
"mcpServers": {
"apple-contacts": {
"command": "uvx",
"args": ["apple-contacts-mcp"],
"env": {
"APPLE_CONTACTS_MCP_SAFETY_MODE": "safe_manage"
}
}
}
}
Running from a clone instead? Use /path/to/Apple-MCPs/AppleContacts-MCP/start.sh as the command with empty args.
Claude Code example
claude mcp add --transport stdio --scope project apple-contacts -- uvx apple-contacts-mcp
Safety Modes
safe_readonlysafe_managefull_access
Transport
stdio is the default and recommended transport. Set APPLE_CONTACTS_MCP_TRANSPORT=streamable-http (with optional APPLE_CONTACTS_MCP_HOST and APPLE_CONTACTS_MCP_PORT) to serve Streamable HTTP instead.
Search Behavior
Name and organization searches use Contacts.app's filtered lookup. A no-match name returns an empty result without scanning the whole address book. Phone queries with a numeric/punctuation base, including recognized extension suffixes (ext, ext., extension, extn., x, #, and ;ext=) and an optional tel: prefix, retain the paginated directory fallback for method-value matching. Email queries containing @ retain it too. Extension matching keeps the base number and extension separate, requires the exact extension, and allows local-number suffix matching. Recipient resolution chooses the matching phone method and rejects multiple distinct matching methods.
Literal control characters and complex emoji returned by Contacts are decoded on the Python side without changing their text.
macOS Permissions
- Contacts access is required
contacts_healthreports whether Contacts access is currently available
Launch Checklist
- Add
uvx apple-contacts-mcp(or a clone'sAppleContacts-MCP/start.sh) to your MCP client - Reload or reconnect the client so the Contacts tool surface is loaded into context
- Call
contacts_healthfirst - If Contacts access is blocked, call
contacts_permission_guide - After changing macOS permissions, call
contacts_recheck_permissions
Prompting Notes
tools/listreturns the full Contacts tool surface. Context-constrained clients can usesearch_toolsfirst, thenget_tool_infofor the Contacts tool they need.- Run Contacts before any iMessage or Mail action when the user gives a person name.
- Resolve by name, phone number, or email before acting.
- If multiple contacts match, confirm the intended person before sending.
- When updating a person, pass explicit
phonesoremailsarrays only when you intend to replace that method set. - Keep a labeled phone or email on the contact before routing Messages or Mail through it.
Related
Native Contacts access
Contacts uses CNContactStore by default, so reads and writes do not wait for Contacts.app. First use compiles the packaged Swift helper with Xcode Command Line Tools and caches an application bundle under ~/.apple-mcps/build. Set APPLE_CONTACTS_MCP_HELPER_BUILD_DIR to choose another build directory. Grant Contacts access to your MCP host when macOS asks.
Set APPLE_CONTACTS_MCP_BACKEND=applescript to use the previous backend. The native backend returns first and last names directly and preserves phone/email update semantics: omit a collection to keep it, or pass [] to clear it. Contact notes require a separate macOS entitlement; a nonempty note is rejected before a native write. The AppleScript backend remains available for notes.
The native helper compiles an immutable source snapshot into a bundle named by its full SHA-256 hash. A source change during compilation is rejected, and a concurrent build cannot replace an installed bundle. Different source versions keep separate executables with the same Contacts permission identity.
The native helper is adapted from Jaume Puig's work in JaumeAP/Apple-MCPs.
Metadata
Release files for apple-contacts-mcp 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| apple_contacts_mcp-1.1.0.tar.gz | 35.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apple_contacts_mcp-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.9 kB
Release files / apple_contacts_mcp-1.1.0.tar.gz
| Download URL | apple_contacts_mcp-1.1.0.tar.gz |
|---|---|
| Size | 35.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e0893eae4ece5919d9942dd6386b4e373d843fd1f4e2c900f498794b9aa0f6d
|
|
BLAKE2b-256 checksum How to use checksums |
2ff5079ce6f9d43ec3f129943cb924cde8b5664ed2c00b4d7a66efbae4d3e041
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / apple_contacts_mcp-1.1.0-py3-none-any.whl
| Download URL | apple_contacts_mcp-1.1.0-py3-none-any.whl |
|---|---|
| Size | 29.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3827703fe9308eeaccffa038b9573a2a1ffbd2bfdd813eb0ee45e141683d4441
|
|
BLAKE2b-256 checksum How to use checksums |
6a01594eda8868971f0a6564cfd7298014b4b1f6910625981b8a3d29d9d20de1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log