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
Choose your client guide, check its authentication and transport, then connect a live provider suite or an enabled mail-only beta.
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.
2 live provider suites · 5 maintained workflow paths. A published guide does not establish every client-and-provider combination.
Conversational clients
Connect the assistants people already ask to plan, search, and follow up.
Setup guide available
Setup surface: Developer mode app. Connect through Pear sign-in using ChatGPT’s preferred CIMD discovery path.
Setup guide available
Setup surface: Custom connector. Use Pear through Claude’s hosted connector infrastructure and preferred CIMD discovery path.
Setup guide available
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.
Setup guide available
Setup surface: Recipe/custom integration. Use Pear from Poke with server URL and bearer auth.
Setup guide available
Setup surface: Custom remote connector. Check remote connector access and the authentication requirements before connecting Pear.
Setup guide available
Setup surface: Custom MCP connector. Add Pear in Manus as a custom HTTP connector with an Authorization header.
Setup guide available
Setup surface: Custom MCP Connector. Review the documented Vibe Work custom MCP setup and its authentication limits before connecting your iCloud or Microsoft 365 account.
Editor and terminal clients
Give code agents calendar, mail, contact, and task context without leaving the workflow.
Setup guide available
Setup surface: Private user settings. Explore Meta Muse and the manual Muse Code MCP setup. Consumer Muse connection and authenticated Muse Code testing remain unverified.
Setup guide available
Setup surface: config.toml. Add Pear once for Codex CLI and the ChatGPT desktop app through their shared MCP configuration.
Setup guide available
Setup surface: Claude Code MCP config. Bring Pear into terminal coding sessions with Claude Code MCP.
Setup guide available
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.
Setup guide available
Setup surface: Cascade mcp_config.json. Configure the legacy Cascade agent in Devin Desktop with Pear. Current Devin Local uses a separate configuration path.
Setup guide available
Setup surface: Remote Servers. Add Pear alongside coding tools for calendar and mail actions.
Setup guide available
Setup surface: .vscode/mcp.json. Add Pear to VS Code so Copilot agents can call productivity tools.
Setup guide available
Setup surface: settings.json. Expose Pear tools to Gemini CLI through mcpServers.
Setup guide available
Setup surface: config.yaml. Use Pear in Continue as a cloud-hosted MCP server.
Setup guide available
Setup surface: opencode.json or opencode.jsonc. Choose the OpenCode v1 or v2 configuration for Pear calendar and mail tools.
Setup guide available
Setup surface: User MCP configuration. Add Pear to Kiro IDE with an approved environment variable for your API key.
Setup guide available
Setup surface: /mcp add in Copilot CLI. Configure a personal Pear connection from the Copilot terminal, separately from VS Code.
Setup guide available
Setup surface: IDE MCP configuration. Connect Antigravity IDE to Pear with a private remote MCP header. This is separate from Gemini CLI setup.
Setup guide available
Setup surface: Customize → MCPs. Add Pear as a custom HTTP MCP server in Devin with a private Authorization header.
Setup guide available
Setup surface: Settings → MCP → Add manually. Add Pear to Trae as a remote HTTP MCP server. Trae sends the header you store and does not refresh it.
Setup guide available
Setup surface: context_servers remote URL. Add Pear as a remote context server in Zed. The Authorization header keeps Zed on the API-key path.
Setup guide available
Setup surface: Custom MCP server headers. Add Pear to Warp as a Streamable HTTP server with a private Authorization header.
Setup guide available
Setup surface: streamable_http extension. Add Pear to Goose as a streamable HTTP extension with a private Authorization header.
Setup guide available
Setup surface: streamable-http MCP server. Add Pear to Roo Code as a streamable-http MCP server with a private Authorization header.
Setup guide available
Setup surface: HTTP MCP server. Add Pear to Augment as an HTTP MCP server with a private Authorization header.
Setup guide available
Setup surface: amp.mcpServers header. Add Pear to Amp with a remote URL and an Authorization header. Amp substitutes environment variables in that header.
Setup guide available
Setup surface: User-scope mcp.json. Add Pear to Junie as a remote HTTP server with a private Authorization header in the user-scope mcp.json.
Setup guide available
Setup surface: Private user settings. Connect Qwen Code to Pear with a private API-key header to use your connected calendar, mail, contacts, and supported tasks.
Setup guide available
Setup surface: Private MCP configuration. Connect Kimi Code CLI to Pear with an API key from your private environment for calendar, mail, contacts, and supported tasks.
Setup guide available
Setup surface: Custom connector. Connect QoderWork to Pear with a private API-key header to use your connected calendar, mail, contacts, and supported tasks.
Setup guide available
Setup surface: User config.toml. Configure Pear in Mistral Vibe Code CLI with a personal API key, then verify account access before approving calendar or mail changes.
Local and community clients
Connect locally operated clients to hosted Pear through HTTP config or a dedicated skill.
Setup guide available
Setup surface: config.yaml. Connect Hermes Agent with the Pear hosted server URL.
Setup guide available
Setup surface: mcp.servers. Connect OpenClaw to Pear with an environment-backed Bearer header.
Setup guide available
Setup surface: MCP Servers settings. Add Pear as an HTTP MCP server in Jan and use a model that can call tools. Provider requests still reach hosted Pear.
Setup guide available
Setup surface: Private mcp.json. Give a tool-capable model in LM Studio access to Pear using remote MCP and a private configuration.
Setup guide available
Setup surface: Private MCP server settings. Add Pear to AnythingLLM with an explicit Streamable HTTP transport and a privately stored Authorization header.
Setup guide available
Setup surface: Install MCP Server → HTTP. Install Pear in Raycast as an HTTP MCP server and leave Dynamic OAuth empty.
Setup guide available
Setup surface: Remote MCP requirements. Check another AI app’s transport, authentication and tool support before connecting your personal Pear account.
Build a private assistant
Connect a conversation agent to Pear. Robot audio and owner access require application setup.
Setup guide available
Setup surface: Python MCPToolset. Add Pear to a private LiveKit Python voice agent with authenticated MCP and selected email read tools. Robot audio integration requires a separate adapter.
Setup guide available
Setup surface: Custom MCP server dashboard. Configure a private ElevenLabs agent with Pear MCP, a secret Authorization header and selected read tools. Includes access requirements and robot integration limits.
A guide can be available while a client feature, provider, or action remains unavailable to a particular account. Check each layer before you start.
Hosted Streamable HTTP endpoint https://pearmcp.com/api/mcp
“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.
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 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.
Visible tools and write actions remain subject to provider permissions, client capabilities, plan access, workspace policy, and action approval.
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.
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.
OAuth
This provider suite connection is available in Pear today. Client access and individual actions still depend on the selected setup path and permissions.
Preview · send-only Gmail first
This provider suite integration is not available in Pear today. The linked page records its status and points to the live alternatives.
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.
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
Use Pear with Apple Calendar when ChatGPT Developer Mode is available; setup and actions depend on account and workspace policy.
Published client paths
Named capabilities
Calendar
Workflow path
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
Named capabilities
Calendar
Workflow path
Read iCloud Mail from documented AI-client paths; write actions depend on client permissions.
Published client paths
Named capabilities
Mail · Contacts
Provider path
Use Apple Calendar, Contacts, and iCloud Mail through one hosted endpoint, plus legacy CalDAV reminder data where Apple exposes it.
Published client paths
Named capabilities
Calendar · Contacts · Mail
Provider path
Use Outlook Mail, Calendar, Contacts, and Microsoft To Do through Microsoft OAuth.
Published client paths
Named capabilities
Calendar · Contacts · Mail · To Do
Confirm that your client account exposes its documented MCP surface, use the auth method named in the Pear guide, and connect a live provider suite or an enabled compatible IMAP/SMTP mailbox beta. Review permissions before approving write actions.