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.
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.
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 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.
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.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.
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.
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.
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.