# Goose MCP setup for iCloud Calendar and Outlook

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

Use the authentication method shown for each client surface.

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

Use Pear tools from Goose with your connected iCloud or Microsoft 365 account. Goose Desktop and the Goose CLI share this extension config.

## 1. Prepare the account

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create an API key in Settings. Goose calls Pear over the network even when the model is configured locally.

## 2. Add a streamable HTTP extension

Open Goose Desktop settings, or run `goose configure`. You can also edit the private config file: `~/.config/goose/config.yaml` on macOS and Linux, or `%APPDATA%\Block\goose\config\config.yaml` on Windows. The extension type is `streamable_http` and the address field is `uri`.

```yaml
extensions:
  pear:
    type: streamable_http
    name: pear
    enabled: true
    uri: "https://pearmcp.com/api/mcp"
    headers:
      Authorization: "Bearer YOUR_PEAR_API_KEY"
    timeout: 300
```

Replace the placeholder only in that private file. Keep the `Bearer ` prefix. Goose's own config guide says to avoid leaving tokens in a shared `config.yaml`. `goose info -v` prints the header, so do not paste that output into a chat.

Set `GOOSE_MODE` to `approve` or `smart_approve` before you use Pear for mail or calendar changes. The default `auto` mode can run tools without a prompt.

## 3. Verify a real tool result

Ask Goose 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 `uri`, 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 remove the `pear` extension or replace the header value. Restart Goose after a direct edit to the config file.

## 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 Goose is still pending.

- [Official Goose configuration files](https://goose-docs.ai/docs/guides/config-files/)
- [HTML setup guide](https://pearmcp.com/guides/goose)