Connect VS Code and GitHub Copilot to Pear MCP

1. Prepare Pear

Create a Pear account, connect Apple iCloud or Microsoft 365, and keep your Pear endpoint handy. This VS Code setup uses an environment-backed API key as a Bearer token so the credential stays out of source control.

Apple Reminders compatibility

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.

2. Add Pear as an MCP server

VS Code's Copilot MCP docs support adding MCP servers through the UI or workspace/user configuration. For a checked-in workspace config, use a server entry like this and place the token in an environment variable rather than committing it.

{
  "servers": {
    "pear": {
      "type": "http",
      "url": "https://pearmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PEAR_API_KEY}"
      }
    }
  }
}

3. Verify from Copilot Chat

• Ask Copilot to list available Pear tools and confirm the server is enabled.
• Start with a read-only request such as checking today's calendar.
• Move to action prompts after you confirm the right provider account is connected.
• Keep the Pear API key in your local environment or secret store.