This is the house 'wegwerf': a memory of Atlantis, run by core.blue on a machine of its own. Its gate admits only its residents. To connect, add https://wegwerf.core.blue/modeller to your MCP client as a remote server; the client signs in by itself, and the person allows it in a browser. No key or code passes through you. Nothing of what the house holds is shown without signing in.

Doors:
  reader    https://wegwerf.core.blue/reader
  author    https://wegwerf.core.blue/author
  modeller  https://wegwerf.core.blue/modeller
  keys      https://wegwerf.core.blue/keys

How to get in, in this order:
1. Add https://wegwerf.core.blue/modeller to your MCP client as a remote server (below). It needs no key.
2. The client opens a browser window. The person signs in there: the first time with the invitation link core.blue sent them (or a code on the page), afterwards with one click on 'Erlauben'.
3. Keep nothing yourself: the client holds what the house gave it, in its own secret storage.
4. Check: call overview; under caller.person it names the person.

VS Code with GitHub Copilot (.vscode/mcp.json or the user configuration, or the command 'MCP: Add Server' (HTTP).)

{
  "servers": {
    "wegwerf": {
      "type": "http",
      "url": "https://wegwerf.core.blue/modeller"
    }
  }
}

- Add the server 'wegwerf' and start it.
- VS Code asks whether the server may sign in: allow it. A browser window opens.
- The person clicks 'Erlauben' there (the first time: opens the invitation link from core.blue first, or signs in with a code).
- In Copilot Chat, in agent mode, ask it to call overview of 'wegwerf'.
- The key lies: In VS Code's secret storage. No file holds it.

Claude.ai (Settings, Connectors: add a custom connector.)

https://wegwerf.core.blue/modeller

- Add a custom connector with this address.
- Connect: a window opens; the person clicks 'Erlauben'.
- In a chat, turn the connector on and ask for the overview of the house.
- The key lies: With Claude.ai, for this account; the desktop app hands it on to Claude Code sessions.

ChatGPT (Settings, Apps & Connectors: create a connector (developer mode).)

https://wegwerf.core.blue/modeller

- Create a connector with this address and OAuth as its authentication.
- Connect: a window opens; the person clicks 'Erlauben'.
- In a chat, use the connector and ask for the overview of the house.
- The key lies: With ChatGPT, for this account.

Claude Code (Your shell.)

claude mcp add --transport http --scope user wegwerf https://wegwerf.core.blue/modeller

- Run the command.
- In a Claude Code session, type /mcp, choose 'wegwerf' and authenticate; a browser window opens.
- The person clicks 'Erlauben'.
- Call overview of 'wegwerf'.
- The key lies: Where Claude Code keeps the sign-ins of its servers, not in a repository.

A script or service without a browser (Its HTTP requests.)

URL https://wegwerf.core.blue/modeller, header 'Authorization: Bearer cb_…' with a key a resident made.

- A script or service without a browser cannot sign in this way. A resident makes it a key (create_key at the door /keys); it sends 'Authorization: Bearer cb_…' with every request.
- The key lies: Wherever the script keeps secrets; outside every repository.

If the key is lost: A client that lost its sign-in signs in again: same address, same window, one click. The key it had before is retracted then. A script that lost its key asks a resident for a new one (create_key).

Usual errors:
- 401 'This house admits only the keys of its residents': the header did not arrive. Check that the client sends 'Authorization: Bearer cb_…' to every door.
- 401 'The header Authorization carries something other than …': the header is there but holds no 'Bearer cb_…'. A key alone, without the word, is taken as it is.
- 401 'This key does not open this house' or 'This key was retracted': the key is wrong, cut short, or retracted. list_keys at the keys door shows the keys; the owner of the house makes a new one.
- 403 'This key opens … and this needs …': the key does not carry the door it was sent to. Send it to a door it carries, or ask the owner for a key with that door.
- 403 'This is the owner key of the house': an owner key opens only /keys. Make a working key there with create_key and use that.
- '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.
- The client asks for OAuth or a login: this house takes only the header. Use a client that lets you set one.

More: https://core.blue/topics/connecting-to-your-house