Skip to content

VS Code + Copilot client guide

Connect VS Code and GitHub Copilot to Pear MCP

Add Pear to VS Code MCP configuration and keep the API key in your local environment.

Connection details

The values VS Code + Copilot asks for first.

Pear hosted endpointhttps://pearmcp.com/api/mcp
Authentication
Bearer API key
Setup surface
.vscode/mcp.json
Quick setupVS Code MCPAPI keyHTTP MCP

VS Code documents MCP servers in workspace/user mcp.json and Command Palette flows.

Setup guide availableOfficial setup reference
Get ready

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.

Start Free

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.

Read the Apple Reminders compatibility note
Make the connection

2. Add Pear as an MCP server

Open MCP: Open Workspace Folder MCP Configuration for.vscode/mcp.json, or MCP: Open User Configuration for your user profile. This example uses the VS Code servers format; the portable Copilot .mcp.json format instead uses mcpServers. Make PEAR_API_KEY available to the VS Code process. A remote window resolves variables in its remote environment. Keep the token outside committed files.

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

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.

Sources and verification status

Use Copilot agent tools with Pear enabled, and review workspace trust and your organization's MCP policy. This guide documents configuration, not a completed authenticated Pear test. Checked on 17 October 2026 against the VS Code MCP reference and variable reference.

Related guides
All guides
VS Code + Copilot + Pear

Put VS Code + Copilot to work across your providers.

Free includes 50 counted provider actions/month. Most provider reads or writes count as one action. Batch writes count once per item. Setup and discovery do not count. Failed actions Pear can confirm had no provider effect also do not count; actions with an unknown outcome may count. Pro removes the cap.