# Roo Code MCP setup for iCloud Calendar and Outlook

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

Use the authentication method shown for each client surface.

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

Use Pear tools from Roo Code with your connected iCloud or Microsoft 365 account. The type value must be `streamable-http`.

## 1. Prepare the account

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create an API key in Settings.

## 2. Add Pear in MCP Servers

Open the Roo Code pane, then the gear icon, then MCP Servers. Choose Edit Global MCP so the key stays in your private user config, or Edit Project MCP only for a file you will not commit.

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

The `type` must be `streamable-http`, with the hyphen. Roo Code uses a `headers` object for authentication tokens. Keep the `Bearer ` prefix. Do not leave `alwaysAllow` turned on for Pear write tools.

## 3. Verify a real tool result

Ask Roo Code 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

A connection failure often means `type` is `http` or missing. For authentication errors, check the `Bearer ` prefix. For provider errors, check the connected account in Pear.

Revoke the API key in Pear to end access, then delete the `pear` server 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 26 September 2026. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Roo Code is still pending.

- [Official Roo Code MCP setup](https://docs.roocode.com/features/mcp/using-mcp-in-roo)
- [HTML setup guide](https://pearmcp.com/guides/roo-code)