The MCP layer
RunningHow tools are exposed, scoped and kept replaceable. 50 in-house servers, 798 tools.
Every tool in the system is exposed through the Model Context Protocol. Nothing is hard-wired into an agent — tools are servers, agents are clients, and the binding between them is configuration.
Why a protocol instead of function calls
A tool behind a protocol boundary can be written in any language, restarted independently, swapped for a different implementation, and scoped per agent without touching agent code. A tool compiled into the agent can do none of those things.
It also means the tool surface is enumerable. You can ask the system what it can do and get a list, rather than reading source to find out.
How many
We counted 50 MCP servers written in-house, exposing 798 tools between them (counted from the code on 27 October 2026). Most speak over standard input and output; a few of the larger space servers speak HTTP. The largest are the sales station with 98 tools, the Brain’s own tool proxy with 79, container operations with 41, database access with 31 and video production with 30. Standard third-party servers are configured on top of that and are not counted here.
One of them has been verified end to end: on 27 October 2026 the sales station’s tool server was initialised, listed its tools and answered a read-only call, all over MCP.
What the servers cover
| Domain | Examples |
|---|---|
| Brain | A proxy exposing the Brain’s capabilities as tools |
| Code retrieval | Semantic search over an indexed repository |
| Containers and system | Container, process, power, registry and update operations — mostly proofs of concept |
| Security | Network monitoring, firewall, endpoint hardening, scanning — proofs of concept |
| Navigation | Resolving natural language to a space for the desktop interface |
| Knowledge | Reading and writing knowledge documents |
| Spaces | Sales station, marketing, video production, learning, ideas, research and others |
The seam that survived the refactor
When the two largest spaces were rewritten in June 2026, the thing that made it survivable was that they had already been addressed through protocol boundaries rather than imported directly. The ideas space lost most of its implementation and kept its MCP surface, so routing into it continued to work against a much smaller server.