# Mistral Vibe Work MCP connector readiness for Pear

<!-- MCP_HOST_IDS: mistral-work -->
<!-- MCP_HOST_COMPATIBILITY:START -->
## Connection and authentication

Use the authentication method shown for each client surface.

| Client surface | Authentication | Setup guide |
| --- | --- | --- |
| Mistral Vibe Work | API key | Setup guide available |
<!-- MCP_HOST_COMPATIBILITY:END -->

Review the documented Vibe Work custom MCP setup and its authentication limits before connecting your iCloud or Microsoft 365 account.

## 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](https://pearmcp.com/guides/mistral-vibe) and legacy Le Chat.

[Sign in to Pear](https://pearmcp.com/login) 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.

```text
Connector name: pear
Server URL: https://pearmcp.com/api/mcp
Description: My connected calendar and mail through Pear
```

Click 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](https://pearmcp.com/guides/mistral-vibe) 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.

## Provider limits and next steps

Tools depend on your connected provider, account permissions, and client settings. Start with a read, then inspect a preview before approving writes.

- [iCloud setup](https://pearmcp.com/icloud-mcp-server)
- [iCloud Mail](https://pearmcp.com/ai-icloud-mail)
- [Microsoft 365 setup](https://pearmcp.com/microsoft-365-mcp-server)
- [Outlook Mail](https://pearmcp.com/outlook-mail-mcp)
- [Microsoft To Do](https://pearmcp.com/microsoft-to-do-mcp)
- [Data handling](https://pearmcp.com/data-handling)
- [Plans](https://pearmcp.com/pricing)

Pear's hosted CalDAV connection cannot access Apple's upgraded Reminders store. Only legacy reminder data still exposed through CalDAV is available; reconnecting cannot change this limit. Microsoft To Do is unaffected. Google Workspace is coming soon.

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

- [Mistral Work custom MCP connectors and authentication](https://docs.mistral.ai/vibe/work/connectors/mcp-connectors)
- [HTML setup guide](https://pearmcp.com/guides/mistral-work)