1. Check the administrator and authentication requirements
Vibe Work custom connectors require an administrator; the account owner fills that role on Free, Pro, and Student plans. This is the Work connector surface, separate from Vibe Code CLI and legacy Le Chat.
Sign in to Pear and connect iCloud or Microsoft 365. Pear accepts a personal API key as a Bearer header, or supported OAuth clients using Client ID Metadata Documents (CIMD). Pear does not provide Dynamic Client Registration (DCR).
2. Enter the documented connector details
Open Connectors → + Add Connector → Custom MCP Connector. Use a simple connector name, enter the server URL, and optionally add a description.
Connector name: pear
Server URL: https://pearmcp.com/api/mcp
Description: My connected calendar and mail through PearClick Connect. Work detects authentication automatically and documents Bearer/Basic credentials and OAuth 2.1 with DCR. If it presents a Bearer credential flow, use your Pear API key from Settings privately, following that prompt. Do not put the key in the URL, description, or chat.
The documentation does not establish a manual Bearer override for Pear. If Work routes you to OAuth or fails registration, stop that setup: its documented DCR flow is not evidence of compatibility with Pear CIMD. Do not invent a client ID or share a personal key across an organization. The Vibe Code CLI guide provides a documented personal API-key configuration instead.
3. Verify only after authentication succeeds
If the connector completes authentication, inspect its available functions and ask Work to call pear_provider_status. Confirm the expected account and services, then read a known calendar event within a narrow date range and explicit timezone.
In My Connectors, open the connector and its Functions tab. Keep Always allow off for write functions while checking the workflow. A saved connector or successful read does not establish approved-write readiness.
From a meeting lookup to a reviewed follow-up
After a successful read, try: “Find tomorrow’s planning meeting and preview a follow-up email from my work account. Show recipients and the full message; do not send it.” Request a Pear draft and review its exact details before approving execution.
Work and its selected model receive tool results used in the conversation. Connect only the account you intend to expose to this workflow, and review organization access before configuring any shared connector.
Authentication errors and access removal
If registration fails, recheck the exact HTTPS endpoint and the authentication path Work selected. Repeated OAuth attempts cannot add DCR support to Pear. If authentication works but a service is unavailable, check its connection in Pear.
For a Bearer connection, revoke the API key in Pear to end access and remove the connector in Work. Removing a connector alone does not revoke a copied key. If a supported OAuth grant is ever established, manage that grant separately in Pear Connected apps.
Choose a useful first workflow
Start with a read. Ask which calendars are connected, find an event in a specific date range, or search a mail folder for a message you already know. Specify the account and timezone when they matter.
For Apple accounts, see iCloud setup and services and iCloud Mail workflows. For Microsoft accounts, see Microsoft 365 setup, Outlook Mail, and Microsoft To Do.
Apple Reminders availability depends on the Apple account. For Apple, Pear can read and write only the legacy reminder lists Apple still exposes through CalDAV. If the account has been upgraded to Apple's newer Reminders store, Pear cannot access those native lists and does not copy them into a separate reminder store. Apple may instead return compatibility placeholders, such as repeated "Where are my reminders?" items; Pear did not create them. Pear's safe fallback hides known placeholders and blocks writes to affected lists. Reconnecting iCloud or replacing the App-Specific Password will not change this Apple limitation. Calendar, Contacts, and Mail are unaffected, and Microsoft To Do uses Microsoft Graph and is unaffected. Full modern Apple Reminders access would require an Apple-platform companion using EventKit with the user's permission; Pear does not currently provide one. Google Workspace remains coming soon.
Pear exposes tools allowed by your account and permissions. Your AI client decides when to call them. Review recipients, dates, and content before approving writes. Read how Pear handles your data and the current plans before expanding the workflow.
Sources and compatibility status
Documentation checked on 26 September 2026. A complete Pear authentication, tool-list, read, and approved-write test in Mistral Vibe Work is still pending. Bearer selection and OAuth compatibility remain unverified; this is a readiness guide, not a verified connection claim.
