# Zed MCP setup for iCloud Calendar and Outlook

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

Use the authentication method shown for each client surface.

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

Use Pear tools from the Zed agent with your connected iCloud or Microsoft 365 account. Zed stores the header in your settings file.

## 1. Prepare the account

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create an API key in Settings. Zed sends header values exactly as written. Do not put the key in a repository.

## 2. Add a remote context server

Open Settings → AI → MCP Servers, choose Add Server, then Add Remote Server. You can also open the settings file with the command palette action `zed: open settings file`. The key is `context_servers`.

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

Replace the placeholder in that private settings file. Keep the `Authorization` header. If a remote server has no Authorization header, Zed prompts for OAuth, and Pear has not certified that flow. Leave tool approval on its default confirm setting so you can review each call.

A green indicator next to the server name means Zed considers the server active. That is a connection check, not a completed calendar read.

## 3. Verify a real tool result

In the Agent Panel, ask Zed 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 header in settings. 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 delete the `pear` context server or replace the header value. Do not commit the settings file while it contains a 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 Zed is still pending.

- [Official Zed MCP documentation](https://zed.dev/docs/ai/mcp)
- [HTML setup guide](https://pearmcp.com/guides/zed)