Skip to content
Pear
Jolly, Meta’s Muse character, at a laptopMuse

Meta’s next chapter. Your everyday apps.

Muse,
meet Pear.

A guide to Meta’s personal agent, its coding companion, and where your iCloud and Microsoft 365 accounts fit in.

Explore Muse Code setup Using the Muse app?

Muse connector: submitted to Meta on 21 September 2026. Review, approval and live Muse testing are pending.

First, meet the family

One name. Three different roles.

The app you use determines how you connect. A model’s tool skills don’t tell you which integrations its host app offers.

The coding companion

Muse Code

Runs in your terminal and supports remote MCP servers. This is the surface covered by the Pear configuration below.

See the manual MCP setup
The model family

Muse Spark

Meta’s model family. Spark 1.3 is available through Muse Code and Meta Model API; your agent application supplies its tools.

Read Meta’s model introduction

For the Muse app

One connection. Your everyday apps.

Read the connector details

Muse can work across connected apps and continue tasks in the background. Its September launch announced a US rollout; check Meta for current availability.

Meta’s Connector Platform accepts an Existing MCP endpoint for review. Pear already provides a hosted MCP service for connected iCloud and Microsoft 365 accounts. Its submission uses API-key authentication.

Pear is not yet an approved Muse directory connector. Submission and a working Muse account connection are separate steps. Until those are complete, use Muse’s available connectors or the Muse Code setup below. See Meta’s connector platform.

Connector details

Built on Pear’s hosted MCP.

The connector uses the same authenticated endpoint and account permissions as other Pear clients. Meta’s review and live Muse testing remain open.

Connect securely

Endpoint: https://pearmcp.com/api/mcp. Use Streamable HTTP with your own Pear API key in the Authorization: Bearer header. Add it through Muse’s secure credential setup when that connection is available, never in chat.

Data handling and permissions

Discover, then read

Initialize MCP, list the tools available to your account, then call pear_provider_status. Connected providers, scopes and plan determine which tools appear. Start with a calendar or task read.

Explore Pear’s tools

Review changes first

Before sending or changing anything, review the exact account, recipient, dates and content. Use Pear’s draft and approved-write flow when available. An interrupted write can have an unknown outcome; check before retrying.

How Pear records approvals

Requires a Pear account and a connected provider. Free includes 50 counted provider actions per month; Pro raises the plan limits. Muse access and availability are controlled by Meta. Pear has no registered Muse OAuth client, so OAuth is not part of this submission.

For the terminal

Give Muse Code a view of your day.

Pear connects Apple iCloud and Microsoft 365 to compatible MCP clients. Muse Code documents the transport and static headers needed for a manual connection.

Manual setup · connection unverified

These steps follow Meta’s Muse Code 1.3.0 reference. Pear has not completed an authenticated Muse Code connection or read/write test.

See Pear’s compatibility status

  1. Connect your account in Pear

    Create your Pear account, then connect Apple iCloud or Microsoft 365. Get your Pear API key from Settings. It is separate from your Meta model API key.

    Install and sign in to Muse Code using Meta’s current setup instructions.

  2. Add Pear to your private settings

    Merge this entry into your personal ~/.config/muse/settings.json, or $XDG_CONFIG_HOME/muse/settings.json if set. Preserve your other settings and 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.

    {
  "schema_version": 1,
  "mcpServers": {
    "pear": {
      "type": "streamable-http",
      "url": "https://pearmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PEAR_API_KEY"
      }
    }
  }
}

    Replace YOUR_PEAR_API_KEY locally. Muse Code 1.3.0 reads HTTP headers literally; an environment-variable reference here will not work. Keep this key in your private, access-restricted settings file, outside shared projects and source control. Never paste it into a chat.

    Prefer OAuth or an environment-backed key? Use another documented Pear client for now. Pear has no dynamic client registration endpoint or published Muse OAuth Client ID, so Muse’s default OAuth sign-in is not a documented Pear setup.

  3. Restart, then check the connection

    Start a fresh Muse Code session. Open /mcp and inspect Pear’s status and tools. Before requesting any provider data, ask:

    Call pear_provider_status and tell me which accounts and services are ready. Don’t change anything.

    A missing server or an authentication error is a setup failure. Check your settings path, the header value and the API key locally. Don’t treat an empty tool list as a connected account.

Once your connection is working

Less switching. More of your day.

Start with a read in Muse Code. These are example requests for connected accounts, not results from a verified Muse session.

Make a little room.

Find the space between your meetings.

Check my work calendar tomorrow. Where could I fit an hour of focused work? Don’t book anything yet.

Find the full story.

Bring the relevant mail into your session.

Find the latest email about the launch in my Outlook inbox. Summarize what I need to know.

See what comes next.

Keep your Microsoft To Do tasks in view.

Show my overdue Microsoft To Do tasks and help me choose what to tackle first.

Your accounts.
Your call.

How Pear handles your data

Available tools depend on your connected providers, permissions and plan. Review recipients, dates and content before approving a write. The AI client decides when it calls Pear’s tools.

Apple Calendar, Contacts and Mail are supported. Apple Reminders is limited to legacy CalDAV lists; Pear cannot access Apple’s upgraded Reminders store. Microsoft To Do is unaffected. Google Workspace is coming soon.

Read the Apple Reminders limitation

Grounded in the docs

The sources behind this guide.

Checked 21 September 2026. Product access and client behavior may change. Pear is independent of Meta; this page does not imply a partnership.

Bring your own AI

Your apps have more to give.

Choose the client and connection path that fit you.

Find your setup guide Explore Pear plans