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

> Add Hence to ChatGPT as a custom connector, verify it, and run a first errand.

<Warning>
  **Not live yet, and not yet verified on ChatGPT.** The execution connector at
  `https://mcp.usehence.com/mcp` is still being built. ChatGPT is a compatibility target rather than
  the first host, so the steps below are written from ChatGPT's documented connector flow and have
  not been walked end to end. Treat anything that does not match what you see as this page's fault
  and tell us.
</Warning>

Hence is a remote MCP server. ChatGPT reaches it as a custom connector over the network; there is
nothing to install.

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

A host that connects only the docs server reports success while nothing can run. Add the execution
server, including the `/mcp` path.

## Prerequisites

* A Hence account (step 1).
* A ChatGPT plan that allows custom connectors, with developer mode enabled in settings.
* A browser, for the consent screen and for any sign-in Hence needs.
* 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://chatgpt.com/#settings/Connectors](https://chatgpt.com/#settings/Connectors).
2. Enable developer mode if custom connectors are not offered, then choose to add one.
3. Paste the URL exactly: `https://mcp.usehence.com/mcp`
4. Complete the Hence sign-in and consent in the window ChatGPT opens.

**Expected outcome.** Hence appears in your connector list, and its tools are selectable in a
conversation.

## Step 3 — Verify

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

**Expected outcome.** An empty list — you have no tasks yet, and an empty list is the pass
condition. 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.** ChatGPT reports a task id, then relays Hence's questions to you and returns
your answers.

## When it does not work

| Symptom                                                         | Cause                                                     | Fix                                                                       |
| --------------------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------- |
| No option to add a custom connector                             | Developer mode is off, or the plan does not allow them    | Enable developer mode in settings; check your plan                        |
| The connector adds 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 fails before any consent screen                          | The URL is missing the `/mcp` path                        | Use the full URL including `/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 connector is added but tools never appear in a conversation | The connector is not selected for that conversation       | Select Hence in the conversation's tool or connector picker               |
| ChatGPT reports the connector 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 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.