1. Connect Pear and check your organization policy
Connect Apple iCloud or Microsoft 365 in Pear, then copy your Pear API key from Settings. Your GitHub organization can restrict MCP servers through a registry or allowlist. Confirm Pear is permitted before configuring the CLI.
This guide is for the Copilot terminal application. For editor setup, use the VS Code and Copilot guide.
2. Add a private HTTP server
Start Copilot CLI and enter /mcp add. Name the server pear, select HTTP, and enter the Pear URL below. HTTP selects Streamable HTTP. Do not select legacy SSE.
https://pearmcp.com/api/mcpIn the HTTP Headers field, add an Authorization header whose value is Bearer followed by a space and your Pear API key. Enter the key only in the private configuration form, not in chat or a shared repository.
For the first check, set Tools to pear_provider_status. Save with Ctrl+S. Copilot stores the personal server in ~/.copilot/mcp-config.json. This contains your credential; keep it private and do not commit it.
3. Verify the provider, then choose tools
Use /mcp list and ask Copilot to call pear_provider_status. After checking the result, use /mcp edit pear to allow the specific read tools you need. See the Pear tool reference for their names.
Keep normal tool approvals enabled. Adding a server does not require granting Copilot unrestricted tool, filesystem, or URL access.
If the server or tools are missing
Check the HTTP selection, the full /api/mcp URL, and the Authorization header. A connected server with only pear_provider_status is expected with the initial tool filter. If an organization policy blocks Pear, an administrator must review the allowlist.
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 9 September 2026. This page documents configuration and requirements. It does not certify a completed Pear connection in GitHub Copilot CLI.
