# Amp MCP setup for iCloud Calendar and Outlook

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

Use the authentication method shown for each client surface.

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

Use Pear tools from Amp with your connected iCloud or Microsoft 365 account. Keep the Pear key in the environment Amp already substitutes.

## 1. Prepare the account

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create an API key in Settings. Make `PEAR_API_KEY` available to the Amp process through your local environment or secret store.

## 2. Add a remote server with a header

Add Pear under `amp.mcpServers`. Amp documents `${VAR_NAME}` substitution in header values. Include the Authorization header so Amp uses that value.

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

A remote URL with no Authorization header can start Amp's browser sign-in. Pear has not certified an Amp OAuth client, so keep the header in place. Do not paste the expanded key into an Amp thread.

## 3. Verify a real tool result

Ask Amp to call `pear_provider_status` and name the ready services for the expected account. Then find a known calendar event in a narrow date range and your timezone. Inspect the actual tool response: describing a proposed calendar check is not a completed read.

After the read, try: “Find tomorrow's planning meeting and summarize its time and attendees. Then preview a follow-up email for me to review; do not send it.” Review the draft, recipients, and sending account before approving a write through Pear.

## Troubleshooting and revocation

For authentication errors, check the URL and that `PEAR_API_KEY` is present in the Amp process. A browser sign-in prompt means the Authorization header is missing. For provider errors, check the connected account in Pear.

Revoke the API key in Pear to end access, then remove the `pear` server or point the environment variable at a replacement key.

## Provider limits and next steps

Tools depend on your connected provider, account permissions, and client settings. Start with a read, then inspect a preview before approving writes.

- [iCloud setup](https://pearmcp.com/icloud-mcp-server)
- [iCloud Mail](https://pearmcp.com/ai-icloud-mail)
- [Microsoft 365 setup](https://pearmcp.com/microsoft-365-mcp-server)
- [Outlook Mail](https://pearmcp.com/outlook-mail-mcp)
- [Microsoft To Do](https://pearmcp.com/microsoft-to-do-mcp)
- [Data handling](https://pearmcp.com/data-handling)
- [Plans](https://pearmcp.com/pricing)

Pear's hosted CalDAV connection cannot access Apple's upgraded Reminders store. Only legacy reminder data still exposed through CalDAV is available; reconnecting cannot change this limit. Microsoft To Do is unaffected. Google Workspace is coming soon.

## Sources and compatibility status

Documentation checked on 26 September 2026. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Amp is still pending.

- [Official Amp MCP configuration](https://ampcode.com/docs/customize/mcp)
- [HTML setup guide](https://pearmcp.com/guides/amp)