The MCP connection · slabos.com/mcp

Your shop’s numbers.
Your own AI.

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.

Enabled in your own settings — there is no public API to sign up for
THE WORKFLOW IN ACTIONSLABOS · 35 SEC

Your AI. Your shop analysis.

Connect an owner's AI client to supported shop analysis through MCP, with read-only access, expiring keys and owner control.

Read the film: text & visual description

SlabOS - Owner MCP Connection (SlabOS-Owner-MCP-Shop-Analysis-v1) - transcript
No voice-over. Every on-screen message and meaningful visual, in order. Times in seconds.

0.05 - 4.2 Hero: YOUR AI.
0.5 - 4.2 Hero: YOUR SHOP ANALYSIS.
0.15 - 4.2 Three separate 3D endpoints rise in: a glowing extruded key, a wireframe AI orb, the extruded SlabOS mark
0.45 - 3.9 Labels under them: OWNER · AI CLIENT · SLABOS
1.0 - 4.2 An orange access-boundary sphere forms around the SlabOS mark
1.7 - 3.9 Badge: OWNER-ONLY · READ-ONLY
3.8 - 4.2 The endpoints slide apart and fade

4.0 - 4.5 The Developer Tools panel swings in (the tab is already there)
4.1 - 6.5 Hero: ONE KEY. OWNER ONLY.
4.4 - 11.9 Panel header: DEVELOPER TOOLS · MCP CONNECTION
4.6 - 6.5 NEW CONNECTION NAME
4.9 - 5.8 The name types itself: OFFICE LAPTOP AI
5.2 - 6.5 Button: + CREATE KEY (pressed at 6.25)
4.8 - 6.5 Box: WHAT A CONNECTION CAN DO / READ COMPUTED BUSINESS METRICS FOR YOUR SHOP. / IT CANNOT CHANGE ANYTHING.
6.5 - 9.0 Hero: SHOWN ONCE.
6.5 - 9.0 An orange-bordered reveal box opens
6.65 - 9.0 COPY THIS KEY NOW — IT IS NOT SHOWN AGAIN
6.85 - 9.0 SLABOS STORES ONLY A FINGERPRINT OF IT.
7.0 - 9.0 slab_mcp_ followed by a moving scramble bar (the key itself is never readable)
7.15 - 9.0 Button: COPY, pressed at 7.6, becomes ✓ COPIED
7.7 - 8.95 Toast: ✓ KEY COPIED
8.1 - 9.0 Link: I'VE SAVED IT — HIDE THIS (clicked at 8.75)
9.0 - 12.0 Hero: EXPIRES IN 30 DAYS.
9.1 - 11.9 Connection card: NAME OFFICE LAPTOP AI · CREATED JUST NOW / KEY slab_mcp_4f9a… / EXPIRES 30 DAYS LEFT / USED 0 CALLS · LAST NEVER
10.1 - 11.9 Chip: 1 OF 3 ACTIVE

12.0 - 12.5 A generic AI client panel swings in
12.15 - 14.5 Hero: 9 TOOLS. READ-ONLY.
12.35 - 19.3 Panel header: AI CLIENT · ● CONNECTED · SLABOS 1.0.0
12.35 - 14.5 BEARER TOKEN followed by a moving scramble bar
12.55 - 14.5 tools/list → 9 tools: business_snapshot, revenue_trend, win_loss_analysis, pipeline_health, schedule_load, material_mix, inventory_position, customer_concentration, salesperson_performance
14.5 - 16.5 Hero: ONE QUESTION.
14.65 - 16.8 Question bubble: HOW DID WE DO IN SEPTEMBER?
15.2 - 16.8 tools/call → business_snapshot
15.4 - 19.3 "dateFrom": "2026-09-01",
15.6 - 19.3 "dateTo": "2026-09-30T23:59:59Z"
16.5 - 19.5 Hero: COMPUTED ANSWERS.
16.5 - 16.9 The conversation scrolls up
16.8 - 19.3 Result streams in, line by line:
"period":{"from":"2026-09-01","to":"2026-09-30"},
"quotesCreated": 48,
"quotesWon": 19, "quotesLost": 11,
"quotesPending": 18, "winRatePct": 63.3,
"wonValue": 142380, "newLeads": 63
17.5 - 19.3 The "quotesCreated": 48 line is boxed in orange
17.7 - 19.3 AGGREGATES IN. NO ROWS OUT.
19.5 - 22.0 Hero: SAME COUNT.
19.5 - 22.0 Two panels side by side: AI CLIENT and QUOTES
19.7 - 22.0 Left: quotesCreated, giant 48, SEP 1 – SEP 30
20.1 - 22.0 Right: filter chip CREATED DATE, giant 48, SEP 1 – SEP 30
20.65 - 22.0 A giant = lights up between the two 48s

22.0 - 24.2 Hero: SEE THE USAGE.
22.3 - 26.6 The connection card returns: OFFICE LAPTOP AI · CREATED 5M AGO / slab_mcp_4f9a… / 30 DAYS LEFT
22.5 - 22.9 USED counts up 1 CALL, 2 CALLS, 3 CALLS, 4 CALLS; LAST JUST NOW
22.6 - 25.0 Chip: 1 OF 3 ACTIVE
23.6 - 24.2 Button: REVOKE (with a trash icon), clicked at 24.2
24.2 - 26.7 Hero: ONE CLICK TO END IT.
24.25 - 24.9 Buttons: CONFIRM / CANCEL; CONFIRM clicked at 24.8
24.9 - 26.6 The pill turns to REVOKED, the card greys out and the Revoke button is gone
25.0 - 26.7 Toast: CONNECTION REVOKED. IT STOPS WORKING IMMEDIATELY.

26.7 - 29.5 The three endpoints again: OWNER · AI CLIENT · SLABOS
26.85 - 29.5 Hero: NEXT CALL: REFUSED.
27.0 - 27.4 The AI orb fires one request toward SlabOS
27.4 - 28.5 The request shatters on the access boundary; the boundary flashes
27.5 - 29.5 THIS MCP CONNECTION IS NO LONGER VALID.

29.4 - 31.7 Hero: READ-ONLY ANALYSIS.
29.7 - 31.7 Hero: OWNER CONTROL.
29.5 - 31.7 Beams draw from the owner key to the AI orb and through the boundary to the SlabOS mark; light packets stream along them and flash as they cross the boundary (poster frame at 30.6)
29.9 - 31.7 OWNER → AI → SHOP ANALYSIS

31.5 - 35.0 End card: the extruded SlabOS mark assembles piece by piece
32.3 - 35.0 SLABOS
32.55 - 35.0 CONNECT YOUR OWN AI.
32.8 - 35.0 slabos.com · BOOK A DEMO →
34.2 - 35.0 Fades to black (loop point)

Open video ↗
At a glance
Owners only. Not admins, not staff, not a role anyone can be granted.
Read-only. Nothing can be created, changed or deleted through it.
Your shop only. Isolation is enforced server-side on every call.
Three keys, 30 days. They expire on their own. Revoke any of them instantly.
Every call logged. You see what your assistant asked for, and when.
Chapter One
01
What it is

A door for your AI.
Not a door for anyone else.

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.

Margin and trend analysis Crew and salesperson performance Yield and inventory movement
“Every shop has the numbers. Almost none of them have the hours to sit with them. This is the part where you get to be curious about your own business.”

Fig. 01 — Your data, somewhere you can actually think with it.

Chapter Two
02
The limits are the point

What it will
never do.

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.

It cannot write

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 cannot export your records

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.

It cannot see another shop

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.

It cannot outlive your access

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.

It cannot be signed up for

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.

It cannot run unwatched

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.

Chapter Three
03
Turning it on

Three clicks,
inside your account.

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.

1
Settings → Developer Tools

Visible only to the shop owner. If you do not see the tab, you are not an owner on this account.

2
Create a connection

You get a key, shown once. Up to three at a time — one for your laptop, one for your phone, one spare.

3
Paste it into your AI client

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.

Curious about
your own shop?

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.

SLABOS IN MOTION 02 FILMS

SEE THE WORKFLOW.IN MORE DETAIL.

A closer look at the decisions, details and handoffs that make the work happen.

How SlabOS access links expire

Follow the different lifetimes of signing codes, password resets, downloads, invitations, AI keys and partner links, alongside the customer's ongoing quote-to-payment portal link.

Open video ↗

The AI permission check's second opinion

Follow a team member's financial question through the illustrated SlabOS AI permission checks, including a second review that withholds an answer when it cannot complete its check.

Open video ↗

Choose a film to play Explore the collection →