# Poke + Pear MCP guide

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

Use the authentication method shown for each client surface.

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

Use Pear with Poke by adding Pear as a custom MCP integration with a Pear API key.

Server URL:

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

Authentication:

```text
Authorization: Bearer YOUR_PEAR_API_KEY
```

Poke also documents automatic DCR and a hosted static recipe that requires a client
ID and client secret. Pear intentionally exposes neither open DCR nor a confidential
client secret. Do not paste a Pear API key into either OAuth field; keep Pear on the
API-key path.

Apple reminder access is limited to the legacy reminder data Apple still exposes
through CalDAV. Pear's hosted CalDAV connection cannot access Apple's upgraded
Reminders store. Microsoft To Do uses Microsoft Graph and is unaffected. See the
[Apple Reminders compatibility note](./apple-reminders-compatibility.md).

Use cases:

- Chat with live Calendar, Tasks/Reminders, Contacts, and Mail context.
- Ask Poke to capture follow-ups in Microsoft To Do or a usable legacy Apple CalDAV
  reminder list.
- Check availability and prepare meeting context from one thread.