# Connecting to your house

> **Planned.** A house of your own cannot be had yet. What follows was tried on 2026-10-06 against
> a house on a machine of its own behind its gate, with VS Code, Claude.ai and ChatGPT, and will hold
> when houses can be had. In the sandbox the lease is the key and none of this applies
> (`the-sandbox`).

Your house is one address: `https://<your-house>/modellierer`, the door with every skill. Add it to
your MCP client as a remote server. The client finds out by itself where to sign in (the way MCP
prescribes, with OAuth), opens a browser window, and the person you act for clicks "Erlauben" there.
Nothing else is needed: no key to keep, no configuration but the address.

## The first time

core.blue sends the person a link: `https://<your-house>/willkommen#…`. They open it once in their
browser and click "Annehmen". The house then knows them, and their browser remembers them. Ask them
to do this before you add the address, or when the window asks for a code: the link is the easy way,
a code on the page the other.

## Then, for every client

1. Add the address as a remote MCP server.
2. The client opens a window: "<client> would like to work in your house as <person>." The person
   clicks "Erlauben". The window names where the answer goes; it should be your client.
3. Call `overview`. Under `caller` it names the person; whatever you write, you write as them.

A second client, a second device: the same address, the same window, one click. Each client gets a
key of its own, kept by the client in its own secret storage; every resident will see it in
`list_keys` and can retract it (planned, with the gate). A client that signs in again replaces its
old key.

## Clients tried

| Client | Where the address goes |
|---|---|
| VS Code with GitHub Copilot | `.vscode/mcp.json` (`{"servers": {"<house>": {"type": "http", "url": "…/modellierer"}}}`) or the command `MCP: Add Server`; then start it and allow it to sign in |
| Claude.ai | Settings, Connectors, a custom connector; the desktop app hands it on to Claude Code sessions |
| ChatGPT | Settings, Apps & Connectors, a connector with OAuth (developer mode) |
| Claude Code | `claude mcp add --transport http --scope user <house> https://<your-house>/modellierer`, then `/mcp` and authenticate (signing in not yet tried) |

The address itself, opened without MCP, says the same: a page for a person in a browser, a text for
an agent.

## Without a browser

A script or a service cannot sign in this way. A resident makes it a key (`create_key` at the keys
door, planned with the gate); it sends `Authorization: Bearer cb_…` with every request.

## The usual errors

- **401 "This house lets a client in when its person allows it":** the client did not sign in. Most
  clients do it when they see this answer; if yours does not, it cannot reach the house.
- **The window asks for a code:** this browser does not know the person yet. Open the link from
  core.blue in it first, or enter a code a resident made with `invite`.
- **"Session not found":** the client sent a session the house did not give out, usually after
  calling the house by hand. Restart the server in the client.

## Go deeper

- [getting-a-house](getting-a-house.md): the stages, and where the link comes from
- [the-three-doors](the-three-doors.md): what each door serves
- [your-data-stays-yours](your-data-stays-yours.md): who holds which key
- [the-sandbox](the-sandbox.md): a house for three hours, with no key