# Meta Muse and Pear ## Connection and authentication Use the authentication method shown for each client surface. | Client surface | Authentication | Setup guide | | --- | --- | --- | | Muse Code | API key | Setup guide available | Canonical page: https://pearmcp.com/guides/muse Documentation checked: 21 September 2026. ## Choose the right surface - **Muse** is Meta's consumer personal agent. Its Connector Platform accepts an Existing MCP endpoint for developer review. Pear submitted its API-key connector on 21 September 2026, but is not yet approved or verified inside Muse. Meta's launch announced a US rollout; check Meta for current availability. - **Muse Code** is Meta's terminal coding agent. It documents Streamable HTTP MCP with static headers. Pear provides a manual configuration below; authenticated host testing remains open. - **Muse Spark** is the model family. Spark 1.3 is available in Muse Code and Meta Model API. A model's tool capabilities do not prove MCP support in a particular app. ## Muse connector technical details Meta's [Connector Platform](https://muse.ai/platform) accepts **Existing MCP** with a public HTTPS hosted endpoint. This is a developer submission path, not evidence that a user can paste an arbitrary MCP URL into the consumer app. - Endpoint: `https://pearmcp.com/api/mcp`. - Connection: Streamable HTTP MCP. The characterized legacy transport supports `2025-11-25` and `2025-06-18`; use initialization to negotiate support. Requests accept `application/json, text/event-stream`; Pear's legacy POST replies are JSON. Send the negotiated `MCP-Protocol-Version` on subsequent requests. - Authentication for this submission: **API keys**. Send the user's own key in `Authorization: Bearer `, injected through the host's secure credential facility. Never ask users to paste keys into chat or a shared file. Do not send Apple app passwords or Microsoft tokens directly to Muse; Pear manages the provider connections. - Start with MCP `initialize`, `notifications/initialized`, `tools/list`, then `tools/call` for `pear_provider_status`. Use only tools and schemas actually returned for that account. Connected providers, scopes, account readiness and plan control discovery and execution. - Scope choices: a dedicated scoped Pear key is preferred where available. Start with the read permissions needed for the intended services. Writes require the appropriate server-side scopes and explicit approval for the exact operation; a natural-language request or tool annotation does not override Pear's checks. - Before writes, review the account, recipients, dates and content. Follow `pear_draft_write` and the approval/approved-write tools when exposed by the current account. Do not automatically retry an interrupted write: the provider outcome may be unknown. Server tools remain responsible for validation, entitlements, approval policy and provider access. - Treat `401` as a missing/invalid credential, `403` as insufficient permission, `429` as a limit and `503` as unavailable. Inspect JSON-RPC errors and `result.isError`; HTTP 200 alone does not mean an action succeeded. Do not log credentials or provider response bodies in connector telemetry. - Disconnect through Muse to stop future requests. Removing a host connection does not prove the Pear API key was revoked. Revoke a dedicated key in Pear, or rotate a shared key if necessary (rotation also affects other clients using that key). - Access: Pear account plus a connected iCloud or Microsoft 365 account. Free includes 50 counted provider actions/month. Current request limits are 60/minute on Free and 120/minute on Pro; plan and abuse controls can further limit use. See [pricing](https://pearmcp.com/pricing). Meta controls Muse regions and access. - OAuth is not offered in this submission. Pear supports PKCE for registered clients, but has no verified Muse callback or published Muse client ID. Do not invent a registration or substitute another client's ID. Pear's `/openapi.json` documents its MCP HTTP endpoint, not a separate provider REST API. Select Existing MCP, not Raw API, in the connector submission. **Status:** submitted to Meta on 21 September 2026; Meta review, directory approval and authenticated Muse end-to-end testing remain pending. Local route tests use synthetic credentials and providers. They do not establish live Muse compatibility. ## Muse Code manual setup 1. Follow Meta's current Muse Code installation and sign-in documentation. 2. Sign in to Pear, connect Apple iCloud or Microsoft 365, and get your Pear API key from Settings. This is not your Meta API key. 3. Merge the following into private user settings at `~/.config/muse/settings.json` or `$XDG_CONFIG_HOME/muse/settings.json` if set. Keep your existing settings and MCP servers. If your file uses the older `mcp_servers` key, rename it to `mcpServers` first, merging existing servers into one object. Never keep both keys: Muse Code disables all MCP servers for that session when both are present. ```json { "schema_version": 1, "mcpServers": { "pear": { "type": "streamable-http", "url": "https://pearmcp.com/api/mcp", "headers": { "Authorization": "Bearer YOUR_PEAR_API_KEY" } } } } ``` Replace the key marker locally. Muse Code 1.3.0 sends HTTP header values literally: `${PEAR_API_KEY}` does not expand there. Keep the actual key in private, access-restricted user settings, outside shared project files and source control. Never paste it into a chat. If private static-key storage is unsuitable, choose another documented Pear client with an environment-backed key or OAuth path. Pear does not expose Dynamic Client Registration and has no published Muse OAuth Client ID. Do not substitute a generic `muse mcp login pear` command for the documented static-header path. 4. Restart Muse Code. Inspect `/mcp` for Pear's connection status and tools. 5. Ask Muse Code to call `pear_provider_status` and report ready accounts and services without changing anything. Resolve missing tools or authentication errors before asking for provider data. This is a documented configuration candidate, not a completed interoperability test. No Muse Code host version, authentication lifecycle, provider read or write has been verified by Pear for this guide. ## Useful first requests After the connection is working, begin with a read: find a free hour in your calendar, summarize a known email in Outlook, or list overdue Microsoft To Do tasks. These are example requests, not verified Muse results. Specify the account and timezone when relevant. Review the recipient, dates and content before approving writes. Tools depend on your providers, permissions and plan. The AI client decides when to invoke them. Apple Calendar, Contacts and Mail are supported. Apple Reminders is limited to legacy CalDAV lists; the upgraded Apple Reminders store is inaccessible to Pear. Microsoft To Do is unaffected. Google Workspace is coming soon. Read [Pear data handling](https://pearmcp.com/data-handling), [compatibility](https://pearmcp.com/mcp-compatibility), [Apple setup](https://pearmcp.com/icloud-mcp-server), and [Microsoft setup](https://pearmcp.com/microsoft-365-mcp-server). ## Primary sources - [Meta Muse launch](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/) - [Muse Connector Platform](https://muse.ai/platform) - [Meta Muse connectors](https://www.meta.com/en-gb/help/artificial-intelligence/1687253048996149/) - [Muse Code MCP reference](https://meta-models.github.io/muse-code-sdk/next/guides/extend/mcp-servers/) - [Muse Code settings](https://dev.meta.ai/docs/muse-code/configuration) - [Muse Spark 1.3](https://research.meta.ai/blog/introducing-muse-spark-1-3) Pear is independent of Meta. This guide does not imply a partnership.