1. Prepare your Pear account
Sign in to Pear, connect iCloud or Microsoft 365, and create a personal Pear API key in Settings. Select only the provider permissions you need.
This guide covers the QoderWork desktop app and its custom MCP connector. Qoder CLI has a separate configuration. QoderWork built-in Microsoft 365 and native macOS connectors are separate from Pear and do not change Pear provider limits.
2. Add a private remote MCP connection
In QoderWork, open Extensions → Connectors → + Add → Paste JSON Config. Paste the configuration below, replace the placeholder privately, and click Import. Use your personal app configuration, not a shared project or a published connector template.
{
"mcpServers": {
"pear": {
"type": "streamable-http",
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_PEAR_API_KEY"
}
}
}
}Alternatively, choose Fill in Config Manually, select Streamable HTTP, name the server Pear, and enter the endpoint plus the Authorization header. The JSON form uses type: "streamable-http".
Replace YOUR_PEAR_API_KEY only in your private configuration. This example stores a literal secret: do not paste it into chat, shell commands or shell history, screenshots, shared settings, or a committed file. It does not promise encrypted local header storage or environment expansion.
3. Verify access with a bounded read
Under Connectors → Installed → Custom, enable Pear and expand it to inspect its tools. Start a new conversation after changing connector availability.
Ask the agent to call pear_provider_status. Confirm the expected provider, account, and ready services. Then read one known event from a named calendar within an explicit date range and timezone. Compare the result with your calendar.
Keep client tool approvals enabled. For a change, request a draft through pear_draft_write, inspect the exact account, recipients, dates, and content, and approve only that action before pear_execute_approved_write. Check the receipt and provider result. A successful read does not prove writes work.
Try a small planning task
“Read my work calendar for tomorrow in my timezone and help me plan two focus blocks. Show the proposal before creating anything.”
Expand the workflow only after the account and first result match your expectations. Available tools depend on connected providers, scopes, plan, and client policy. Pear Free includes 50 counted provider actions per month; check current plans for your needs.
Troubleshooting and removing access
If tools are missing, check that Pear is enabled and start a new conversation. Check the Streamable HTTP type and complete endpoint; this custom connector does not require a Pear marketplace listing.
For authentication failures, check the complete Bearer prefix and the active key in Pear. For unavailable services, repair the provider connection in Pear. An OAuth login prompt is not proof this API-key setup has connected.
To remove access, revoke the API key in Pear and delete the local Pear server entry. Removing the entry alone does not revoke a copied key. Revoke an exposed key before replacing it, and update any other clients that used that key.
Pear receives structured tool calls rather than your full chat transcript. Tool results enter the AI client and are subject to its data policies. Review Pear data handling before sharing sensitive provider data.
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; authenticated Pear testing in QoderWork, including authentication, tool discovery, a read, an approved write, and revocation, remains pending. This guide is not an official marketplace listing or an endorsement by the client vendor.
