1. Prepare the account
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings. Junie CLI uses the same JSON shape as Junie in JetBrains IDEs.
2. Add Pear in the user-scope file
Put this server in ~/.junie/mcp/mcp.json. That user-scope file stays on your machine. A project file at .junie/mcp/mcp.json can be committed, so leave the key out of it.
{
"mcpServers": {
"pear": {
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_PEAR_API_KEY"
}
}
}
}Replace the placeholder in the user-scope file. Keep the Bearer prefix. Run /mcp in Junie CLI and confirm the server is listed. Junie's browser Authorize action is for remote servers that require OAuth. This Pear path uses the header instead.
The Junie IDE plugin page says it does not store security tokens in MCP configs for its local-server examples. Use the user-scope file above, and do not commit a copy that contains the key.
3. Verify a real tool result
Ask Junie 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 Junie 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 the Bearer prefix in the user-scope file. An Authorization required status means Junie is waiting on OAuth. This path uses the header instead. 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 from ~/.junie/mcp/mcp.json 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 26 September 2026. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Junie is still pending.
