Availability: extension shut down
The official repository states that the Roo Code extension was shut down on May 15. Its published MCP documentation remains available for existing installations. For a current alternative, see the Cline guide. This page does not establish Pear support in community forks or Roomote.
1. Existing-install prerequisites
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings.
2. Add Pear in MCP Servers
In an existing installation, open MCP Servers from the top of the Roo Code pane, scroll to the bottom, and choose Edit Global MCP. Merge the server into the existing object. Keep credentials out of the project’s .roo/mcp.json; a matching project entry overrides the global entry.
Roo Code v3.54.0 supports the environment reference below. Set PEAR_API_KEY privately in the environment that starts your editor, then restart the editor so the extension inherits it.
{
"mcpServers": {
"pear": {
"type": "streamable-http",
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:PEAR_API_KEY}"
}
}
}
}The type must be streamable-http, with the hyphen. Roo Code uses a headers object for authentication tokens. Keep the Bearer prefix. Do not leave alwaysAllow turned on for Pear write tools.
3. Verify a real tool result
Ask Roo Code 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 Roo Code 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
A connection failure often means type is http or missing. An authentication error calls for the Bearer prefix. An unavailable provider calls for checking the connected account in Pear.
Revoke the key in Pear to end its access, then delete the pear server or replace the header value.
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. Historical setup reference only; a complete Pear authentication, tool-list, read, and approved-write test in Roo Code has not been completed.
