1. Prepare a personal connection
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings. Use a private AnythingLLM installation for your personal key. On a shared deployment, establish which users can invoke the server before adding personal account access.
Choose an agent model with reliable tool support. A local model still needs network access to Pear, and provider data returned by tools becomes available to the selected model.
2. Set the Streamable HTTP transport explicitly
Open Agent Skills, then edit plugins/anythingllm_mcp_servers.json inside your AnythingLLM storage directory. Add pear to the existing mcpServers object.
{
"mcpServers": {
"pear": {
"type": "streamable",
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_PEAR_API_KEY"
}
}
}
}Keep type: "streamable": AnythingLLM assumes SSE for remote entries when the type is omitted. Replace the key placeholder only in your private local configuration, and protect both that file and its backups. Do not add a local command to this remote server entry.
3. Refresh Agent Skills and inspect Pear
Use Refresh on the Agent Skills page to reload the configuration. Select Pear, check its status, and inspect the available tools. If it fails to start, inspect the server error before asking the model to use it.
In an agent conversation, ask it to call pear_provider_status and report the connected account and ready services. Then read a known calendar event. If tools are listed but never called, check the selected agent model and its context capacity.
Use an agent for a focused workflow
Try: “Find the meeting with my project team this Friday. Show the time and attendees, then preview a follow-up email for approval.” Confirm the sending account, recipients, and content before approving a write through Pear.
AnythingLLM Desktop documents MCP tool support. This guide uses those tools and does not depend on MCP resources, prompts, or sampling.
Fix transport errors and remove credentials
For a transport error, check type and url first. For an authentication error, check the full Bearer header and active key in Pear. If a provider is unavailable, reconnect or repair that account in Pear before retrying its tools.
Revoke the key in Pear to end access, remove the local server entry, and refresh Agent Skills. If you replace a key, update the private file before reconnecting. Check error logs without publishing the 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 AnythingLLM is still pending.
