> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usehence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Claude Cowork

> Use Hence from Claude Cowork, including a scheduled check-in that reports what needs you without anyone in the conversation.

<Warning>
  **Not live yet.** The execution connector at `https://mcp.usehence.com/mcp` is still being built
  and does not answer. Step 1 works today; steps 2 to 4 are written for the moment it ships.
</Warning>

Cowork uses the connectors on your Claude account, so there is no second connector to add: connect
once, and Hence is available both in ordinary conversations and in scheduled tasks. Scheduled tasks
are the reason this page exists separately — they are how Hence reaches you after you have closed
the conversation.

## Two servers, and only one of them runs errands

| Server                         | What it does                                                      |
| ------------------------------ | ----------------------------------------------------------------- |
| `docs.usehence.com/mcp`        | Lets an assistant **read about** Hence — these pages, searchable. |
| `https://mcp.usehence.com/mcp` | Lets an assistant **act as you** — this is the connector to add.  |

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](https://app.usehence.com/sign-up).

**Expected outcome.** You are signed in and can see your household in the Hence app.

## Step 2 — Connect

1. Open [https://claude.ai/settings/connectors](https://claude.ai/settings/connectors).
2. Choose **Add custom connector** and paste `https://mcp.usehence.com/mcp`.
3. Complete the Hence sign-in and consent in the browser window Claude opens.
4. Open Cowork from the Claude sidebar and confirm Hence is listed among the available connectors.

**Expected outcome.** The connector shows as connected on your account, and Cowork lists the Hence
tools.

## 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.

An errand that moves an old 401(k) into a new employer's plan has a ceiling of **READY**: Hence
fills the distribution form to its review page and **stops before submitting**, handing you a
ready-to-finish form.

**Expected outcome.** Cowork reports a task id and relays Hence's questions to you as they arrive.

## 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.

## When it does not work

| Symptom                                       | Cause                                                        | Fix                                                                                              |
| --------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| Cowork lists no Hence tools                   | The connector was added on a different Claude account        | Add it on the account you use for Cowork                                                         |
| The connector adds but nothing can run        | The docs server was added instead of the execution server    | Remove it and add `https://mcp.usehence.com/mcp`                                                 |
| Every tool call refuses cleanly               | Execution is not enabled for your account yet                | Request access; the existing connection starts working when it is enabled                        |
| The scheduled task reports nothing, ever      | The schedule runs but there is genuinely nothing new         | Start an errand in a normal conversation first, then check the next morning                      |
| The scheduled task cannot reach the connector | Connector availability inside scheduled tasks varies by host | Run the check-in prompt in a normal conversation to confirm it works, then report the difference |
| Cowork says the connector is unreachable      | The execution server is not live yet                         | Nothing to fix on your side; see the banner at the top of this page                              |

## For your agent

```json theme={null}
{
  "connector": {
    "url": "https://mcp.usehence.com/mcp",
    "role": "execution",
    "transport": "streamable-http",
    "auth": "oauth2.1",
    "status": "not-yet-live"
  },
  "signup": {
    "url": "https://app.usehence.com/sign-up",
    "selfServe": "unconfirmed"
  },
  "verify": {
    "tool": "list_tasks",
    "arguments": {},
    "expect": { "tasks": [] },
    "refusedWhenAccessOff": true,
    "status": "not-yet-live"
  },
  "scheduledCheckIn": {
    "tool": "poll_events",
    "cadence": "hourly-or-slower, set by the host",
    "status": "not-yet-live"
  }
}
```

## What these docs will not do

No credential appears in these pages or in the flow they describe. No step asks your assistant to
act inside the Hence app on your behalf. **Signing up and approving the consent screen are your
hands only** — that is where things stand today, not a rule we are defending.