# Gemini CLI + Pear MCP guide

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

Use the authentication method shown for each client surface.

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

Add Pear to Gemini CLI as a Streamable HTTP MCP server for hosted calendar, task,
contact, and mail workflows.

Server URL:

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

## Setup

Gemini CLI accepts `httpUrl` and custom headers for remote servers. Pear's recommended
Gemini CLI path is this environment-backed API-key configuration:

```json
{
  "mcpServers": {
    "pear": {
      "httpUrl": "https://pearmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${PEAR_API_KEY}"
      }
    }
  }
}
```

Gemini CLI expands environment variables in settings strings. Set `PEAR_API_KEY` in an
environment source Gemini CLI loads, keep the interpolation above, and never commit a
substituted key to a shared project file.

Inspect the server registry and test a read-only 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).