1. Connect your provider in Pear
Sign in to Pear, connect the iCloud or Microsoft 365 account you want to use, and create a Pear API key in Settings. Load a model that can use tools in LM Studio.
The model can run locally while Pear supplies remote tools. Using the hosted endpoint still requires internet access and sends requests to Pear; tool results are made available to your selected model.
2. Edit LM Studio's mcp.json
Open the Program tab in the right sidebar, then choose Install → Edit mcp.json. Merge the pear entry into the existing mcpServers object without replacing your other servers.
{
"mcpServers": {
"pear": {
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_PEAR_API_KEY"
}
}
}
}Replace YOUR_PEAR_API_KEY only inside your private local app configuration. This is a literal Bearer header. Keep the completed file out of shared presets, repositories, screenshots, and chats.
3. Check tools and provider readiness
Save the configuration and confirm Pear's tools are available in LM Studio. Ask the model to call pear_provider_status, then read one known calendar event or message from the expected account.
Use a small request with an exact date range or search term. Inspect the tool result rather than accepting an unsupported answer. A model that cannot reliably select tools or form valid arguments needs attention even when MCP itself connects.
Keep the first task small
Try: “Find the planning event on my work calendar next Tuesday and show its start time in my timezone. Preview a task to prepare for it, then wait for approval.” Check the selected account and proposed details before allowing a write.
LM Studio warns that large tool definitions can consume a local model's context. If a conversation overflows or tool selection degrades, reduce the number of active servers, shorten the conversation, or choose a model with suitable tool support and context capacity.
Troubleshooting and revocation
If tools are missing, check that the entry is inside mcpServers, with the exact url and a valid JSON structure. If authentication fails, check the literal header and the key's status in Pear. Provider readiness errors should be resolved in Pear before retrying the task.
Revoke the API key in Pear when removing access or after accidental disclosure. Remove the local entry, or replace its key and reconnect. Deleting the file entry alone does not revoke a copied credential.
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 LM Studio is still pending.
