Two servers, and only one of them runs errands
Connecting only the docs server is the failure worth naming: the host reports success and no errand
can ever run. Add the execution server, with the
/mcp path.
Prerequisites
- A Hence account (step 1).
- A paid Claude plan — Cowork’s scheduled tasks are a paid-plan feature, and they run remotely.
- The Hence connector added on the same Claude account (step 2).
- Access enabled for your Hence account. You can connect without it; errands refuse until it is on.
Step 1 — Account
Create or sign in at https://app.usehence.com/sign-up. Expected outcome. You are signed in and can see your household in the Hence app.Step 2 — Connect
- Open https://claude.ai/settings/connectors.
- Choose Add custom connector and paste
https://mcp.usehence.com/mcp. - Complete the Hence sign-in and consent in the browser window Claude opens.
- Open Cowork from the Claude sidebar and confirm Hence is listed among the available connectors.
Step 3 — Verify
In a Cowork conversation, ask: “List my Hence tasks.” Expected outcome. An empty list. A clean refusal saying execution is not enabled for your account means the connection is good and access is not on yet.Step 4 — Your first errand
Three prompts, each with its published ceiling:- “What am I actually paying on my debts?” — ceiling: DONE. Hence reads APR, balance, minimum and promo end date at each servicer and returns a table. Nothing changes at any servicer.
- “Am I capturing my full 401(k) match?” — ceiling: READY for the read; DONE for the change behind approval. It reads the formula, proposes a rate, and changes it only on your explicit yes.
- “Ask my card issuer for a lower APR.” — ceiling: READY; DONE where the issuer answers in-session. It drafts the request and sends it behind a confirm step. The issuer may say no.
The scheduled check-in
This is what Cowork adds. Create a scheduled task with a prompt like:Every morning, ask Hence for new events and tell me what needs me.The scheduled run asks Hence for anything new since it last looked — an errand that finished, a question waiting on you, a watch that fired — and reports it through Cowork’s own notifications. Nobody has to be in the conversation when it happens. Expected outcome. A morning summary that is usually “nothing new”, and occasionally a finished errand or a question to answer. Two honest limits. The schedule is the host’s, and the finest is hourly, so this is a daily digest rather than an alert. And a question that arrives mid-errand pauses the scheduled run rather than completing it — the check-in surfaces the question, and you answer it in an ordinary conversation.