1. Prepare the account
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings. Zed sends header values exactly as written. Do not put the key in a repository.
2. Add a remote context server
Open Settings → AI → MCP Servers, choose Add Server, then Add Remote Server. You can also open the settings file with the command palette action zed: open settings file. The key is context_servers.
{
"context_servers": {
"pear": {
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_PEAR_API_KEY"
}
}
}
}Replace the placeholder in that private settings file. Keep the Authorization header. If a remote server has no Authorization header, Zed prompts for OAuth, and Pear has not certified that flow. Leave tool approval on its default confirm setting so you can review each call.
A green indicator next to the server name means Zed considers the server active. That is a connection check, not a completed calendar read.
3. Verify a real tool result
In the Agent Panel, ask Zed 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 Zed 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 checking the URL and header in settings. A browser sign-in prompt means the Authorization header is missing. An unavailable provider calls for checking the connected account in Pear.
Revoke the key in Pear to end its access, then delete the pear context server or replace the header value. Do not commit the settings file while it contains a 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 26 September 2026. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Zed is still pending.
