# Junie MCP setup for iCloud Calendar and Outlook

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

Use the authentication method shown for each client surface.

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

Use Pear tools from Junie CLI with your connected iCloud or Microsoft 365 account. Store the key in the user-scope config, not in a committed project 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. Junie CLI uses the same JSON shape as Junie in JetBrains IDEs.

## 2. Add Pear in the user-scope file

Put this server in `~/.junie/mcp/mcp.json`. That user-scope file stays on your machine. A project file at `.junie/mcp/mcp.json` can be committed, so leave the key out of it.

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

Replace the placeholder in the user-scope file. Keep the `Bearer ` prefix. Run `/mcp` in Junie CLI and confirm the server is listed. Junie's browser Authorize action is for remote servers that require OAuth. This Pear path uses the header instead.

The Junie IDE plugin page says it does not store security tokens in MCP configs for its local-server examples. Use the user-scope file above, and do not commit a copy that contains the key.

## 3. Verify a real tool result

Ask Junie 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 the `Bearer ` prefix in the user-scope file. An Authorization required status means Junie is waiting on OAuth. This path uses the header instead. For provider errors, check the connected account in Pear.

Revoke the API key in Pear to end access, then delete the `pear` server from `~/.junie/mcp/mcp.json` 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 Junie is still pending.

- [Official Junie CLI MCP configuration](https://junie.jetbrains.com/docs/junie-cli-mcp-configuration.html)
- [HTML setup guide](https://pearmcp.com/guides/junie)