1. Prepare the account and model
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings. Choose a model in Jan that supports tool calling; a server connection and a model's ability to use its tools are separate checks.
Running a model locally does not make this an offline workflow. Requests go to Pear's hosted endpoint, and returned calendar or mail data becomes context for the model you select.
2. Add Pear in MCP Servers
Open Settings → MCP Servers → Add MCP Server. Choose HTTP, which Jan uses for Streamable HTTP, and enter the following endpoint and custom header.
Transport: HTTP
URL: https://pearmcp.com/api/mcp
Header name: Authorization
Header value: Bearer YOUR_PEAR_API_KEYReplace the placeholder in your private local Jan configuration with your Pear key. Jan sends an explicit Authorization header as-is and does not attempt OAuth for that server. Keep the Bearer prefix; do not paste the key into a conversation or a shared configuration.
Enable the server. Jan displays an active connection with a green indicator. Leave Allow All MCP Tool Permissions off so you can review tool requests.
3. Verify a real tool result
Ask Jan 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 Jan only describes how it would check your calendar, the read has not happened. Confirm the selected model can call tools and that the Pear server remains enabled.
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 endpoint, header, and key in Jan. An unavailable provider calls for checking the connected account in Pear. Missing or unreliable tool calls after a successful connection can instead be a model capability or permissions issue.
For this API-key setup, revoke the key in Pear to end its access, then remove the Jan server entry or update it with a replacement key. Jan's Clear authentication action concerns stored OAuth tokens; it does not revoke a Pear API key supplied in a header.
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 Jan Desktop is still pending.
