# Mistral Vibe Code CLI MCP setup for iCloud and Outlook

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

Use the authentication method shown for each client surface.

| Client surface | Authentication | Setup guide |
| --- | --- | --- |
| Mistral Vibe Code CLI | API key via environment | Setup guide available |
<!-- MCP_HOST_COMPATIBILITY:END -->

Configure Pear in Mistral Vibe Code CLI with a personal API key, then verify account access before approving calendar or mail changes.

## 1. Prepare your personal connection

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

```toml
[[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.

```bash
read -r -s -p "Pear API key: " PEAR_API_KEY
printf '\n'
export PEAR_API_KEY
vibe
unset PEAR_API_KEY
```

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

## 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 Code CLI is still pending.

- [Mistral MCP server configuration](https://docs.mistral.ai/vibe/code/cli/mcp-servers)
- [Mistral configuration locations and precedence](https://docs.mistral.ai/vibe/code/cli/configuration)
- [HTML setup guide](https://pearmcp.com/guides/mistral-vibe)