# Connect another AI app to Pear MCP ## Connection and authentication Use the authentication method shown for each client surface. | Client surface | Authentication | Setup guide | | --- | --- | --- | | Generic local MCP client | API key via environment | Setup guide available | This checklist is for an AI app or local agent without a dedicated Pear guide. It does not certify every MCP client. First check [Pear's client guides](https://pearmcp.com/docs) for instructions specific to the app, version, plan, and workspace you use. ## Requirements The AI app must support remote MCP over Streamable HTTP and an authentication method Pear accepts. Running a local model does not establish MCP support. A stdio-only client needs a separately supported remote connection path; this guide does not provide a universal bridge or CLI command. Create a Pear account and connect Apple iCloud or Microsoft 365. Add a personal MCP server named Pear with this complete hosted endpoint: ```text https://pearmcp.com/api/mcp ``` Choose the client's documented remote HTTP or Streamable HTTP option. Do not substitute a legacy SSE URL or local command. The client handles MCP initialization, protocol negotiation, and tool discovery. Configuration schemas vary; use that client's official documentation instead of copying another host's JSON. ## Personal API-key authentication If the client documents a Bearer token field or custom HTTP headers, create or copy a Pear API key in Settings. A dedicated Bearer token field normally accepts the key itself. A complete HTTP Authorization header has this form: ```text Authorization: Bearer ``` This is a header illustration, not a working credential or configuration file. Follow the client documentation so the Bearer prefix appears exactly once. Prefer the client's native secret input or documented environment-variable interpolation. Do not assume a variable such as PEAR_API_KEY is expanded by every client. If a literal key is required, store it only in private personal settings outside shared projects and version control. Never put it in chat, a URL query string, or a shared team connector. If the client cannot keep a personal credential private, stop before adding the key. ## OAuth compatibility Pear publishes OAuth discovery metadata and supports Client ID Metadata Documents (CIMD). Pear intentionally has no Dynamic Client Registration (DCR) endpoint. A host requiring DCR alone cannot complete that path. Read the [host-specific compatibility guidance](https://pearmcp.com/mcp-compatibility) before using OAuth or arranging client preregistration. Do not invent a Client ID or secret, reuse another host's registration, or use a Pear API key as an OAuth client secret. OAuth support in a client is not itself proof of interoperability. ## Verify without sending or changing provider data 1. Refresh MCP connections and inspect the returned tools. Keep tool approvals on. 2. Ask: "Call pear_provider_status and report which accounts and services are ready. Do not change anything." 3. Choose one ready account and perform a bounded read: list calendar events for one day with an explicit timezone, or find one known message in a named folder. Compare the result with the original provider app. Use returned IDs and schemas. 4. To inspect a write workflow, request a non-executing draft and review the exact account, recipients, dates, and content. Stop at draft and approval review for this setup check. Do not send mail or execute a provider change to test the connection. A working read does not establish write support. ## Troubleshooting and revocation - **401 Unauthorized:** check the endpoint, auth mode, and whether the key is missing, expired, or revoked. Confirm environment interpolation works in the process launching the client. For OAuth, use the host guide to sign in again. - **403 Forbidden:** inspect the error and review granted scopes, provider readiness, account or plan restrictions, and organization policy. Retrying does not grant permission. - **Empty tool list:** check connection state, tool filters, account readiness, and scopes before attempting provider actions. This is not proof of an empty mailbox or calendar. Removing a server from the AI app does not prove that its credential was revoked. Revoke a dedicated key in Pear, or rotate a shared key when required; rotation affects other clients using it. Disconnect a managed OAuth app in Pear's Connected apps settings. Legacy OAuth connections may require API-key rotation until they reauthorize. ## Local model and provider boundaries A local model can use Pear through a capable MCP client, but the connection still goes to Pear's hosted endpoint. Pear receives structured tool requests and fetches permitted provider data. Results return to the AI app and may reach its chosen model service. This is not an offline or local-only provider connection. Review the app's data settings and [Pear's data handling](https://pearmcp.com/data-handling). Apple iCloud and Microsoft 365 are live. Apple Calendar, Contacts, and Mail are supported. Apple Reminders is limited to legacy CalDAV reminder data; Pear cannot access Apple's upgraded Reminders store. Microsoft To Do is unaffected. Google Workspace is coming soon. Available tools depend on connected providers, granted scopes, account readiness, plan, and enabled capabilities. For provider setup and useful first reads, see [iCloud](https://pearmcp.com/icloud-mcp-server), [Microsoft 365](https://pearmcp.com/microsoft-365-mcp-server), and [Pear's tool reference](https://pearmcp.com/mcp-tools). ## Sources and status Official protocol sources checked on 26 September 2026: - [MCP transport specification](https://modelcontextprotocol.io/specification/2025-11-25/basic/transports) - [MCP authorization specification](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization) This documents requirements, not a completed connection test. Authentication, tool discovery, reads, persistence, and revocation must be tested in the actual client. Writes need separate evidence. See [Pear's compatibility status](https://pearmcp.com/mcp-compatibility).