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.
Hosted iCloud Contacts
Turn your contact book into exact, permission-scoped agent context.
Search, update, group, and batch-manage contacts from one MCP endpoint.
carddav://connectedWhat you can do
- List contacts, search by available contact fields, and fetch one exact contact record.
- Pear reports ambiguous or incomplete person matches instead of silently choosing a contact.
- Create, update, and delete contacts when contact-write access and approval are available.
- List, create, and delete contact groups, then add an exact contact to a selected group.
- Update contact photos or create and delete contacts in batches when the active permissions and write policy allow it.
- Use Pear’s hosted CardDAV connection instead of maintaining a local CardDAV integration.
From setup to your first request
Make the connection. Then make it useful.
Follow your client’s setup guide, then try a request with the accounts you have connected.
Try first
Start with a question.
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.
Setup path
Connect once. Keep your apps close.
Create a Pear account and connect iCloud with an Apple App-Specific Password.
Follow the maintained setup guide for your chosen AI client and its documented authentication path.
Test a contact search first, then approve only the write actions you intend to make.
Why it matters
A little less switching.
Bring accurate contact details into planning, scheduling, and outreach prompts.
Avoid maintaining local CardDAV discovery, parsing, and write logic.
Keep ambiguous person matches and consequential contact changes visible before execution.
- 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
A few good questions
Before you connect.
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
Ready to connect your apps?
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.