1. Create your Pear API key
Sign in to Pear, connect your provider account, and copy a Pear API key. This setup uses an environment-backed Bearer token in Gemini CLI settings so the key stays out of the configuration file.
Get Your API KeyApple Reminders compatibility
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.
Read the Apple Reminders compatibility note2. Add Pear to Gemini CLI settings
Gemini CLI documents MCP servers through amcpServersobject in settings and expands environment variables in string values. For Pear, use a Streamable HTTP entry with an environment-backed bearer token.
{
"mcpServers": {
"pear": {
"httpUrl": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer ${PEAR_API_KEY}"
}
}
}
}Set PEAR_API_KEY in the environment Gemini CLI loads. Keep the interpolation in user or project settings; never commit a substituted key.
3. Check the MCP registry
- Use Gemini CLI's MCP inspection command to confirm Pear is connected.
- Check that calendar, task/reminder, contact, mail, and scheduling tools appear.
- Try a read-only prompt before asking Gemini CLI to create or update data.
- Keep API keys outside project files and shell history where possible.
