# Jan Desktop MCP setup for iCloud Calendar and Outlook

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

Use the authentication method shown for each client surface.

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

Use Pear tools from Jan Desktop with your connected iCloud or Microsoft 365 account and a model that can call tools.

## 1. Prepare the account and model

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create an API key in Settings. Choose a model with tool-calling support in Jan. A successful server connection does not establish that a model can use the tools reliably.

This workflow requires network access even with a local model. Requests go to Pear's hosted endpoint, and returned calendar or mail data becomes context for your selected model.

## 2. Add Pear in MCP Servers

Open Settings → MCP Servers → Add MCP Server. Choose `HTTP`, Jan's Streamable HTTP transport, and configure:

```text
Transport: HTTP
URL: https://pearmcp.com/api/mcp
Header name: Authorization
Header value: Bearer YOUR_PEAR_API_KEY
```

Replace the placeholder only in your private local Jan configuration. An explicit `Authorization` header is used as-is and suppresses OAuth for that server. Keep the `Bearer ` prefix. Do not paste the key into a conversation or share the completed configuration.

Enable the server and check for the green active indicator. Leave Allow All MCP Tool Permissions off so you can review requests.

## 3. Verify a real tool result

Ask Jan 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.

If tools are not called, check the selected model's tool support and that Pear is enabled. 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 endpoint, header, and active key. For provider errors, check the connected account in Pear. Missing or unreliable tool calls after a successful connection may be a model or permissions issue.

Revoke the API key in Pear to end access, then remove the Jan server or replace its key. Jan's Clear authentication action concerns OAuth tokens; it does not revoke an API key in a header.

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

- [Official Jan Desktop MCP settings and authentication](https://www.jan.ai/docs/desktop/integrations/mcp-servers)
- [HTML setup guide](https://pearmcp.com/guides/jan)