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

> Add Hence to Claude on web or desktop as a custom connector, verify it, and run a first errand.

<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, and
  this banner comes down when it does.
</Warning>

Hence is a **remote MCP server**. Claude calls it over the network as a custom connector — there is
nothing to install, and the connector belongs to your Claude account rather than to a device.

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

The docs server is generated from this site and is genuinely useful; it is also the single most
common way to end up with a connector that reports success while nothing can run. **Add the
execution server.** Keep the `/mcp` path: a bare hostname never completes the handshake.

## Prerequisites

* A Hence account (step 1 below).
* A Claude account on Free, Pro or Max. Custom connectors with OAuth need no admin step on those
  plans, though Free allows only one custom connector at a time. On **Team or Enterprise**, a
  workspace owner has to add the connector first.
* Access enabled for your Hence account. You can connect without it; errands refuse until it is on.
* A browser. The consent screen and any sign-in Hence needs are completed by you, in your browser.

<Note>
  **Use a personal Claude account for the pilot, not a Team or Enterprise workspace.** Each tester
  adds the connector on their own account. That is what keeps the connector, the consent and the
  errand history attached to one person rather than to a shared workspace.
</Note>

## Step 1 — Account

Create or sign in to your Hence account 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.

<Note>
  **Whether you can sign up directly or must be invited is not settled yet.** The app gates access
  by list today, so a new account may land on the waitlist rather than in the product. This page
  will say which, plainly, once it is decided — it is not something to guess at, because a wrong
  answer here either turns away a tester or implies access nobody granted.
</Note>

## Step 2 — Connect

1. Open [https://claude.ai/settings/connectors](https://claude.ai/settings/connectors) — the same
   page Claude's own settings reach under Connectors.
2. Choose **Add custom connector**.
3. Paste the URL exactly: `https://mcp.usehence.com/mcp`
4. Claude sends you to Hence to sign in and consent. Approve the request.

**Expected outcome.** The connector appears in your list as connected, and Claude shows the Hence
tools in the conversation's tool list.

### What the consent screen is asking

The consent step is one sentence in plain words: *this assistant may run errands as me at Hence.*
Concretely, approving it lets the connector, on your behalf, check whether an errand is admissible,
start and cancel errands, read their state, and deliver answers and approvals you give in the
conversation. It does **not** hand your assistant your Hence password, your bank credentials, or a
token for any third party. Those stay on our side, and the sensitive ones never exist in the
conversation at all.

### Household selection

Errands run against a **household**, not just a login, because the accounts and the financial
picture belong to the household. If your Hence account belongs to exactly one household, that is the
one used, and you will not be asked. If it belongs to more than one, the first errand asks which one
to run against, as an ordinary question relayed through Claude.

## Step 3 — Verify

Ask Claude: **"List my Hence tasks."** Claude calls `list_tasks`.

**Expected outcome.** An empty list, phrased however Claude phrases it — you have no tasks yet. An
empty list is the pass condition. If instead you get a clean refusal saying execution is not enabled
for your account, the connection is fine and access is not on yet; see the failure table.

## Step 4 — Your first errand

Three prompts to start from. Each names its published ceiling, because the ceiling is what you are
actually delegating.

<AccordionGroup>
  <Accordion title="Find the rate on every debt I have — ceiling: DONE">
    *"What am I actually paying on my debts? I have a Chase card, a Discover card and the car loan
    with Ally."*

    Hence signs in at each servicer through a single-use page you complete, reads APR, balance,
    minimum, promo end date and whether the rate is fixed or variable, screenshots each account, and
    returns a table. Nothing changes at any servicer. Where a portal shows no rate at all, it asks
    you for that one number rather than guessing.
  </Accordion>

  <Accordion title="Capture my full 401(k) match — ceiling: READY for the read; DONE for the change behind approval">
    *"Am I capturing my full 401(k) match?"*

    Hence reads the match formula and your current deferral from the recordkeeper portal, works out
    the gap, and proposes a new rate. It changes the rate **only after you say yes** to a question
    that names the exact new number. Decline and nothing is changed.
  </Accordion>

  <Accordion title="Ask for a lower rate on a card — ceiling: READY; DONE where the issuer answers in-session">
    *"Ask Chase for a lower APR on my card."*

    Hence reuses the rate and account age it already read as leverage, drafts the request into the
    issuer's secure message centre, and sends it only behind a confirm step. The issuer may say no;
    that answer is recorded as the result.
  </Accordion>
</AccordionGroup>

If you want the one that shows the ceiling doing its job, ask about moving an old 401(k) into your
new employer's plan — **ceiling: READY**. Hence fills the old plan's distribution form to its review
page, screenshots it, and **stops before submitting**, because submitting is irreversible. You get a
ready-to-finish form and the last click stays yours.

**Expected outcome.** Claude reports a task id, then relays Hence's questions to you as they come
and returns your answers. The same task is visible in the Hence app.

## When it does not work

| Symptom                                                       | Cause                                                     | Fix                                                                                                                   |
| ------------------------------------------------------------- | --------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| The connector adds successfully but no Hence tools appear     | The docs server was added instead of the execution server | Remove it and add `https://mcp.usehence.com/mcp`                                                                      |
| Adding the connector fails before any consent screen          | The URL is missing the `/mcp` path                        | Use the full URL including `/mcp`                                                                                     |
| The tools are listed, but every call refuses cleanly          | Execution is not enabled for your account yet             | Request access. The connection stays valid and starts working the moment it is enabled — re-adding it changes nothing |
| Consent completes but errands run against the wrong household | Your account belongs to more than one household           | Answer the household question at the start of the errand, or leave the extra household in the app                     |
| **Add custom connector** is missing or disabled               | You are on a Team or Enterprise workspace                 | Ask a workspace owner to add it, or use a personal Claude account                                                     |
| Claude 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"
  }
}
```

## What these docs will not do

No credential appears anywhere in these pages or in the flow they describe — not a password, not a
one-time code, not an API key. Nothing here asks your assistant to act inside the Hence app for you.

**Signing up and approving the consent screen are your hands only.** That is where things stand
today, not a rule we are defending: an agent front door for signup is a live question, and this line
will change if it is answered that way.