SlabOS speaks MCP — the open standard for connecting an AI assistant to live data. Switch it on inside your account and your own AI works with your shop’s real numbers: margins, win rates, crew utilisation, slab yield. Ask it what you’d ask an analyst.
It reads. It never writes. And it is only ever available to the owner of the shop, on that shop’s own data.
MCP — the Model Context Protocol — is how an AI assistant talks to a live system instead of guessing from what it was trained on. Connect SlabOS and your assistant stops speculating about your business and starts reading it.
The questions owners actually ask look like this: which material line is quietly losing margin, who closes fastest on quartz, what a slow February does to crew utilisation, whether the yard is turning over or just filling up.
You ask in your own words, in whichever AI client you already use. SlabOS answers from your own numbers.
Fig. 01 — Your data, somewhere you can actually think with it.
Most software answers “is it secure?” with a list of things it protects. Here is the shorter, more useful version — things this connection is structurally incapable of. Not policy, not a setting someone can flip. It cannot do these because the surface to do them was never built.
No create, no edit, no delete, no status change. There is no write path behind it, so there is nothing to misconfigure and nothing for a confused assistant to break.
It returns analysis — figures, trends, comparisons. It does not hand back rows of jobs, quotes or customers, so it cannot become a back door for copying a database.
Which shop you are is bound to the credential and re-checked server-side on every call. It is not a parameter, so it is not something that can be tampered with.
Keys expire after 30 days on their own. If an owner is deactivated or stops being an owner, the connection stops on the next call — not whenever a token happens to lapse.
No public API, no developer portal, no self-serve key. The only way to get one is to already be the owner of a shop running on SlabOS, and to switch it on yourself.
Every call is logged against the key that made it, visible to you, with its own limits. If something starts asking more than a person would, you see it.
Nothing to install and no configuration file to edit. If you are the owner, it is already waiting in your settings.
We tell you when a key is close to expiring, and your settings page always shows how many days it has left.
Visible only to the shop owner. If you do not see the tab, you are not an owner on this account.
You get a key, shown once. Up to three at a time — one for your laptop, one for your phone, one spare.
Anything that speaks MCP. From then on it reads your shop, and you watch every question it asks.
Fig. 02 — The whole setup. Revoke any connection from the same screen.
Book a demo and we will run SlabOS on one of your real jobs. If you already run on SlabOS and you are the owner, the connection is in your settings right now.
SlabOS does not publish an API reference. The connection details live inside your account, where only you can see them.