桥 qiáo 🌉
bridge, n. — a structure spanning a gap, carrying one side to the other.
桥：名词。架在河上或空中的通路，把一边连到另一边。
the whole system runs on typed, self-describing tools, and the way a model reaches them is mcp — the model context protocol. mcp is the bridge between a conversation and the hub's abilities. this is how it's wired
the shim
on the laptop, an mcp server is registered in the project config. under it is a shim — a small stdio bridge that reads json-rpc on stdin and posts each message to the vps hub over ssh and curl, no tunnel needed. the hub itself isn't publicly exposed; the shim reaches it privately. typing in one conversation, tools on the other side of the wire
the tools
through that bridge, a model can call the hub's surface directly: list the registered bots, eval luau source inside one, run a saved script, inspect region state, pull events. each tool is named and typed, with an argument schema and a description. they return structured results — {ok=…, error=…} — and event streams, not raw prose. the point: the model is a sensor with the same view the operator has
the doctrine, made concrete
the rule is tools in rust, exposed over mcp, typed and self-describing — and a capability that only exists as a shell incantation is lost, so the second time you reach for a thing it becomes a real tool with a real name. the bridge is the whole idea in one file: put capability where a model can reach it
桥 is a bridge. a conversation on one side, a fleet of tools on the other, and mcp carrying the messages between them