Connect Muse to Sundial Habits

You need a signed-in Sundial account and a Muse client that supports custom connectors. Each person connects their own account. Muse can read your habits, history, and streaks, and optionally record or undo check-ins.

1. Ask Muse to connectCopy Anchor Link

Copy this prompt into Muse. It contains no credentials:

Connect my Sundial Habits account.
Read https://docs.sundialhabits.com/connect-muse.md and walk me through setup.
Use https://docs.sundialhabits.com/openapi.json for the custom connector.
Ask for my access key through your secure credential prompt, never ordinary chat.
Call get_connection and confirm my account and permissions before using my habits.

Wait until Muse has its secure key field ready, then create your key in Sundial.

2. Create your connectionCopy Anchor Link

In Sundial, open You → Settings → Connected Apps. Name the connection Muse and choose:

• Read Only to ask about your habits, history, and streaks.
• Read and Record Check-ins to also check off or undo habits.

Both choices include private habits. Recording a shared check-in can notify friends under your existing settings. Select Create Connection. The key appears only once and expires in three years.

3. Enter the key and confirmCopy Anchor Link

Select Copy Access Key and paste it into Muse's secure key field. Keep the key out of ordinary chat, URLs, and source files. On iPhone, the copy button supports Universal Clipboard to your Mac when Handoff is available. The copied key expires from the clipboard after two minutes. Keep the one-time key screen open until Muse connects.

Muse should confirm your account, permissions, and expiry. Then try “What habits do I have today?” or “How is my walking streak going?” With check-in access, try “Mark my walk complete today.” If a name is ambiguous, choose the habit before recording a check-in.

If setup gets stuckCopy Anchor Link

• Connected Apps is missing: update Sundial to a build with Connected Apps, then open You → Settings.
• The clipboard is empty or the wrong text appears: copy the full key again while its screen is open. Do not copy another prompt between copying the key and pasting it into Muse.
• You dismissed the key, or it expired or was disconnected: disconnect the unused connection and create a replacement. Sundial cannot show an old key again.
• Muse cannot show a secure key field: stop setup and use a client with secure custom-connector credentials. Do not send the key in chat.

For connector clientsCopy Anchor Link

The production API origin is https://api.sundialhabits.com. Use the OpenAPI document for the available operations. Send Authorization: Bearer <ACCESS_KEY> and an identifying User-Agent, such as Sundial-Muse/1.0, on each request. Call get_connection first to confirm the account and access. Keep credentials in the client's secure credential store.

If even /health returns Cloudflare error 1010, check that the client sends an identifying User-Agent header. Cloudflare's Browser Integrity Check can reject requests with a missing or nonstandard user agent before they reach Sundial. Re-entering the key will not resolve that error.

Use remote Streamable HTTP at https://api.sundialhabits.com/mcp, with Authorization: Bearer <ACCESS_KEY> on every request. This endpoint uses pre-issued keys; it does not advertise OAuth login or registration. Read-only connections discover only read tools. The server checks permissions again when a tool executes.

DisconnectCopy Anchor Link

Open Connected Apps in Sundial and select Disconnect for this connection. Future requests are rejected. Information already read may remain in the assistant's history or memory. To reconnect, create a replacement key.

Meta describes custom connectors in its Help Center. Connection steps can vary by Muse client. On October 20, 2026, the Muse desktop client completed connection verification, habit reads, MCP tool discovery, and a user-requested check-in against Sundial's production API.