# Trae MCP setup for iCloud Calendar and Outlook

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

Use the authentication method shown for each client surface.

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

Use Pear tools from Trae with your connected iCloud or Microsoft 365 account and a static private header.

## 1. Prepare the account

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create an API key in Settings. This setup uses the static header you enter, without browser sign-in. It does not refresh an expired token; replace or revoke the key in Pear when needed.

## 2. Add Pear manually

In TraeCode, open Settings → MCP → Add → Add Manually. In TraeWork, open your avatar → Settings → MCP, then Create → Create Manually; choose the Local runtime in TraeWork Desktop for a personal key. Paste this configuration into private settings, replace the placeholder with your Pear key, and confirm. Do not add a personal key to a shared or project-level server.

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

Keep the `Bearer ` prefix. Do not commit this file or paste the completed header into a chat. If the key is revoked, edit the header yourself. These instructions cover the documented static-header path. Pear authentication through other Trae paths remains unverified.

## 3. Verify a real tool result

Ask Trae 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, the header name, and that the value starts with `Bearer `. For provider errors, check the connected account in Pear.

Revoke the API key in Pear to end access, then delete the Trae server entry or replace the header value.

## 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 4 October 2026. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Trae is still pending.

- [Official TraeCode MCP settings](https://docs.trae.ai/ide/add-mcp-servers)
- [Official TraeWork MCP servers](https://docs.trae.ai/solo/remote-mcp-server)
- [HTML setup guide](https://pearmcp.com/guides/trae)