# Antigravity IDE MCP setup for iCloud and Microsoft 365

<!-- MCP_HOST_IDS: antigravity-ide -->
<!-- MCP_HOST_COMPATIBILITY:START -->
## Connection and authentication

Use the authentication method shown for each client surface.

| Client surface | Authentication | Setup guide |
| --- | --- | --- |
| Google Antigravity | API key | Setup guide available |
<!-- MCP_HOST_COMPATIBILITY:END -->

Connect Google Antigravity IDE to Pear so your coding assistant can check your connected iCloud or Microsoft 365 calendar, mail, and contacts.

## 1. Prepare your Pear account

[Sign in to Pear](https://pearmcp.com/login), connect iCloud or Microsoft 365, and create a Pear API key in Settings. The key grants access to the services and permissions available to your Pear account. This setup uses Antigravity IDE's custom MCP configuration and does not require a Pear MCP Store listing.

## 2. Open the personal MCP configuration

In the agent side panel, open the three-dot menu, then MCP Servers → Manage MCP Servers → View raw config. Use the global `~/.gemini/config/mcp_config.json` file for your personal credential, outside a shared project. Merge `pear` into the existing `mcpServers` object without replacing other servers.

```json
{
  "mcpServers": {
    "pear": {
      "serverUrl": "https://pearmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PEAR_API_KEY"
      }
    }
  }
}
```

Replace `YOUR_PEAR_API_KEY` only in the private local file. Antigravity requires `serverUrl` for remote servers; `url` and `httpUrl` are not substitutes. The header holds the literal key. Do not commit or share it.

## 3. Check the account and tools

Inspect Pear in the MCP server panel. Ask the agent to call `pear_provider_status`, then read one known calendar event with a specific date range and timezone. Check that the expected account and services are ready.

Keep tool approvals enabled. A useful first prompt is: “Check my work calendar for tomorrow in my timezone and suggest a free hour for this release review. Don't create an event yet.” Ask for a preview before any change and approve only the intended account, recipients, and details. A read does not establish write readiness.

## Troubleshooting and removal

If Pear is absent, check JSON syntax and `serverUrl`. If authentication fails, check the `Bearer ` prefix and the key's active status in Pear. This setup uses the explicit header; an OAuth registration prompt is not a completed Pear connection.

Resolve provider readiness errors in Pear before retrying an action. To remove access, revoke the API key in Pear and remove its local server entry. Revoke an exposed key before replacing it.

## Provider limits and next steps

Available tools depend on your connected provider, account permissions, and client settings. Start with a read and 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. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Antigravity IDE is still pending.

- [Official Antigravity MCP configuration and custom headers](https://antigravity.google/docs/mcp?tab=ide)
- [HTML setup guide](https://pearmcp.com/guides/antigravity)