# Hermes Agent + Pear MCP guide

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

Use the authentication method shown for each client surface.

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

Use Pear with Hermes Agent by adding Pear as a remote HTTP MCP server in `~/.hermes/config.yaml`.

## Environment-backed Bearer config

The recommended Pear path for Hermes uses `PEAR_API_KEY` from `~/.hermes/.env` or
Hermes's local secret/config flow. Keep the environment reference in
`config.yaml`; never write the key itself there.

```yaml
mcp_servers:
  pear:
    url: "https://pearmcp.com/api/mcp"
    headers:
      Authorization: "Bearer ${PEAR_API_KEY}"
    tools:
      prompts: false
      resources: false
```

After editing config, restart Hermes or run `/reload-mcp`.

Hermes prefixes remote MCP tools with the server name, so Pear tools appear with an
`mcp_pear_` prefix.

## Why bare OAuth is incompatible

Hermes's bare OAuth mode—`auth` set to `oauth`—attempts dynamic client registration
(DCR). Pear intentionally exposes no DCR endpoint, so that mode is incompatible; it
is not a fallback for the Bearer configuration 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).

## Use cases

- Use Hermes as a morning operator that summarizes calendar, mail, and tasks.
- Ask Hermes to turn a conversation into follow-up tasks and a calendar hold.
- Let Hermes search recent provider mail before drafting a customer or vendor response.