Build your own UI

undrstand has no app of its own, and you do not have to write one. Connect Claude, then ask it to build the page you want: a timeline, a pattern board, a weekly review. This guide gives you the prompt and tells you what to expect.

The idea

undrstand is headless. It stores what you tell it and what it found, and answers over an API. It has no screens, on purpose: the right screen is the one you want, and Claude can build it for you.

You need two things: Claude connected to undrstand, so it knows what your data looks like, and a token, so the page it builds can read that data. Both take minutes.

Step 1: connect Claude

MCP — Follow the MCP guide to add undrstand as a connector in Claude. Signing in creates your account. Talk to it for a few days first: a page with nothing on it is not much of a page.

Step 2: a token for your page

A page in your browser cannot use Claude's connection. It needs a token of its own, tied to your account. Honest answer: getting one means two commands in a terminal, once. On a Mac open Terminal; on Windows open PowerShell.

Ask for a code by mail, with the email you signed in with:

curl -X POST https://api.undrstand.com/magic-links/mails \
  -H "Content-Type: application/json" -H "Accept: application/json" \
  -d '{"email": "you@example.com"}'

Open the mail, then trade the six-digit code for a token:

curl -X POST https://api.undrstand.com/magic-links/tokens \
  -H "Content-Type: application/json" -H "Accept: application/json" \
  -d '{"email": "you@example.com", "code": "123456"}'

# {"data": {"token": "3|eyJ…", "two_factor": false}}

The answer holds your token. Copy it and keep it like a password: it opens your whole account until you revoke it.

Step 3: ask Claude

In a chat with the undrstand connector on, paste this and change what you want. Claude reads your real patterns through the connector, so it builds for your data, not for a guess.

Prompt
Build me a single HTML file I can open in my browser. It shows my undrstand patterns as cards: name, impact, urgent flag, the feelings, and the description. Clicking a card shows the flows and the correlations. Above the cards, a timeline of the last 30 days: one row per day with a dot per capture. Use fetch against the API domain with a bearer token I paste into a field at the top, kept only in memory. Use my real pattern names from the connector as the sample data while you build. No frameworks, no build step, one file.

Open the file, paste the token, and the page reads your account. Ask for changes the way you would ask a colleague: a weekly review, a page per pattern, a print layout.

The page talks to the API from your browser, so it needs the API domain and your token. Claude knows the routes from the connector and the generated reference; if it guesses a field wrong, tell it to check the reference.

What to expect

  • A first page in one go, usually right for the shape of the data and rough on looks. Iterate.
  • Captures take up to two minutes to process, so a page that posts a capture has to wait before it can show the result.
  • Patterns need three different days. The first week the page will mostly show captures.
  • Your data lives on undrstand's servers in the EU. The page keeps nothing unless you ask Claude to make it remember things in your browser.

What not to do

  • Do not paste the token into the file itself or into a page other people can open. A field you fill each time is safer than a file that carries the key.
  • Do not publish the page with your token in it. If it happens, revoke the token by deleting it on the personal access token route, or ask Claude Code to do it.
  • Do not send your data to another service from the page without deciding that you want to.
  • Do not read a pattern as a verdict on you. It is what the data shows so far.