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.
{
"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.
Choose a useful first workflow
Start with a read. Ask which calendars are connected, find an event in a specific date range, or search a mail folder for a message you already know. Specify the account and timezone when they matter.
For Apple accounts, see iCloud setup and services and iCloud Mail workflows. For Microsoft accounts, see Microsoft 365 setup, Outlook Mail, and Microsoft To Do.
Apple Reminders availability depends on the Apple account. For Apple, Pear can read and write only the legacy reminder lists Apple still exposes through CalDAV. If the account has been upgraded to Apple's newer Reminders store, Pear cannot access those native lists and does not copy them into a separate reminder store. Apple may instead return compatibility placeholders, such as repeated "Where are my reminders?" items; Pear did not create them. Pear's safe fallback hides known placeholders and blocks writes to affected lists. Reconnecting iCloud or replacing the App-Specific Password will not change this Apple limitation. Calendar, Contacts, and Mail are unaffected, and Microsoft To Do uses Microsoft Graph and is unaffected. Full modern Apple Reminders access would require an Apple-platform companion using EventKit with the user's permission; Pear does not currently provide one. Google Workspace remains coming soon.
Pear exposes tools allowed by your account and permissions. Your AI client decides when to call them. Review recipients, dates, and content before approving writes. Read how Pear handles your data and the current plans before expanding the workflow.
Sources and compatibility status
Documentation checked on 9 September 2026. This page documents configuration and requirements. It does not certify a completed Pear connection in Kiro IDE.
