Skip to content
Documentation

Connect Pear to the AI tools you already use.

Start with one hosted endpoint, then follow the documented setup path for your chat app, coding agent, or self-hosted client. The server URL and authentication options stay in view while you choose.

Start setupBrowse client guides
OAuthAPI keyJSON / YAMLSkill path
Hosted MCP endpointLive
https://pearmcp.com/api/mcp

Popular setup guides

ChatGPTClaudeGrokPokeCodexClaude Code

Client layer

Chat apps, coding agents, and documented self-hosted paths.

Provider layer

Apple iCloud and Microsoft 365 are live today.

The short version

Three steps from account to first result.

Pear separates the data connection from the AI client connection. Set up each provider once, then reuse it across the clients you configure.

  1. 1

    Create your Pear account

    Start Free without a card, then open the dashboard to connect your work.

  2. 2

    Connect a provider

    Choose Apple iCloud or Microsoft 365. Google Workspace is still coming soon.

  3. 3

    Follow your client guide

    Use the OAuth, API-key, config-file, or skill path shown for your client.

Client guides

Choose the app in front of you.

The same Pear service appears in different places depending on the client: an OAuth screen, a config file, editor settings, or a dedicated skill path.

Open setup
Conversational clients

Chat apps

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

ChatGPTOAuth client metadata document · Developer mode appSetup guide availableChatGPT custom app: Pear host smoke pendingHost lifecycle evidence is pending.ClaudeOAuth client metadata document · Custom connector betaSetup guide availableClaude hosted remote connector: Pear host smoke pendingHost lifecycle evidence is pending.GrokOAuth with a registered Client ID · API key via environment · API key · Build/API documented; web blockedSetup guide availableGrok web: BlockedThe Pear OAuth application is not active.Grok Build: Pear host smoke pendingHost lifecycle evidence is pending.xAI API: Pear host smoke pendingHost lifecycle evidence is pending.PokeAPI key · Recipe/custom integrationSetup guide availablePoke: Pear host smoke pendingHost lifecycle evidence is pending.
Editor and terminal clients

Coding agents

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

CodexAPI key via environment · config.tomlSetup guide availableCodex CLI: Pear host smoke pendingHost lifecycle evidence is pending.Codex in ChatGPT desktop app: Pear host smoke pendingHost lifecycle evidence is pending.Claude CodeAPI key via environment · Claude Code MCP configSetup guide availableClaude Code: Pear host smoke pendingHost lifecycle evidence is pending.CursorAPI key via environment · .cursor/mcp.jsonSetup guide availableCursor: Pear host smoke pendingHost lifecycle evidence is pending.Devin Desktop / WindsurfAPI key via environment · Cascade MCP settingsSetup guide availableDevin Desktop / Cascade (Windsurf legacy config): Pear host smoke pendingHost lifecycle evidence is pending.ClineAPI key · Remote ServersSetup guide availableCline: Pear host smoke pendingHost lifecycle evidence is pending.VS Code + CopilotAPI key via environment · .vscode/mcp.jsonSetup guide availableVS Code Copilot: Pear host smoke pendingHost lifecycle evidence is pending.Gemini CLIAPI key via environment · settings.jsonSetup guide availableGemini CLI: Pear host smoke pendingHost lifecycle evidence is pending.ContinueAPI key via environment · config.yamlSetup guide availableContinue: Pear host smoke pendingHost lifecycle evidence is pending.
Local and community clients

Self-hosted and skill clients

Use Pear through HTTP config or a dedicated skill where the client expects it.

HermesAPI key via environment · config.yamlSetup guide availableHermes Agent: Pear host smoke pendingHost lifecycle evidence is pending.OpenClawExternal skill · ClawHub skillSetup guide availableOpenClaw skill: External skill pathThis is an external skill path, not direct Pear-hosted MCP.
Provider setup

Connect the work data once.

Billing, revocation, credentials, and permissions stay in one Pear dashboard, even when you follow more than one documented client setup path.

Live

Apple iCloud

App password · reminders limited

CalendarLegacy CalDAV remindersContactsMail
View provider guide
Live

Microsoft 365

OAuth

CalendarTasks (To Do)ContactsMail
View provider guide
Coming soon

Google Workspace

Preview

CalendarTasksContactsGmail
View provider guide
AI-readable documentation

Plain Markdown for agents and search.

These routes mirror Pear's product overview, provider status, and client guides in a format that assistants can read directly.

Model Context Protocol
Pear MCP Markdown IndexPear MCP OverviewAI Productivity FAQCodex iCloud Mail and CalendarClaude Apple Calendar MCPPear vs Local MCP ServersMicrosoft 365 MCPGoogle MCP Coming SoonClaude Guide
ChatGPT GuideCodex GuideGrok GuideHermes GuideOpenClaw GuideCursor GuideWindsurf GuideCline GuidePoke GuideClaude Code GuideVS Code and GitHub Copilot GuideGemini CLI GuideContinue Guide
Before you connect
  • Use an Apple App-Specific Password for iCloud, or Microsoft OAuth for Microsoft 365.
  • OAuth-native clients redirect into Pear sign-in instead of asking for a raw key.
  • Config-first clients use the hosted Pear server URL with the authentication method in their guide.
  • OpenClaw currently uses a separate skill path instead of the hosted endpoint.

Need a hand choosing?

Tell us which AI client and provider you use. We'll point you to the right setup path.

Contact support
Ready when you are

Connect your first client in a few focused steps.

Create your account, connect Apple iCloud or Microsoft 365, then follow the guide for the AI client you already use.

Start freeCompare plans