1. Prepare the account
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings. Goose calls Pear over the network even when the model is configured locally.
2. Add a streamable HTTP extension
Open Goose Desktop settings, or run goose configure. You can also edit the private config file: ~/.config/goose/config.yaml on macOS and Linux, or %APPDATA%\Block\goose\config\config.yaml on Windows. The extension type is streamable_http and the address field is uri.
extensions:
pear:
type: streamable_http
name: pear
enabled: true
uri: "https://pearmcp.com/api/mcp"
headers:
Authorization: "Bearer YOUR_PEAR_API_KEY"
timeout: 300Replace the placeholder only in that private file. Keep the Bearer prefix. Goose's own config guide says to avoid leaving tokens in a shared config.yaml. goose info -v prints the header, so do not paste that output into a chat.
Set GOOSE_MODE to approve or smart_approve before you use Pear for mail or calendar changes. The default auto mode can run tools without a prompt.
3. Verify a real tool result
Ask Goose 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 Goose 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 uri, the header name, and that the value starts with Bearer . An unavailable provider calls for checking the connected account in Pear.
Revoke the key in Pear to end its access, then remove the pear extension or replace the header value. Restart Goose after a direct edit to the config file.
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 Goose is still pending.
