1. Prepare your personal connection
Sign in to Pear, connect iCloud or Microsoft 365, and create a Pear API key in Settings. Your Mistral model credential and your Pear key serve different purposes; use the Pear key for this MCP connection.
This guide covers Vibe Code CLI. Vibe Work has a separate connector interface; legacy Le Chat is another surface. The CLI currently does not support MCP OAuth.
2. Add Pear to your user configuration
Open ~/.vibe/config.toml in your editor and append this server table without replacing existing settings. Keep personal credentials outside shared project files. Trusted project configuration can take precedence over the user file; check which configuration is active if Pear is missing.
[[mcp_servers]]
name = "pear"
transport = "streamable-http"
url = "https://pearmcp.com/api/mcp"
api_key_env = "PEAR_API_KEY"
api_key_header = "Authorization"
api_key_format = "Bearer {token}"Supply PEAR_API_KEY through a private environment available to the CLI. For a temporary Bash session, the following prompt accepts the key without placing it in shell history. Paste the key at the hidden prompt, not into the command itself.
read -r -s -p "Pear API key: " PEAR_API_KEY
printf '\n'
export PEAR_API_KEY
vibe
unset PEAR_API_KEYDo not paste the key into chat, commit it, or enable shell tracing while handling it. The configuration uses the documented environment-key fields instead of a literal secret header.
3. Inspect the tools and run a bounded read
Use /mcp pear to inspect discovered tools. Vibe prefixes MCP tool names with the server name, so Pear names can appear with an additional pear_ prefix. Ask for pear_provider_status through the Pear server and confirm the expected account and ready services.
Then ask for one known calendar event in a specific date range and timezone. Inspect the tool result before expanding the request. Keep write tools on manual approval; tool discovery alone does not prove a provider read or write succeeds.
Plan a review, then inspect the draft
Try: “Find a free hour tomorrow in my work calendar for a release review. Show me a proposed event with the calendar, timezone, start, end, and attendees; do not create it.” After the read, request a Pear draft and approve only the exact intended action.
Calendar and mail results become context for the model used by Vibe. A locally running CLI still sends requests to Pear and may send returned data to a hosted model.
Troubleshooting and removal
For authentication failures, check that the launched CLI inherited PEAR_API_KEY, the key remains active, and the endpoint is exact. For missing tools, inspect configuration precedence and tool filters. For unavailable services, repair the provider connection in Pear.
Revoke the key in Pear to end access. Remove the server table and clear the key from any private environment source you configured. Closing the shell alone does not revoke the key.
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 Code CLI is still pending.
