# VS Code + GitHub Copilot + Pear MCP guide

<!-- MCP_HOST_IDS: vscode-copilot -->
<!-- MCP_HOST_COMPATIBILITY:START -->
## Connection and authentication

Use the authentication method shown for each client surface.

| Client surface | Authentication | Setup guide |
| --- | --- | --- |
| VS Code Copilot | API key via environment | Setup guide available |
<!-- MCP_HOST_COMPATIBILITY:END -->

Add Pear as an HTTP MCP server in VS Code so Copilot agent workflows can use the
provider accounts connected to Pear.

Server URL:

```text
https://pearmcp.com/api/mcp
```

## Setup

VS Code supports remote HTTP MCP servers and secure input or environment variables.
Pear's recommended VS Code setup is this environment-backed Bearer configuration:

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

Keep the key outside checked-in workspace files. Confirm Pear is enabled in Copilot
Chat and begin with a read-only provider-status or calendar request through the
API-key path above.

## Apple Reminders compatibility

Pear's hosted CalDAV connection cannot access Apple's upgraded Reminders store. It can
use only the legacy reminder data Apple still exposes through CalDAV. Reconnecting
iCloud or replacing the App-Specific Password cannot change that protocol limit.
Microsoft To Do uses Microsoft Graph and is unaffected. See the
[Apple Reminders compatibility note](./apple-reminders-compatibility.md).