Momentum

Manage tasks, habits, routines

Create, review, update, complete, and delete your own Momentum tasks, habits, routines, daily habit progress, and private personal programs from your AI. Changes sync with the Momentum app and are limited to the signed-in user.

What you can ask

Show me all my current habits.
Example path →

MCP connector

Server URL: https://momentum-beb80.web.app/mcp
Login: OAuth
Protocol: MCP 2025-11-25
Instructions: Use Momentum tools only when the user asks to view or change their Momentum tasks, habits, routines, habit values, or private personal programs. returns habit definitions and tracking types, not daily logs. When the user asks what they logged, today's progress, or an individual habit's current value, call for each relevant habit; counter and timer logs include both a cumulative value and individual entries. Use to add an amount to a counter without replacing its existing total. To migrate old data, create or identify the destination habit, preview the date range and record count, obtain explicit confirmation, then call with one full-day snapshot per past date. Prefer detailed values or checklist selections when the source provides them; use completed alone for summary-only complex history and never invent missing details. Habit tools accept either habitId or an exact habitName; prefer habitId when it is already available. Use the user's IANA time zone whenever requested. A routine is a named grouping of habits, so link habits with routineId. Before authoring a program, call , then interview the user about their outcome, triggers, constraints, schedule, previous attempts, preferences, and difficult days. Use blueprintStartingPoints when a proven structure fits, but personalize it instead of copying it. Then ; follow lessonAuthoring and use slide_lesson whenever the program needs to teach, check understanding, or guide application instead of representing that learning as a checkbox. Show the canonical draft, warnings, and content hash and obtain explicit confirmation before create or revision apply. Connecting, interviewing, validating, and saving an unstarted personal-program draft are free. Creating a personal program saves it for review but does not start it, so do not ask for a start date or claim enrollment; tell the user to open Momentum, review the complete program, and tap Start my program. Momentum asks for Pro or an eligible free trial only at that point. Reuse idempotency keys on retries. Personal programs are private to the connected user and must never be described as public or shared. Ask for explicit confirmation before calling an import, delete, or clear tool, and never claim a write succeeded unless the tool confirms it.

Tools

Reads data9

Changes data7

Deletes or can't be undone12

Skills

None in the store listings or on the server

MCP connector

Server URL

https://momentum-beb80.web.app/mcp

OAuth

Protocol

MCP 2025-11-25

Instructions

Use Momentum tools only when the user asks to view or change their Momentum tasks, habits, routines, habit values, or private personal programs. returns habit definitions and tracking types, not daily logs. When the user asks what they logged, today's progress, or an individual habit's current value, call for each relevant habit; counter and timer logs include both a cumulative value and individual entries. Use to add an amount to a counter without replacing its existing total. To migrate old data, create or identify the destination habit, preview the date range and record count, obtain explicit confirmation, then call with one full-day snapshot per past date. Prefer detailed values or checklist selections when the source provides them; use completed alone for summary-only complex history and never invent missing details. Habit tools accept either habitId or an exact habitName; prefer habitId when it is already available. Use the user's IANA time zone whenever requested. A routine is a named grouping of habits, so link habits with routineId. Before authoring a program, call , then interview the user about their outcome, triggers, constraints, schedule, previous attempts, preferences, and difficult days. Use blueprintStartingPoints when a proven structure fits, but personalize it instead of copying it. Then ; follow lessonAuthoring and use slide_lesson whenever the program needs to teach, check understanding, or guide application instead of representing that learning as a checkbox. Show the canonical draft, warnings, and content hash and obtain explicit confirmation before create or revision apply. Connecting, interviewing, validating, and saving an unstarted personal-program draft are free. Creating a personal program saves it for review but does not start it, so do not ask for a start date or claim enrollment; tell the user to open Momentum, review the complete program, and tap Start my program. Momentum asks for Pro or an eligible free trial only at that point. Reuse idempotency keys on retries. Personal programs are private to the connected user and must never be described as public or shared. Ask for explicit confirmation before calling an import, delete, or clear tool, and never claim a write succeeded unless the tool confirms it.

Tools