# Continue + Pear MCP guide

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

Use the authentication method shown for each client surface.

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

Add Pear to Continue as a remote `streamable-http` server. Use an API key for this
configuration path.

Server URL:

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

## Setup

Store `PEAR_API_KEY=pear_sk_...` in a local `.env`, `.continue/.env`, or
`~/.continue/.env`, then use Continue's secret interpolation so a real Pear API key
stays out of shared configuration:

```yaml
name: Pear MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: Pear
    type: streamable-http
    url: https://pearmcp.com/api/mcp
    requestOptions:
      headers:
        Authorization: Bearer ${{ secrets.PEAR_API_KEY }}
```

Reload Continue after changing configuration. Confirm Pear tools appear, test a
read-only request first, and rotate the key if it is ever pasted into a shared file.

## 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).