Connect Cursor

Not live yet, and not yet verified in Cursor. The execution connector at https://mcp.usehence.com/mcp is still being built, and Cursor is a compatibility target rather than the first host. The steps below follow Cursor’s documented remote-MCP configuration and have not been walked end to end.

Cursor reaches Hence as a remote MCP server over the network. There is no package to install and no local process to run.

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.

Adding only the docs server gives you a client that reports success and can never run an errand. Add the execution server, with the /mcp path.

Prerequisites

A Hence account (step 1).
Cursor, recent enough to support remote MCP servers with OAuth.
A browser for the consent screen.
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

Add Hence to your MCP configuration — ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project:

{
  "mcpServers": {
    "hence": {
      "url": "https://mcp.usehence.com/mcp"
    }
  }
}

Then open Cursor Settings → MCP, find hence, and complete the sign-in and consent in the browser window it opens. Expected outcome. hence shows as connected in the MCP settings pane with its tools listed.

Step 3 — Verify

In the chat pane, ask: “List my Hence tasks.” Cursor calls list_tasks. Expected outcome. An empty list — 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. Cursor reports a task id and relays Hence’s questions to you in the chat pane.

When it does not work

Symptom	Cause	Fix
`hence` never leaves a connecting state	The URL is missing the `/mcp` path	Use the full URL including `/mcp`
Connected, but no Hence tools listed	The docs server was configured instead of the execution one	Change the `url` to `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
No browser window opens for consent	The client did not start the OAuth flow	Reload the MCP server from Cursor’s MCP settings pane
Edits to `mcp.json` seem to do nothing	The file was not reloaded	Reload the server from the MCP settings pane, or restart Cursor
Cursor reports the server 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

{
  "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 — the mcp.json above carries a URL and nothing else. 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.

Start here

Connect

How tasks work

What Hence can do

Trust and control

Reference

Changelog

Connect Cursor

Two servers, and only one of them runs errands

Prerequisites

Step 1 — Account

Step 2 — Connect

Step 3 — Verify

Step 4 — Your first errand

When it does not work

For your agent

What these docs will not do

​Two servers, and only one of them runs errands

​Prerequisites

​Step 1 — Account

​Step 2 — Connect

​Step 3 — Verify

​Step 4 — Your first errand

​When it does not work

​For your agent

​What these docs will not do

Two servers, and only one of them runs errands

Prerequisites

Step 1 — Account

Step 2 — Connect

Step 3 — Verify

Step 4 — Your first errand

When it does not work

For your agent

What these docs will not do