Skip to content

Pear MCP compatibility

Your AI. Its setup path.

Choose your client guide, check its authentication and transport, then connect a live provider suite or an enabled mail-only beta.

Client setup guides

42 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.

2 live provider suites · 5 maintained workflow paths. A published guide does not establish every client-and-provider combination.

Conversational clients

Chat apps

Connect the assistants people already ask to plan, search, and follow up.

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.

Perplexity

Setup guide available

Authentication
API key requirements
Transport
Streamable HTTP

Setup surface: Custom remote connector. Check remote connector access and the authentication requirements before connecting Pear.

Manus

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: Custom MCP connector. Add Pear in Manus as a custom HTTP connector with an Authorization header.

Mistral Vibe Work

Setup guide available

Authentication
Authentication pending
Transport
Streamable HTTP

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

Coding agents

Give code agents calendar, mail, contact, and task context without leaving the workflow.

Muse Code

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

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.

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.

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.

OpenCode

Setup guide available

Authentication
Bearer API key
Transport
Streamable HTTP

Setup surface: opencode.json or opencode.jsonc. Choose the OpenCode v1 or v2 configuration for Pear calendar and mail tools.

Devin

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: Customize → MCPs. Add Pear as a custom HTTP MCP server in Devin with a private Authorization header.

Trae

Setup guide available

Authentication
Static Bearer header
Transport
Streamable HTTP

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.

Zed

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

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.

Warp

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: Custom MCP server headers. Add Pear to Warp as a Streamable HTTP server with a private Authorization header.

Goose

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: streamable_http extension. Add Pear to Goose as a streamable HTTP extension with a private Authorization header.

Roo Code

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: streamable-http MCP server. Add Pear to Roo Code as a streamable-http MCP server with a private Authorization header.

Amp

Setup guide available

Authentication
Environment-backed Bearer header
Transport
Streamable HTTP

Setup surface: amp.mcpServers header. Add Pear to Amp with a remote URL and an Authorization header. Amp substitutes environment variables in that header.

Junie

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

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.

Qwen Code

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

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.

Kimi Code CLI

Setup guide available

Authentication
API key via environment
Transport
Streamable HTTP

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.

QoderWork

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: Custom connector. Connect QoderWork to Pear with a private API-key header to use your connected calendar, mail, contacts, and supported tasks.

Local and community clients

Local and skill clients

Connect locally operated clients to hosted Pear through HTTP config or a dedicated skill.

Jan Desktop

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

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.

LM Studio

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: Private mcp.json. Give a tool-capable model in LM Studio access to Pear using remote MCP and a private configuration.

AnythingLLM

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: Private MCP server settings. Add Pear to AnythingLLM with an explicit Streamable HTTP transport and a privately stored Authorization header.

Raycast

Setup guide available

Authentication
Private Bearer header
Transport
Streamable HTTP

Setup surface: Install MCP Server → HTTP. Install Pear in Raycast as an HTTP MCP server and leave Dynamic OAuth empty.

Build a private assistant

Voice agents

Connect a conversation agent to Pear. Robot audio and owner access require application setup.

LiveKit Agents

Setup guide available

Authentication
Bearer API key
Transport
Streamable HTTP

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.

ElevenLabs Agents

Setup guide available

Authentication
Bearer API key
Transport
Streamable HTTP

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.

Read 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.

Hosted Streamable HTTP endpoint https://pearmcp.com/api/mcp

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.

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
  • Mail
View provider details
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
  • Mail
View provider details
Coming soon

Google Workspace

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.

  • Calendar
  • Tasks
  • Contacts
  • Send-only Gmail first
Read status and live alternatives
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.

Maintained page

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

Open maintained page
Maintained page

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

Open maintained page

Workflow path

AI + iCloud Mail

Maintained page

Read iCloud Mail from documented AI-client paths; write actions depend on client permissions.

Published client paths

ChatGPTClaude

Named capabilities

Mail · Contacts

Open maintained page

Provider path

Hosted iCloud MCP

Maintained page

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

Open maintained page

Provider path

Microsoft 365 MCP

Maintained page

Use Outlook Mail, Calendar, Contacts, and Microsoft To Do through Microsoft OAuth.

Published client paths

ChatGPTClaude

Named capabilities

Calendar · Contacts · Mail · To Do

Open maintained page

Start with your client’s guide.

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.