Connect Hermes Agent to Pear MCP

1. Create your Pear account

Sign up at pearmcp.com, then connect Apple iCloud or Microsoft 365. Pear's recommended Hermes path is an environment-backed API key sent in a Bearer header.

Apple Reminders compatibility

Apple Reminders availability depends on the Apple account. For Apple, Pear can read and write only the legacy reminder lists Apple still exposes through CalDAV. If the account has been upgraded to Apple's newer Reminders store, Pear cannot access those native lists and does not copy them into a separate reminder store. Apple may instead return compatibility placeholders, such as repeated "Where are my reminders?" items; Pear did not create them. Pear's safe fallback hides known placeholders and blocks writes to affected lists. Reconnecting iCloud or replacing the App-Specific Password will not change this Apple limitation. Calendar, Contacts, and Mail are unaffected, and Microsoft To Do uses Microsoft Graph and is unaffected. Full modern Apple Reminders access would require an Apple-platform companion using EventKit with the user's permission; Pear does not currently provide one.

2. Add Pear to Hermes MCP config

Hermes reads MCP servers from ~/.hermes/config.yamlunder mcp_servers. Its official MCP docs show local stdio servers and remote HTTP servers in the same config. Keep the key inPEAR_API_KEY and add this remote server entry:

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

Hermes resolves ${VAR} placeholders in remote URLs and headers from the environment, including values placed in~/.hermes/.env. Theprompts andresources settings keep Hermes focused on Pear's callable tools instead of optional prompt/resource wrappers.

Why bare OAuth is incompatible

Do not configure Hermes with its bare OAuth setting, where authis set to oauth. Hermes currently uses dynamic client registration for that path, and Pear does not expose a DCR endpoint. It therefore fails before sign-in rather than serving as a fallback to the Bearer configuration above.

3. Reload and test Pear

After adding the Bearer configuration, restart Hermes or run/reload-mcp. Hermes prefixes tools with the server name, so Pear tools appear with an mcp_pear_ prefix. Begin with a read-only provider-status request before trying write actions.

• What is on my calendar today?
• Create Microsoft To Do tasks from these notes, or first confirm Apple exposes a usable legacy CalDAV reminder list.
• Find a free time for a follow-up call next week.
• Search recent mail from this customer and summarize the thread.

What Pear unlocks inside Hermes

• Give Hermes Calendar, Contacts, Mail, Microsoft To Do, and legacy Apple CalDAV reminder tools through remote MCP.
• Use Apple iCloud and Microsoft 365 provider workflows from the same Pear endpoint.
• Filter prompts/resources while keeping Pear's action tools available.
• Reload MCP config without rebuilding a local tool server.

Hermes workflows worth testing

• Use Hermes as a morning operator: summarize calendar, mail, and tasks into a planning note.
• 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.