Skip to content
iCloud Contacts MCP

Give AI assistants useful iCloud Contacts context without running CardDAV locally.

Pear connects to iCloud Contacts over hosted CardDAV and exposes contact tools from one MCP endpoint. Start with search and exact-contact reads; create, update, group, photo, and batch actions require the applicable permissions and active write policy.
Apple App-Specific Password, not your main password
Contact writes follow the applicable permission and active policy
Revoke the App-Specific Password from your Apple Account
Hosted iCloud Contacts
carddav://connected

Search, update, group, and batch-manage contacts from one MCP endpoint.

Ask your assistant

Find Alex Chen in my iCloud contacts and show the exact match before making changes.

1

List contacts, search by available contact fields, and fetch one exact contact record.

2

Pear reports ambiguous or incomplete person matches instead of silently choosing a contact.

3

Create, update, and delete contacts when contact-write access and approval are available.

What Pear unlocks

Turn your contact book into exact, permission-scoped agent context.

01

List contacts, search by available contact fields, and fetch one exact contact record.

02

Pear reports ambiguous or incomplete person matches instead of silently choosing a contact.

03

Create, update, and delete contacts when contact-write access and approval are available.

04

List, create, and delete contact groups, then add an exact contact to a selected group.

05

Update contact photos or create and delete contacts in batches when the active permissions and write policy allow it.

06

Use Pear’s hosted CardDAV connection instead of maintaining a local CardDAV integration.

Try first

Prompts that prove the connection is working.

Find Alex Chen in my iCloud contacts and show the exact match before making changes.
After I approve it, create a contact for Morgan with this email address and phone number.
Add this exact contact to the Project Atlas group after showing me the selected contact and group.
Prepare a batch of these new contacts for approval without changing any existing records.
Why it matters

Pear turns one-off chats into finished provider workflows.

The connection carries context into action, while you remain in control of what gets changed.
Outcome 01

Bring accurate contact details into planning, scheduling, and outreach prompts.

Outcome 02

Avoid maintaining local CardDAV discovery, parsing, and write logic.

Outcome 03

Keep ambiguous person matches and consequential contact changes visible before execution.

FAQ

Answers for agents and search results.

Can Pear find an iCloud contact from a person’s name?

Pear can search iCloud Contacts and resolve a person conservatively. When a query has no safe single match, Pear returns ambiguity details rather than guessing which contact you meant.

Can an AI assistant manage iCloud contact groups and photos?

Pear exposes tools for contact groups, group membership, contact photos, and batch contact changes. Those are write actions, so the current Pear permissions and active write policy must allow the exact operation.

Does an iCloud Contacts MCP connection require a Mac?

No local Mac service is required for Pear’s hosted CardDAV connection. Your AI client still needs a documented remote MCP setup path, and the tools it exposes depend on its current authentication and permissions.

iCloud Contacts MCP

Give your assistant a real action layer.

Pear connects to iCloud Contacts over hosted CardDAV and exposes contact tools from one MCP endpoint. Start with search and exact-contact reads; create, update, group, photo, and batch actions require the applicable permissions and active write policy.