MCP · Model Context Protocol

Talk to your habit data

Habit Pocket hosts an MCP server, so you can connect Claude, ChatGPT, or any MCP-capable AI assistant straight to your own habits. Say “log 8 hours of sleep”, ask “do I sleep better on days I run?”, or have it build a chart. Nothing to install, your data stays yours, and it's part of Pro.

Get Started for Free

5 habits free. No credit card. Sync is free.

The server

One URL, hosted by us.

There's no bridge to download and no process to keep running. The server lives next to your data and speaks standard MCP over HTTP, so any client that supports remote MCP servers can connect to it.

MCP server URL

https://api.habitpocket.io/mcp

Two ways in, depending on your client: the OAuth consent flow (claude.ai custom connectors — you approve access in your browser, no key handling), or an API key from Settings → Integrations for clients where you configure headers yourself.

Set up · claude.ai

Connect from claude.ai in about a minute.

Custom connectors use the OAuth flow: claude.ai discovers the server, sends you to a Habit Pocket consent page, and you approve. No key to copy.

Open connector settings
In claude.ai, go to Settings → Connectors → Add custom connector.
Paste the server URL
https://api.habitpocket.io/mcp — name it Habit Pocket.
Approve access
Claude sends you to a Habit Pocket page that shows exactly what access means. Sign in if you aren’t already, hit Approve, and you land back in Claude, connected.
Say something
Try: “How’s my week going?” Claude pulls your stats and answers from your real data.

Set up · ChatGPT

ChatGPT works the same way.

ChatGPT's connectors speak the same protocol and use the same approval flow — the steps just live in a different menu.

Add a connector
In ChatGPT, go to Settings → Connectorsand create a new connector (on some plans this lives under developer mode).
Paste the server URL
https://api.habitpocket.io/mcp — name it Habit Pocket and pick OAuth authentication.
Approve access
ChatGPT sends you to the same Habit Pocket consent page; approve and you’re connected. Enable the connector in a chat and ask away.

Set up · Claude Code, Cursor & friends

Everywhere else: one key, one header.

Clients where you configure servers yourself connect with an API key. Create one in the app under Settings → Integrations, then send it as a Bearer token.

Claude Code

claude mcp add --transport http habit-pocket https://api.habitpocket.io/mcp \
  --header "Authorization: Bearer mp_live_xxxxx"

The same shape works in Cursor and any client that supports remote MCP servers with custom headers: transport http, URL https://api.habitpocket.io/mcp, header Authorization: Bearer mp_live_xxxxx. Revoke the key in Settings and access ends immediately.

Capabilities

Eleven tools, honest boundaries.

Reads cover everything — habits, entries, stats, sections, charts. Writes are deliberately additive: log and clear daily values, create habits, add charts. Editing, archiving, and deleting what you built stays in the app, so an over-eager assistant can never restructure your tracker.

Tool	Access	What it does
get_account_context	read	Your timezone and today’s date — so “yesterday” lands on the right day.
list_habits	read	Your habits with types, targets, and streaks.
get_entries	read	One habit’s daily values across a date range.
get_all_entries	read	Every habit’s values in one call — the workhorse for “analyze my week”.
get_stats	read	Streaks, completion rates, perfect days — the app’s own numbers.
log_entry	write	Set a habit’s value for a day.
clear_entry	write	Remove a day’s value.
list_sections	read	Your habit groups.
create_habit	write	Create a new habit, any of the four types.
list_charts	read	The chart cards on your dashboard.
create_chart	write	Add a dashboard chart — line, heatmap, summary, or candle.

Prefer raw HTTP? The identical contract is available as a REST API — MCP tools and API endpoints hit the same code path, so a value logged by your assistant syncs to your phone like any other entry.

Built-in prompts

One-click workflows.

Five prompt templates ship with the server — in Claude they appear in the “+” menu once connected. Each one drives the right tool sequence, so a weekly review is one click, not a paragraph of instructions.

weekly_review

What held, what slipped, streaks at risk, one focus for next week.

monthly_review

Trends over 30 days: direction per habit, best and worst weeks.

correlation_check

Do two habits move together? Honest analysis, lagged effects included.

streak_risk

Which streaks die today if you don’t act tonight.

habit_design

Design tracking for a goal, grounded in your actual follow-through.

Things to try

Say it like you'd say it to a person.

No syntax to learn. These all work on day one:

“Log 7.5 hours of sleep and mark meditation done for yesterday.”
“How’s my week going? Anything I should worry about today?”
“Do I sleep better on days I run? Check the last three months.”
“I was travelling this week — here’s what happened: ran Tuesday and Thursday, slept badly, about 6 hours a night. Fill in my habits.”
“Create a candle chart showing my sleep window from bedtime to wake-up, overlaid with sleep score.”
“Which of my targets are unrealistic based on my actual data?”

Privacy

You bring the AI. We never send your data anywhere.

Connecting via MCP is you authorizing your own assistant to reach your own account — Habit Pocket doesn't ship your data to any AI company, ever. Access is scoped to exactly your account, every write syncs visibly to your devices, and revoking the key or connector ends access immediately.

FAQ

MCP — common questions

MCP (Model Context Protocol) is the open standard AI assistants use to connect to outside tools. Once Habit Pocket is connected, your assistant can read your habits, entries, and stats, log values for you, and create habits and charts — by talking to it, no code involved. Habit Pocket hosts the server; nothing to install.

Anything that speaks MCP over HTTP. Claude (claude.ai custom connectors, the Claude mobile apps, Claude Desktop, and Claude Code) is the best-tested path, and ChatGPT connects the same way through its connectors with the same approval flow. Editors like Cursor and other MCP-capable clients work with an API key in the Authorization header.

Not by us, ever. Habit Pocket never sends your data anywhere. Connecting via MCP is you authorizing your own AI assistant to read your account — the same as handing a tool your API key. The conversation happens between you and your assistant; revoke access any time and it ends immediately.

It can only do what the tools allow: log or clear daily values, and create habits or charts. It cannot edit, archive, or delete habits, touch your account, or see anyone else’s data. Writes sync to your devices like normal entries, so anything it logs is visible — and fixable — in the app.

Yes — MCP access is part of Pro, same as the REST API. Connecting is free to set up; the tools check your plan when they run.

If you connected with an API key, revoke the key under Settings → Integrations and access ends immediately. If you connected through the consent flow (claude.ai or ChatGPT), remove the connector in the assistant’s settings; tokens expire on their own and can no longer be refreshed once the connector is gone.

Five habits. Thirty days.
See what shows up.

No credit card. Pick five habits. Come back in a month.