# Kiro IDE MCP setup for iCloud and Microsoft 365

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

Use the authentication method shown for each client surface.

| Client surface | Authentication | Setup guide |
| --- | --- | --- |
| Kiro IDE | API key via environment | Setup guide available |
<!-- MCP_HOST_COMPATIBILITY:END -->

Set up Pear in Kiro IDE with remote MCP and an approved API-key environment variable. Includes provider checks and troubleshooting.

## 1. Prepare a personal Pear connection


Sign in to Pear and connect Apple iCloud or Microsoft 365. Copy a Pear API key from Settings and make PEAR_API_KEY available to the process that starts Kiro IDE. A terminal environment and a desktop launcher can load different variables.



## 2. Open the user MCP configuration


In Kiro IDE, open the Command Palette and choose Kiro: Open user MCP config (JSON). Add this entry inside mcpServers while keeping your existing servers.


```json
{
  "mcpServers": {
    "pear": {
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer ${PEAR_API_KEY}"
},
"disabled": false,
"autoApprove": []
    }
  }
}
```


Approve PEAR_API_KEY when Kiro requests environment-variable access. You can review it in the Mcp Approved Env Vars setting. Keep the variable reference in the file and leave autoApprove empty while checking the connection.



## 3. Inspect Pear in the MCP panel


Open Kiro's MCP servers panel, check the connection, and ask it to call pear_provider_status. Review which provider services are ready before trying a calendar or mail request. Kiro's tool permissions and your Pear account both affect which actions are available.



## Kiro IDE and Kiro Web have different support


This guide covers the IDE. Kiro's current documentation does not list remote MCP support for Kiro Web or mobile. A local command configuration is also different from Pear's hosted HTTP endpoint.


If authentication fails, check both the launch environment and the approved-variable setting. If Kiro tries to register an OAuth client automatically, return to the documented Bearer-header configuration. Pear does not expose dynamic client registration.


## 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 Kiro IDE.

- [Official Kiro IDE documentation](https://kiro.dev/docs/mcp/configuration/)
- [Kiro support by surface](https://kiro.dev/docs/mcp/)