# LM Studio MCP setup for iCloud and Microsoft 365

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

Use the authentication method shown for each client surface.

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

Add Pear as a remote MCP server in LM Studio, then use a tool-capable model with your connected iCloud or Microsoft 365 calendar, mail, and contacts.

## 1. Prepare Pear and your model

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create an API key in Settings. Load a model with tool support in LM Studio. A local model still needs internet access for Pear's hosted endpoint; tool results become available to the selected model.

## 2. Edit mcp.json

Open the Program tab in the right sidebar, then Install → Edit mcp.json. Merge the `pear` entry into the existing `mcpServers` object without replacing your other servers.

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

Replace `YOUR_PEAR_API_KEY` only in your private local app configuration. This is a literal Bearer header. Keep the completed file out of shared presets, repositories, screenshots, and chats.

## 3. Check tools and provider readiness

Save and confirm Pear's tools are available. Ask the model to call `pear_provider_status`, then read one known event or message from the expected account. Use a narrow date range or search term and inspect the tool response.

If the model cannot select the tool or form valid arguments, resolve that separately from connection problems. LM Studio warns that tool definitions can consume substantial context. Reduce active servers, shorten the conversation, or select a model with suitable tool support and context capacity if requests overflow or become unreliable.

## A useful first workflow

Try: “Find the planning event on my work calendar next Tuesday and show its start time in my timezone. Preview a task to prepare for it, then wait for approval.” Review the account and proposed details before allowing a write through Pear.

## Troubleshooting and removal

Missing tools: check that the entry is inside `mcpServers` and the JSON and `url` are correct. Authentication errors: check the literal header and active key in Pear. Provider readiness errors: resolve the connected account in Pear before retrying.

Revoke the API key in Pear after disclosure or when ending access. Remove the local entry or replace its key and reconnect. Deleting a server entry does not revoke a copied key.

## Provider limits and next steps

Available 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 LM Studio is still pending.

- [Official LM Studio MCP configuration and troubleshooting](https://lmstudio.ai/docs/app/mcp)
- [HTML setup guide](https://pearmcp.com/guides/lm-studio)