1. Prepare your Pear account
Sign in to Pear, connect iCloud or Microsoft 365, and create a Pear API key in Settings. The key grants access to the services and permissions available to your Pear account.
This setup is for Antigravity IDE's custom MCP configuration. It does not require Pear to appear in the MCP Store.
2. Open the personal MCP configuration
In the agent side panel, open the three-dot menu, choose MCP Servers, then Manage MCP Servers and View raw config. Use the global ~/.gemini/config/mcp_config.json file for this personal credential, keeping it outside a shared project.
Add pear inside the existing mcpServers object. Preserve any servers already configured.
{
"mcpServers": {
"pear": {
"serverUrl": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_PEAR_API_KEY"
}
}
}
}Replace YOUR_PEAR_API_KEY only in your private local file. Antigravity expects serverUrl for remote servers; url and httpUrl are not substitutes. The header contains the literal key, so do not commit or share this file.
3. Check account access before using tools
Check Pear in the MCP server panel and ask the agent to call pear_provider_status. Confirm the expected account and ready services, then request one known calendar event with an explicit date range and timezone.
Keep tool approvals enabled while checking the connection. For a change, ask for a preview first, inspect the exact account, recipients or event details, and approve only the intended write. A successful read does not establish that writes are ready.
Use personal context while planning work
Try: “Check my work calendar for tomorrow in my timezone and suggest a free hour for this release review. Don't create an event yet.” Once the result matches your calendar, you can decide whether to request an event draft.
Connection errors and key removal
If Pear is absent, check the JSON and the serverUrl field. For an authentication error, check the full Bearer prefix and that the API key is still active. This guide uses the custom-header route; an OAuth registration prompt is not a completed Pear connection.
If the provider status reports an unavailable service, resolve that connection in Pear before retrying the action. To remove access, revoke the API key in Pear and remove its local server entry. Revoke an exposed key before replacing it.
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 Antigravity IDE is still pending.
