ChatGPT
Setup guide available
- Authentication
- OAuth
- Transport
- Remote MCP
Setup surface: Developer mode app. Connect through Pear sign-in using ChatGPT’s preferred CIMD discovery path.
Pear MCP compatibility
Find the maintained path from your AI client to Pear.
Choose a published client guide, check its authentication and transport, then connect a live provider suite or, when enabled, a compatible IMAP/SMTP mailbox beta.
This page separates guide availability, client requirements, provider state, and maintained workflow content. It does not claim every possible client-and-provider combination.
15 setup-guide families2 live provider suites5 maintained workflow paths
Published compatibility mapNo blanket matrix
- 1Choose a client guideFollow its exact setup surface15
- 2Use its documented authOAuth, API key, config, or skill path
- 3Check the data connectionLive suite or enabled mailbox beta2 live suites
Hosted Streamable HTTP endpoint
https://pearmcp.com/api/mcpRead the labels precisely
Compatibility has four separate gates.
A guide can be available while a client feature, provider, or action remains unavailable to a particular account. Check each layer before you start.
Guide availability
“Setup guide available” means Pear publishes a maintained setup path for that client family. It is not a promise about every client plan or workspace.
Authentication and transport
Each guide names its own OAuth, Bearer API key, configuration-file, or external-skill path. Do not copy one client’s setup into another.
Provider state
Provider suite availability is listed separately. Apple iCloud and Microsoft 365 are live; Google Workspace is still coming soon. Compatible IMAP/SMTP mailboxes are a mail-only beta when enabled.
Permissions still apply
Visible tools and write actions remain subject to provider permissions, client capabilities, plan access, workspace policy, and action approval.
Client setup guides
15 maintained setup-guide families.
Use the guide for the exact client surface you are configuring. Authentication, transport, setup location, client plan, and workspace controls differ. Most guides configure hosted Pear directly; OpenClaw is explicitly labelled as a separate external-skill path.
Conversational clients
Chat apps
Connect the assistants people already ask to plan, search, and follow up.
Claude
Setup guide available
- Authentication
- OAuth
- Transport
- Remote MCP
Setup surface: Custom connector beta. Use Pear through Claude’s hosted connector infrastructure and preferred CIMD discovery path.
Grok
Setup guide available
- Authentication
- Web OAuth
- Transport
- Remote MCP
Setup surface: Web OAuth + PKCE. Connect Grok Web with Pear’s active production OAuth Client ID or use the documented Grok Build and xAI API Bearer paths. Grok Bot is not supported or tested yet.
Poke
Setup guide available
- Authentication
- Bearer API key
- Transport
- Remote MCP
Setup surface: Recipe/custom integration. Use Pear from Poke with server URL and bearer auth.
Folk
Setup guide available
- Authentication
- Bearer API key
- Transport
- Remote MCP
Setup surface: Custom MCP server. Use Pear from Folk with the hosted server URL and your Pear API key.
Editor and terminal clients
Coding agents
Give code agents calendar, mail, contact, and task context without leaving the workflow.
Codex
Setup guide available
- Authentication
- Bearer API key
- Transport
- Streamable HTTP
Setup surface: config.toml. Add Pear once for Codex CLI and the ChatGPT desktop app through their shared MCP configuration.
Claude Code
Setup guide available
- Authentication
- Bearer API key
- Transport
- Remote MCP
Setup surface: Claude Code MCP config. Bring Pear into terminal coding sessions with Claude Code MCP.
Cursor
Setup guide available
- Authentication
- OAuth + PKCE
- Transport
- Remote MCP
Setup surface: Cursor editor or Cloud Agents dashboard. Connect Pear separately in the Cursor editor or Cursor Cloud Agents with OAuth, or use the documented API-key alternative.
Devin Desktop / Windsurf
Setup guide available
- Authentication
- Bearer API key
- Transport
- Streamable HTTP
Setup surface: Cascade MCP settings. Use Pear in Devin Desktop / Cascade; legacy installs retain Windsurf configuration paths.
Cline
Setup guide available
- Authentication
- Bearer API key
- Transport
- Streamable HTTP
Setup surface: Remote Servers. Add Pear alongside coding tools for calendar and mail actions.
VS Code + Copilot
Setup guide available
- Authentication
- Bearer API key
- Transport
- HTTP MCP
Setup surface: .vscode/mcp.json. Add Pear to VS Code so Copilot agents can call productivity tools.
Gemini CLI
Setup guide available
- Authentication
- Bearer API key
- Transport
- Streamable HTTP
Setup surface: settings.json. Expose Pear tools to Gemini CLI through mcpServers.
Continue
Setup guide available
- Authentication
- Bearer API key
- Transport
- Streamable HTTP
Setup surface: config.yaml. Use Pear in Continue as a cloud-hosted MCP server.
Local and community clients
Local and skill clients
Connect locally operated clients to hosted Pear through HTTP config or a dedicated skill.
Hermes
Setup guide available
- Authentication
- Bearer API key
- Transport
- Remote HTTP
Setup surface: config.yaml. Connect Hermes Agent with the Pear hosted server URL.
OpenClaw
Setup guide available
- Authentication
- External skill
- Transport
- Skill path
Setup surface: ClawHub skill. Use the OpenClaw skill path for Apple-focused workflows.
Provider state
Check the data connection separately.
A client guide explains how that client reaches Pear. These cards cover provider suites: Apple iCloud and Microsoft 365 are live, while Google Workspace remains a preview. Mail-only compatible IMAP/SMTP mailbox support is a separate beta when enabled.
Live
Apple iCloud
App password · reminders limited
This provider suite connection is available in Pear today. Client access and individual actions still depend on the selected setup path and permissions.
- Calendar
- Legacy CalDAV reminders
- Contacts
Live
Microsoft 365
OAuth
This provider suite connection is available in Pear today. Client access and individual actions still depend on the selected setup path and permissions.
- Calendar
- Tasks (To Do)
- Contacts
Coming soon
Google Workspace
Preview
This provider suite integration is not available in Pear today. The linked page records its status and points to the live alternatives.
- Calendar
- Tasks
- Contacts
- Gmail
Maintained workflow content
Only the pairings Pear publishes.
These are the client-and-provider or client-and-workflow relationships in Pear’s maintained public content map. They are deliberately narrower than the full client guide list.
Why there is no full matrix
A client setup guide and a live provider suite do not automatically create a maintained client-by-provider pairing. Pear lists a pairing here only when its public workflow map names that relationship and links a dedicated page.
Workflow path
ChatGPT + Apple Calendar
Use Pear with Apple Calendar when ChatGPT Developer Mode is available; setup and actions depend on account and workspace policy.
Published client paths
ChatGPT
Named capabilities
Calendar
Workflow path
Claude + Apple Calendar
Follow Pear’s documented custom-connector path; Team and Enterprise setup starts with an Owner or Primary Owner, and tools depend on permissions.
Published client paths
Claude
Named capabilities
Calendar
Workflow path
AI + iCloud Mail
Read iCloud Mail from documented AI-client paths; write actions depend on client permissions.
Published client paths
ChatGPTClaude
Named capabilities
Mail · Contacts
Provider path
Hosted iCloud MCP
Use Apple Calendar, Contacts, and iCloud Mail through one hosted endpoint, plus legacy CalDAV reminder data where Apple exposes it.
Published client paths
ChatGPTClaude
Named capabilities
Calendar · Contacts · Mail
Provider path
Microsoft 365 MCP
Use Outlook Mail, Calendar, Contacts, and Microsoft To Do through Microsoft OAuth.
Published client paths
ChatGPTClaude
Named capabilities
Calendar · Contacts · Mail · To Do
Before you connect
Start with the exact guide, not a generic configuration.
Confirm that your client account exposes its documented MCP surface, use the auth method named in the Pear guide, and connect a provider suite marked Live or, when enabled, a compatible IMAP/SMTP mailbox beta. Review permissions before approving write actions.
Start with a maintained path
Connect your client to Pear, one documented layer at a time.
Create your account, connect a live provider suite or a compatible IMAP/SMTP mailbox beta when enabled, then follow the setup guide for the exact AI client surface you use.