Set up and use Ember
Ember is a chief of staff inside your own Claude. It keeps what you decide, promise and hand out, tells you each morning what needs you, and follows your team through. It runs on your own Claude plan (a paid plan is needed).
Connect Ember
1. On the web, once
- Open claude.ai, then Settings, then Connectors.
- Choose Add custom connector. Name: Ember. URL:
https://stanford.futurise.studio/mcp - Press Connect, sign in with your email and the six-digit code we email you, then press Allow.
2. Desktop app
- Open the Claude desktop app with the same account. Ember is already there.
- If it says Connect, open Settings, Connectors, Ember and press Connect.
3. iPhone and Android
- Sign in to the Claude app with the same account; Ember comes with it.
- Start a chat and say: Hey Ember. In voice mode, allow Claude to use Ember when it asks.
Then add the Ember skill: download it from your Ember page and upload it in Claude, Settings, Capabilities, Skills.
What to say
- “Hey Ember, brief me.” At most five things that need you, each with a one-word choice.
- “Rakesh will send the bank files by Friday.” Saved as a promise with an owner and a date.
- “Ask Himanshu to send the drawing to Mehta by Thursday.” A task, and a message drafted for you to send.
- “What did we agree with Mehta?” The answer, with where it came from.
- “I’m in Mumbai till Thursday.” Times and dates follow you.
Two scheduled tasks
Create them once in Claude (Scheduled tasks), paste the words and pick the schedule. They run on your Claude plan, even when your computer is off.
Ember morning brief (Weekdays, at your brief time (for example 07:30))
Use the Ember connector. Call ember_routine with name "brief_prep" and do exactly what it says. Give me the brief exactly as ember_brief returns it: at most five items, each with its owner and the numbered choices. Never send any email or message; drafts only. When done, call ember_routine_report with name "brief_prep".Ember mail check (Hourly (during working hours if Claude offers it))
Use the Ember connector and my Gmail connector. Call ember_routine with name "inbox_check" and do exactly what it says. Never send, delete, archive or label any email; create Gmail drafts only. When done, call ember_routine_report with name "inbox_check". If there is no new mail, report zero and stop.What Ember can do
| Tool | What it does | Changes data |
|---|---|---|
| Start Ember ember_start | Use at the start of an Ember conversation (the user says "Hey Ember", or asks about their business, people, tasks, promises, mail or meetings). Returns who the user is, their local date, time and place, how Ember presents results, what Ember cannot see yet, and whether the Ember skill is out of date. | No |
| Ember help and unblock ember_help | Use when a task needs a connector that is off, when the user says something is wrong, or to set up the scheduled tasks. Returns one line on what is missing and at most three short steps, plus Ember's health (last brief, last mail check). | No |
| Remember a fact, preference or note ember_remember | Use when the user tells you something to keep: a fact about the business, a preference, a person, a note. Store each item separately (up to ten). | Adds |
| Recall from Ember's memory ember_recall | Use when the user asks what Ember knows: about a person, a promise, a decision, what was agreed. Searches facts, promises, decisions, tasks and meetings the user may see. | No |
| Correct Ember ember_correct | Use when the user says Ember got something wrong, or says always or never about how Ember works. Fixes the item if a ref is given and records the correction. | Yes, asks first |
| Add a promise, decision or hold ember_commitment_add | Use whenever the user makes or receives a promise, takes a decision, or puts something on hold ("I will decide after the quote"). Every promise needs an owner and a date: if either is missing the item is saved and a question is returned; ask it. | Adds |
| List promises and decisions ember_commitment_list | Use to show open promises, decisions and holds, with their age. Filters by kind, state, owner, counterparty; overdue_only shows only past-due ones; holds_older_than_hours shows aged holds. | No |
| Update a promise or decision ember_commitment_update | Use when the user says a promise was kept, missed or released, a decision was taken, or a date moved. Never mark a promise kept unless the user said so. | Yes, asks first |
| Hand a task to a person ember_delegate | Use when the user hands work to someone ("ask Himanshu to send the drawing to Mehta by Thursday"). Records the task with assignee and due date, and returns a drafted message to the assignee for the user to send. | Adds |
| Follow-through on delegated work ember_delegations | Use to see what was handed out and how it is going: done, slipping, blocked, waiting. slipping_only shows past-due open tasks. | No |
| Update a delegated task ember_delegation_update | Use when a task moves: started, blocked, done, cancelled, new date (with a reason), or when the user wants a nudge drafted. Never sends anything: drafts only. | Yes, asks first |
| My tasks ember_my_tasks | Use when a team member asks what is on their plate. Returns tasks assigned to the signed-in person. | No |
| Morning brief: what needs you ember_brief | Use when the user asks for the brief, "what needs me", or at the start of the day. Returns at most five items (enforced), each with what, owner, numbered one-word choices and source, plus counts and what Ember could not see. | No |
| Answer a brief item ember_brief_decide | Use when the user answers a brief item ("1 done", "push 2 to Friday"). Applies the choice to the underlying promise, task, mail or meeting. | Yes, asks first |
| Prepare for a meeting ember_meeting_prep | Use before a meeting. Give the title, day and the people. | Adds |
| Capture a meeting ember_meeting_capture | Use after a meeting with the commitments you extracted from the notes or transcript. Each commitment needs an owner and a date; those without get a question back. | Adds |
| Get a routine's procedure ember_routine | Use when the user's Ember scheduled task runs (name inbox_check or brief_prep). Returns the steps of that routine, its budget (how much mail to read), and where the findings are reported. | No |
| Report mail findings to Ember ember_inbox_ingest | The mail check calls this with what it found: per thread the sender, a summary of at most 200 characters, dates and amounts, whether it needs a reply, and whether a draft was made in Gmail. Never send mail bodies. | Adds |
| Mail that needs the user ember_inbox_state | Use when the user asks about mail. Returns the mail Ember holds from the scheduled checks, needing a reply first, with draft status. | No |
| Report a routine run ember_routine_report | The scheduled task calls this last, with counts, errors and hints (for example "plan limit reached"). This is the heartbeat Futurise watches. | Adds |
| Where the user is ember_location | Use when the user says where they are or will be ("I'm in Mumbai till Thursday", "back in Raipur", "my home is Raipur"), or when their calendar shows travel. Sets their current city and time zone until an end date (then Ember is back to home on its own), or their home. | Yes, asks first |
| Team ember_team | Owner only. List the team, or add a member by email (they then sign in to their own Ember with that email and see the tasks given to them). | Yes, asks first |
What Ember never does
- It never sends anything for you. Replies and messages are drafts; you press send.
- It never gives medical or investment advice.
- It never scrapes LinkedIn or gets around CAPTCHAs.
- It never tracks your location; it knows only what you tell it or what your calendar shows.
Help
Say “Hey Ember, something is wrong” for the quick fix, or write to hello@futurise.studio. Read how we handle your data in the privacy policy.