Your practice, available to your assistant

1. In Claude, open Settings or Customize → Connectors, then choose Add custom connector.
2. Name it miracle.fyi and enter the exact server URL: https://miracle.fyi/mcp.
3. Select Connect. Sign in to miracle.fyi in the browser window and review the requested scopes.
4. Approve mcp:read to read your practice. Approve mcp:write only if you want the assistant to make changes.
5. Back in the conversation, enable miracle.fyi and ask: Which Miracle account and timezone are connected? Claude should use get_profile before the first write.

OAuth keeps your password out of Claude. Disconnecting removes the connection stored by that client, and each issued access token expires after one hour. Disconnecting is not a server-side revocation endpoint, so contact support immediately if an OAuth token may have been copied or exposed. The production resource URL must include /mcp exactly.

MCP Inspector and compatible developer clients can use a dedicated miracle.fyi API token instead of browser OAuth.

1. Open miracle.fyi, then go to Settings → AI tools.
2. Create or copy the dedicated AI tools token. This token is separate from your email-to-inbox address.
3. Set the MCP endpoint to https://miracle.fyi/mcp and send Authorization: Bearer YOUR_TOKEN as a request header.
4. Call initialize, then tools/list. The current server advertises 37 tools.

Treat the token like a password. Do not put it in a URL, screenshot, source file, chat message, or log. Rotate it immediately from AI tools if it may have been exposed.

An API-token Inspector run is developer diagnostics, not proof of a fresh OAuth connection. Connector-directory review evidence must come from a newly authorized reviewer session in interactive Inspector.

The supported public connector is the exact URL https://miracle.fyi/mcp. It updates automatically and uses Miracle's scoped first-party OAuth flow. There is no official Miracle npm package today, so do not install packages that merely look official.

If a verified local stdio package is published later, this guide and the developer overview will name and link it directly.

• Profile, 1 tool: confirm the connected account and timezone before making changes.
• To-dos, 10 tools: list, create, read, edit, move, complete, reopen, archive, restore, and permanently delete archived items.
• Habits and pacts, 12 tools: read active or archived commitments, create free habits and pacts, check in, edit, archive, restore, delete, and read 90-day statistics.
• Goal Grid, 4 tools: read or update the five goal levels and record, list, or remove dated check-ins.
• 3·6·9 Journal, 2 tools: read one real day and set one explicit journal line.
• Vision board, 4 tools: list items and create, update, or delete phrase-only extras.
• North Star, 2 tools: read or update the sentence with conflict protection.
• Time on Earth, 2 tools: read or update the configured headline and lifespan fields with conflict protection.

Each tool has a human-readable title, a narrow input schema, a structured output schema, a single read or write scope, and safety annotations that tell a compatible client when approval is required.

• “Show my In Progress and Today items, then identify the clearest next action.”
• “Create a Priority to-do called Prepare the board packet, with a checklist for the cover memo, exhibits, and final review.”
• “Read my Goal Grid and tell me whether today’s plan supports my monthly goal. Do not change anything.”
• “Show my free habits and their 90-day completion statistics.”
• “Read today’s 3·6·9 journal progress and tell me which session is next.”

For a write, ask the assistant to read the current record first and preserve its returned conflict token. Use a unique idempotency key when repeating a create request after a timeout.

The MCP surface is deliberately not a billing control plane. It cannot create, change, activate, pause, or end a money stake; accept paid terms; add or change a payment method; create or resolve a dispute; create, retry, reconcile, refund, or cancel a charge; or initiate Stripe or Connect flows.

Pact mutations are restricted to owner-controlled free commitments. A check-in may record that an existing commitment was completed, but it cannot create or increase financial exposure. Permanent deletes require an archive first. Conflict-protected Goal Grid, journal, North Star, and Time on Earth writes can refuse stale changes instead of overwriting newer work.

miracle.fyi does not proactively send account content to an MCP client. After you connect and approve scopes, the client can request the specific records its enabled tools expose and can send approved changes back. The client provider processes returned data under its own privacy terms.

Read the complete Privacy Policy. For account, product, or security concerns, use the support form or email claycollins@gmail.com.

• Authentication fails: confirm the endpoint is exactly https://miracle.fyi/mcp, disconnect the connector, and complete a fresh OAuth connection.
• You see fewer than 37 tools: the client has stale connector metadata. Disconnect it, remove the custom connector, and add it again.
• A write returns insufficient_scope: reconnect and approve mcp:write, or keep the connection read-only by design.
• A write reports a conflict: read the record again and retry with the new updated_at or expected-text value. The first write was not silently overwritten.
• A due item appears in Today: this is intentional. Due and overdue active items resolve to Today unless they are In Progress.
• The wrong account is connected: call get_profile, disconnect, sign out of the unintended miracle.fyi account, and reconnect in a private browser session.
• An API token fails: rotate it in Settings → AI tools and update the client’s Authorization header. Never add the token to the server URL.

Start at the Developer Center, explore the human API reference, inspect the machine-readable OpenAPI contract, or give an agent the compact llms.txt overview.