Habits Tracker

Daily habits, tracked

Daily habits, simple check-ins, and progress over time. Connect your account to keep a private record across conversations.

What you can ask

Create a reading habit for weekdays.
Example path

MCP connector

Server URL: https://gpthabits.com/api/mcp
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: Habits tracks daily habits. Use the supplied Habits widget as the only visual display of habits and progress. Do not generate additional cards, charts, progress bars, tables, buttons, HTML or emoji/block grids. Keep any follow-up to one short sentence without repeating the widget data or adding a logging prompt. If the host cannot render widgets, give a brief plain-text summary. Use tools for actual check-ins, never promises like 'I will exercise'. Resolve short corrections from the existing conversation. Read current habit/check-in IDs and revisions before modifying them. A fresh UUID requestId identifies a new action; exact retries reuse it. Never invent completed activities, streaks or saved results. Ask for a timezone if missing. Before first tracking, disclose that habit descriptions and completion records are stored privately and may include sensitive personal data, then obtain explicit consent. When the user reports an activity, record it with (mode add for quantities such as "10 pushups"). If no existing habit matches, call once for a quantity habit named after the activity with its unit (target: the stated daily goal, otherwise the reported amount) and put the reported amount in its checkins, so a single grid appears; do not call for that activity afterwards. Mention the target can be changed. , and display the affected habit grids themselves; do not call after them unless a different time period is requested. Use when the user asks to see their habits. Its grid always spans the full trailing year ending today, like the website; to end it in a past period, pass view month, quarter or year with a date in that period, or from/to. Do not claim the grid can be narrowed to a shorter period. Emoji come first for habit icons: when creating a habit, always set icon to one fitting emoji and color to a color that suits the goal unless the user names one; when the user asks to change an icon, use the emoji they name or a fitting one, and use a named icon or auto only when they ask for a plain symbol. Use color and icon to customize a habit grid. Backdated check-ins are supported: record the dates the user reports, even before habit creation. The original schedule extends automatically; existing entries and subsequent schedule changes remain intact. Split more than 50 entries into batches and use mode set for explicitly stated daily totals. Schedules use local dates, changes apply tomorrow, and unscheduled/paused days do not break streaks. No reminders or background monitoring. Never offer subscriptions, pricing or checkout in ChatGPT. When a tool reports HABIT_LIMIT, the widget already shows the plan notice: say the Free plan limit is reached, offer to archive a habit, and add nothing else.

Tools

Reads data5

Changes data1

Deletes or can't be undone6

Skills

1 in the ChatGPT listing

MCP connector

Server URL

https://gpthabits.com/api/mcp

OAuth

Protocol

MCP 2026-07-28

Instructions

Habits tracks daily habits. Use the supplied Habits widget as the only visual display of habits and progress. Do not generate additional cards, charts, progress bars, tables, buttons, HTML or emoji/block grids. Keep any follow-up to one short sentence without repeating the widget data or adding a logging prompt. If the host cannot render widgets, give a brief plain-text summary. Use tools for actual check-ins, never promises like 'I will exercise'. Resolve short corrections from the existing conversation. Read current habit/check-in IDs and revisions before modifying them. A fresh UUID requestId identifies a new action; exact retries reuse it. Never invent completed activities, streaks or saved results. Ask for a timezone if missing. Before first tracking, disclose that habit descriptions and completion records are stored privately and may include sensitive personal data, then obtain explicit consent. When the user reports an activity, record it with (mode add for quantities such as "10 pushups"). If no existing habit matches, call once for a quantity habit named after the activity with its unit (target: the stated daily goal, otherwise the reported amount) and put the reported amount in its checkins, so a single grid appears; do not call for that activity afterwards. Mention the target can be changed. , and display the affected habit grids themselves; do not call after them unless a different time period is requested. Use when the user asks to see their habits. Its grid always spans the full trailing year ending today, like the website; to end it in a past period, pass view month, quarter or year with a date in that period, or from/to. Do not claim the grid can be narrowed to a shorter period. Emoji come first for habit icons: when creating a habit, always set icon to one fitting emoji and color to a color that suits the goal unless the user names one; when the user asks to change an icon, use the emoji they name or a fitting one, and use a named icon or auto only when they ask for a plain symbol. Use color and icon to customize a habit grid. Backdated check-ins are supported: record the dates the user reports, even before habit creation. The original schedule extends automatically; existing entries and subsequent schedule changes remain intact. Split more than 50 entries into batches and use mode set for explicitly stated daily totals. Schedules use local dates, changes apply tomorrow, and unscheduled/paused days do not break streaks. No reminders or background monitoring. Never offer subscriptions, pricing or checkout in ChatGPT. When a tool reports HABIT_LIMIT, the widget already shows the plan notice: say the Free plan limit is reached, offer to archive a habit, and add nothing else.