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 locally operated client. Every path connects to hosted Pear; the server URL and authentication options stay in view while you choose.
https://pearmcp.com/api/mcpClient layer
Chat apps, coding agents, and locally operated clients that connect to hosted Pear.
Provider layer
Apple iCloud and Microsoft 365 are live today.
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.
- 01
Create your Pear account
Start Free without a card, then open the dashboard to connect your work.
- 02
Connect a provider
Choose Apple iCloud or Microsoft 365. Google Workspace is still coming soon.
- 03
Follow your client guide
Use the OAuth, API-key, config-file, or skill path shown for your client.
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.
Filter guides
Setup guides
15 guides

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.
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.
Browse 33 Markdown routes
Direct discovery
For agents and tooling
Start from compact Markdown, then follow the standards-based catalog, authentication, and service descriptions without scraping the visual interface.
- llms.txtCurated product map and fit boundaries
- MCP tools MarkdownCanonical tool names, access, safety, and scopes
- Compatibility MarkdownConservative support and authentication status
- Authentication guideOAuth, API keys, registration policy, and secret handling
- API catalogRFC 9727 service links and metadata
- OpenAPIMachine-readable HTTP contract
- 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.

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.