> ## 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 any MCP client

> The host-independent facts: the server URL, the auth shape, how to verify a connection, and what to expect when access is off.

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

This page is the generic version, for a client that is not one of the hosts with its own page. If
yours is [Claude](/connect/claude), [Cowork](/connect/claude-cowork),
[ChatGPT](/connect/chatgpt) or [Cursor](/connect/cursor), start there instead.

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

Both are real MCP servers and both will answer. A client that connects only the docs server reports
a healthy connection and can never run an errand, which is the single most common setup failure.
Add the execution server, including the `/mcp` path — a bare hostname does not handshake.

## Prerequisites

* A Hence account (step 1).
* An MCP client that supports **remote servers over Streamable HTTP** with **OAuth 2.1**. A
  stdio-only client cannot reach Hence, and there is no local bridge to install.
* A browser the client can open for the authorization step.
* 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

Point the client at `https://mcp.usehence.com/mcp` however it takes a remote server, and complete
the authorization in the browser. Hence is the resource server; authorization is OAuth 2.1 with
Hence's own identity provider, and the client registers by client-ID metadata document where it
supports that, by dynamic registration otherwise.

**Expected outcome.** The client lists the Hence tools, and the authorization is stored against your
Hence user rather than against a device.

## Step 3 — Verify

Call `list_tasks` with no arguments.

**Expected outcome.** A result carrying an empty task list. That is the pass condition — an empty
list means the connection, the authorization and the identity resolution all worked. 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.

Moving 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.** A durable task id, then a sequence of pending requests the client relays to
the user. The task id survives a disconnect; reconnect and read it again.

## Two relay paths

A client that can only call tools is a first-class citizen: call `start_task`, poll `get_task`,
show each pending request to the user in your own voice, and return the answer with `answer_task`.
Results reference the screenshots rather than carrying them; the image of a signed-in page stays on
our side.

A client that declares the richer extensions gets the same errand as a durable task handle, with
elicitation for questions and approvals and an inline task card. Nothing needed for an errand is
only available on that path.

## When it does not work

| Symptom                                          | Cause                                                      | Fix                                                                       |
| ------------------------------------------------ | ---------------------------------------------------------- | ------------------------------------------------------------------------- |
| Handshake never completes                        | The URL is missing the `/mcp` path                         | Use the full URL including `/mcp`                                         |
| Connected, but no Hence tools                    | The docs server was connected instead of the execution one | Connect `https://mcp.usehence.com/mcp`                                    |
| Tools are listed, but every call refuses cleanly | Execution is not enabled for your account yet              | Request access; the existing connection starts working when it is enabled |
| The client cannot complete authorization         | It does not support OAuth 2.1 for remote servers           | Use a client that does; there is no token to paste and no local bridge    |
| A task id stops resolving after a reconnect      | A different Hence account was authorized the second time   | Authorize with the account that started the task                          |
| The server 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 in these pages or in the flow they describe. No step asks your assistant to
act inside the Hence app on the user's behalf. **Signing up and approving the consent screen are the
user's hands only** — that is where things stand today, not a rule we are defending.