# GitHub Copilot CLI MCP setup for iCloud and Microsoft 365

<!-- MCP_HOST_IDS: github-copilot-cli -->
<!-- MCP_HOST_COMPATIBILITY:START -->
## Connection and authentication

Use the authentication method shown for each client surface.

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

Add Pear to GitHub Copilot CLI with a private HTTP configuration for iCloud and Microsoft 365. Includes tool filters and setup checks.

## 1. Connect Pear and check your organization policy


Connect Apple iCloud or Microsoft 365 in Pear, then copy your Pear API key from Settings. Your GitHub organization can restrict MCP servers through a registry or allowlist. Confirm Pear is permitted before configuring the CLI.


This guide is for the Copilot terminal application. For editor setup, use the [VS Code and Copilot guide](https://pearmcp.com/guides/vscode-copilot).



## 2. Add a private HTTP server


Start Copilot CLI and enter /mcp add. Name the server pear, select HTTP, and enter the Pear URL below. HTTP selects Streamable HTTP. Do not select legacy SSE.


```text
https://pearmcp.com/api/mcp
```


In the HTTP Headers field, add an Authorization header whose value is Bearer followed by a space and your Pear API key. Enter the key only in the private configuration form, not in chat or a shared repository.


For the first check, set Tools to pear_provider_status. Save with Ctrl+S. Copilot stores the personal server in ~/.copilot/mcp-config.json. This contains your credential; keep it private and do not commit it.



## 3. Verify the provider, then choose tools


Use /mcp list and ask Copilot to call pear_provider_status. After checking the result, use /mcp edit pear to allow the specific read tools you need. See the [Pear tool reference](https://pearmcp.com/mcp-tools) for their names.


Keep normal tool approvals enabled. Adding a server does not require granting Copilot unrestricted tool, filesystem, or URL access.



## If the server or tools are missing


Check the HTTP selection, the full /api/mcp URL, and the Authorization header. A connected server with only pear_provider_status is expected with the initial tool filter. If an organization policy blocks Pear, an administrator must review the allowlist.


## Provider limits and next steps

Start with a read such as provider status, a known event, or a known message. Specify the account and timezone. Available tools depend on the connected provider, account, and client permissions.

- [iCloud setup](https://pearmcp.com/icloud-mcp-server)
- [iCloud Mail](https://pearmcp.com/ai-icloud-mail)
- [Microsoft 365](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. It can use only the legacy reminder data Apple still exposes through CalDAV. Reconnecting cannot change this limit. Microsoft To Do is unaffected. Google Workspace is coming soon.

Review recipients, dates, and content before approving writes. Pear exposes permitted tools; the AI client controls when it calls them.

## Sources and status

Documentation checked on 9 September 2026. Setup guidance is not proof of a completed Pear connection in GitHub Copilot CLI.

- [Official GitHub Copilot CLI documentation](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers)