1. Prepare the account
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings. Make PEAR_API_KEY available to the Amp process through your local environment or secret store.
2. Add a remote server with a header
For the local Amp CLI, merge Pear into amp.mcpServers in ~/.config/amp/settings.json. Amp documents ${VAR_NAME} substitution in header values. Include the Authorization header so Amp uses that value.
{
"amp.mcpServers": {
"pear": {
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer ${PEAR_API_KEY}"
}
}
}
}A remote URL with no Authorization header can start Amp's browser sign-in. Pear has not certified an Amp OAuth client, so keep the header in place. Do not paste the expanded key into an Amp thread.
3. Verify a real tool result
Amp runs tools without approval by default. Review its tool policy before connecting personal data; a prompt asking for a draft is not a client permission boundary. Enterprise registry rules can block Pear. This local file is not automatically loaded by a remote Amp orb.
Ask Amp to call pear_provider_status and name the ready services for your account. Then ask it to find a calendar event you already know, with a narrow date range and the correct timezone.
Inspect the actual tool response. If Amp only describes how it would check your calendar, the read has not happened.
From a read to a reviewed draft
Try: “Find tomorrow's planning meeting and summarize its time and attendees. Then preview a follow-up email for me to review; do not send it.” Review the draft, recipient list, and sending account before approving any write through Pear.
Troubleshoot the connection or remove access
An authentication error calls for the URL and for PEAR_API_KEY being present in the Amp process. If a browser sign-in prompt appears, check that the header and environment variable reached the running Amp process; the prompt alone does not identify the cause. An unavailable provider calls for checking the connected account in Pear.
Revoke the key in Pear to end its access, then remove the pear server or point the environment variable at a replacement key.
Choose a useful first workflow
Start with a read. Ask which calendars are connected, find an event in a specific date range, or search a mail folder for a message you already know. Specify the account and timezone when they matter.
For Apple accounts, see iCloud setup and services and iCloud Mail workflows. For Microsoft accounts, see Microsoft 365 setup, Outlook Mail, and Microsoft To Do.
Apple Reminders availability depends on the Apple account. For Apple, Pear can read and write only the legacy reminder lists Apple still exposes through CalDAV. If the account has been upgraded to Apple's newer Reminders store, Pear cannot access those native lists and does not copy them into a separate reminder store. Apple may instead return compatibility placeholders, such as repeated "Where are my reminders?" items; Pear did not create them. Pear's safe fallback hides known placeholders and blocks writes to affected lists. Reconnecting iCloud or replacing the App-Specific Password will not change this Apple limitation. Calendar, Contacts, and Mail are unaffected, and Microsoft To Do uses Microsoft Graph and is unaffected. Full modern Apple Reminders access would require an Apple-platform companion using EventKit with the user's permission; Pear does not currently provide one. Google Workspace remains coming soon.
Pear exposes tools allowed by your account and permissions. Your AI client decides when to call them. Review recipients, dates, and content before approving writes. Read how Pear handles your data and the current plans before expanding the workflow.
Sources and compatibility status
Documentation checked on 17 October 2026. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Amp is still pending.
Official Amp MCP configuration · Tool permissions · Enterprise registry rules
