Ambi, in your AI

Connect Claude, ChatGPT or any MCP app to Ambi. Plan your week in a chat on your computer; it is on your phone when you pick it up.

https://app.ambiai.app/mcp

Connect

ClaudeSettings → Connectors → Add custom connector → name Ambi, the URL above → Connect, sign in, allow. Also in Claude Desktop and the Claude app.

ChatGPTSettings → Apps & Connectors → Advanced settings → Developer mode on → Create: name Ambi, the URL above, authentication OAuth → sign in, allow.

Claude Codeclaude mcp add --transport http ambi https://app.ambiai.app/mcp, then /mcp → ambi → sign in.

Cursor, VS Code…Add a remote MCP server: { "mcpServers": { "ambi": { "url": "https://app.ambiai.app/mcp" } } }. The app opens the sign-in page itself.

What to ask

“What’s on my plate today?”Your day, in the order Ambi shows it.

“Plan my week from my goals.”Proposes days from your goals and Later, writes what you agree to.

“I want to run a half marathon in March.”The goal with its steps, milestones and a running habit.

“I ran 8 km this morning.”Checks your Run habit with 8 km.

“My tracker syncs to this file. Check Run when I run 3 km.”A connection, an automation, and the data sent in.

“How was my month?”Streak, things done, focus hours, goals reached.

Your data

Your AI can bring in data Ambi does not collect itself: a watch, a running app, a sleep tracker, a script of your own. Tell it where the data is. It creates a connection with its own key, sends the data points through it, and sets up automations (if I run 3 km or more, check Run) that you can see and edit in the dashboard. An automation fires at most once a day, acts like your own tap, never replaces a check already there and never re-checks a day you unchecked.

A script sends data points with the connection's key:

curl https://go.ambiai.app/signals \
  -H "Authorization: Bearer ambi_…" \
  -H "Content-Type: application/json" \
  -d '{
    "workouts": [{ "external_id": "run-0816", "type": "run",
                   "started_at": "2026-08-16T15:44:04+02:00",
                   "duration_min": 40.9, "distance_km": 4.448 }],
    "sleep": [{ "external_id": "night-0913",
                "started_at": "2026-09-13T00:02:00+02:00",
                "ended_at": "2026-09-13T07:30:00+02:00", "total_min": 439 }],
    "daily": [{ "day": "2026-09-13", "metric": "steps", "value": 9214 }]
  }'

workoutsexternal_id type started_atduration_min · distance_km · kcal · avg_hr · steps

sleepexternal_id started_at ended_attotal_min · deep_min · rem_min · score · kind

dailyday metric valueunit

Times carry their offset. Up to 500 rows a request. The same external_id sent again replaces the earlier one. A point dated more than 10 minutes ahead is refused.

Tools

get_today

The user's day in Ambi, in the order the app shows it: habits due today, the next step of each active goal, and the tasks dated today; timed items first.

get_day

The list for another day, past or future, same shape as get_today.

list_later

The tasks waiting outside the next 7 days, as the app's Later screen splits them: overdue (dated before today and not done), no day, and coming up (dated after the next 7 days).

list_goals

The goals, active ones first: progress (steps done of total), the next open step, the deadline, and the habits that feed each goal.

get_goal

Everything about one goal: why, deadline, status, its steps in order (done or not, with ids for complete_step), its milestones (dated thresholds), the habits that feed it with their streaks, and its open tasks.

list_habits

The habits: their days ('every day' or a list of weekdays), reminder time, daily amount (e.g. 20 pages, 30 min, 1 time), goal, current streak (scheduled days in a row, today not counted against it until it ends), this week's done/scheduled, whether today is checked, and the automations that check it by themselves.

get_stats

The figures of the app's Profile: the current streak (days in a row with at least one thing done), the best streak, things done (tasks, steps and habit check-ins), focus time from Ambi's focus timer, and goals reached, over all time or the last 30 or 7 days.

add_task

Adds a one-off task.

update_task

Changes a task: only the fields given change.

move_task

Gives a task another day, or none (null) to send it back to Later.

complete_task

Marks a task done.

uncomplete_task

Marks a done task as not done.

delete_task

Deletes a task.

add_goal

Creates a goal, optionally with everything it needs in one go: a deadline, the reason (why), its steps in order (concrete pieces of work; the app shows the next open one on Today, one per day), habits that feed it, and milestones (dated thresholds, e.g. 'Run 10 km' by a date).

add_step

Adds a step at the end of a goal's plan.

complete_step

Marks a goal's step done.

uncomplete_step

Marks a goal's step as not done.

add_habit

Adds a habit: something done on fixed weekdays (every day when days is omitted). amount is what one day asks, as target + unit (min, times, pages, km); default 1 time, i.e. just do it. time sets a daily reminder on those days.

check_habit

Marks a habit done for a day: today by default, or a past day up to 30 days back (never a future day). value records how much was done in the habit's unit (e.g. 8 for 8 km); below the target the day counts as worked but stays open in the app.

uncheck_habit

Removes the check of a habit for a day (today by default).

list_connections

Where the user's outside data comes from: official integrations and their custom connections ('My tracker'), each with the start of its key and when it last sent data.

create_connection

Creates a custom connection for a source of data the user named ('My watch', 'Strava export', 'Screen time'), with its key.

log_signal

Sends data points to Ambi through one of the user's connections: workouts, sleeps, or a day's metrics (steps, game_hours…).

list_automations

The user's automations: 'if X then Y' rules that act on their connections' data, e.g. if a run of 3 km or more, check the habit Run.

create_automation

Creates an 'if X then Y' automation on the user's data: when a day's data meets the trigger, Ambi does the actions for that day, like the user would (a habit checked this way looks like a tap).

update_automation

Changes an automation: its name, trigger (when), actions (then), or turns it on or off (enabled).

delete_automation

Deletes an automation.

test_automation

Checks a trigger against the data already received for a day (today by default) without saving anything: whether it is met, and by which value.

Privacy

What your AI sees. Your plan in Ambi: tasks, goals with their steps and milestones, habits and their check-ins, automations, the figures of your Profile. Not your chats with Ambi, your photos or your email.

Where it goes. To the AI app you connected, under its own terms. Ambi sees the tool calls, never your conversation.

What it can change. What you can change in the app. Every change reaches your phone like one made on another of your devices.

Stop. Remove the Ambi connector in your AI app; an access nobody uses expires after 30 days. A revoked key stops at once. Deleting your Ambi account removes everything.

Terms · Privacy Policy · contact@ambiai.app