The three doors
A house is one MCP server with three routes. Each route serves a profile, and each profile contains the one before it. The route names are German.
| Door | Route | Skills | What it adds |
|---|---|---|---|
| reader | /leser | 44 | finding, describing, reading, walking, counting, planning an erasure, seeing the open work; writes nothing |
| author | /autor | 102 | storing values, creating individuals and documents, reading files, asserting and retracting facts, notes, open questions, plans, conversations, erasing, taking and submitting open work |
| modeller | /modellierer | 105 | the vocabulary: define_form, define_aspect, include_concept |
The numbers are those of the house software as of 2026-10-07. A sandbox switches import_url
off and shows one skill fewer at the author and modeller doors. The root of the address serves
the reader profile.
Doors are not tiers and not licences. They are a way to give an agent exactly the reach
its job needs: a reviewing agent connects to the reader door and cannot write, however it
is prompted. The reader door does not know the writing skills at all: calling store_text
there is answered with "unknown tool".
The house describes its own skills
list_skillsreturns every skill with the smallest door that serves it, whether it writes, whether repeating a call is harmless, and one sentence of summary.read_skillreturns one skill whole: the full description and the parameter schema exactly as the door serves it. A skill that needs a higher door says so:define_formread through the reader door carries the hint that it is callable from the modeller profile upwards.
Read a skill before you use it the first time. The descriptions state conventions that a
name cannot: that creating never searches, that a path is an array, that a year is a span.
read_skill shows the arguments of a skill, not the shape of its answer; look at the first
answer before you script against it.
Preambles
Each door greets a connecting agent with a short instruction. The modeller door's says:
call overview first; reuse before coinage; every answer reports is_new, and that is
your accountability. The word varies in practice: storing and asserting skills report
is_new, creating skills created, and set_property reports changed.
Errors are written for you
Where the house refuses, it says what would work. Asking for the versions of a document without naming the aspect was answered:
No property slot 'Structure' at this thing. No property slot here without a context. Also at this thing: Structure — pass context_id '…' (Document).
One exception found while writing this manual: an argument of the wrong JSON type (a
string where an array is expected) is answered with a bare "an error occurred" and no
hint. If you get that, compare your arguments with the schema from read_skill.
Besides the doors
GET /binary/{hash}andPOST /binarycarry bytes. They carry no meaning: an upload returns a content hash, and a skill gives the hash its meaning./opsis the operations endpoint: it reports the state of the service, not the content of the house.
Who may connect
A house listens on its own machine only. Access from outside goes through a gate in front of
it that admits a key per person; the gate is built and was tried on a test machine, and in a
house you can have it is planned (connecting-to-your-house). A sandbox is reached through
core.blue's server, and its lease is the key.
Go deeper
- First hour in a house: the doors in use
- Forms, aspects and concepts: the modeller door
- Finding things: the reader door
- A memory you can shape