The connection speaks the Model Context Protocol. A coach connection carries
ninety nine tools, and five more once the coach on it has accepted the current
connection agreement. A gym owner connection carries nineteen, on a separate
registry, scoped to the roster. A manager account is handed a list of zero.
Seventy seven of the coach tools are newer than the ten jobs above, so no job
on this page composes them yet and you reach them by asking for them. They come
in ten groups.
-
One drafts a social post. It writes the text and stops.
-
Two are your lead pipeline. A coach connection can read its
own pipeline as stages and waiting times, and can have a follow up drafted for
one lead on the channel you pick.
-
Three read your schedule. How full you are over a forward
window, which hours of your week are quiet, and where the gaps sit between
what you have committed to. These read no identity of any kind, which is
covered below.
-
Four propose schedule changes. Opening a one to one slot,
holding a window, moving something to a different start time, and listing what
is proposed and still waiting. Every one of them writes a proposal into a
separate staging table. None of them can reach your real calendar.
-
Five are your own social accounts, and none of them posts.
Three would read which accounts you have linked and what you have already
posted on them. Two work on drafts: one writes a post into your Lamella tab
and stops there, and one lists the drafts already waiting. Nothing is linked
today and the connection to the posting service is not set up on our side
either, so the three that read answer that they are unavailable rather than
pretending. There is no tool on the connection that publishes to a social
account, and there is no half of one behind a switch.
-
Nine are not switched on. Five would list and pause scheduled
work, and four would read and draft replies to your public reviews. Nothing
runs scheduled work today and no review account is connected, so all nine
answer that they are unavailable rather than pretending.
-
Four are your lead pipeline, and three of them are hands rather than
eyes. One reads which leads have gone past your own follow up rhythm,
longest wait first. Three let your Claude QUEUE an act instead of only
describing one: move a lead to another stage, set a follow up, or draft a
note. Nothing it queues happens on its own. Each lands in a list on your
leads page with the sentence it would perform, and it happens when you press
it and not before.
-
Three take your public page live, and bring it back down.
One reads the whole page back and hands over a confirmation. The other two
will not act without that confirmation, and it is worth exactly one press, on
the page you were actually shown, for ten minutes. Edit a word in between and
it stops working on purpose, so you are never asked about one page and given
another. Marrow refuses to publish a page with no web address, a page whose
owner has no working email to receive enquiries, and a page with nothing on it
at all. Taking the page down asks in the same way and is never refused, so
this is not a one way door.
-
Eleven are about the people you actually coach. Four read
your side of the training relationship: who has been turning up, whether your
check ins are keeping pace, how measurements are moving, and how far through a
program somebody is. One more reads nutrition, the plans in your own
library. Two read who is drifting away from you and how overdue each
person is. The last four write DRAFTS into your
Marrow tab: a check in message, a progress note, a win back, and a nutrition
plan. Nothing here is sent to anybody, and no name, email address, phone
number or photo of a member reaches your Claude. It sees your members the
way a roster sees them, as an anonymous handle and a pattern.
-
Thirty five reach accounts of yours that are not Marrow, and not one
of them sends, posts or books anything. They cover your booking
calendar, your video library, your email list, your Instagram and Facebook
messages, your Google Calendar, your Facebook Pages and Instagram, your text
messaging account, and a destination you can hand an automation. Each one
either READS what is already there or writes a DRAFT into your Lamella tab.
Every one of those services can be written to. Marrow does not do it: there
is no tool here that creates a booking, uploads or edits a video, sends a
broadcast, replies to a message, moves a calendar event, publishes a post or
sends a text, and there is no half of one behind a switch. The part of the
connection that talks to each service is only allowed to ask for the handful
of pages it reads, and it refuses anything else before the request leaves.
Nothing is linked until you link it: you connect an account from inside Marrow
while signed in, with a key you get from that service, and you disconnect it
the same way. Until you do, every one of those tools answers that no account
is connected rather than pretending. On the two that use a Google or Meta sign
in, permission to WRITE was never asked for at all, so those two could not
post even if something tried.
Five more tools are built and finished, and they are not in the ninety nine
above. Two of them read what your business took, in dollars. One reads the
ceiling on what can be staged against your account. Two propose a refund or a
price change. Every one of them works.
These five wait on the connection agreement rather than on us. A coach reaches
them only after accepting the current version, which is the one that describes
the money surface in plain words, and Marrow holds a switch over that surface
on top of your acceptance. Until both hold they are not handed to your
Claude, they are not in your tool list, and a request that names one is
answered that it is unavailable. Everything you already use keeps working
whether you accept or not.
Every drafting and staging tool in that list writes and stops. Lamella sends
nothing, on any channel, to anybody. It holds no inbox, no phone number and no
messaging login for you. Your social accounts are yours: linking them is
something you would do yourself, and even once one is, the tools that reach it
only read what is there and write drafts you read. So the posting, the booking
and the sending are acts you take yourself after you have read what it wrote.
The ten jobs on this page are not a document you have to keep. They ride on
the connection itself, as named jobs your Claude can list and open, and the
connection states what it is the moment it opens. So a connected Claude
knows the job list before your first message, and what it opens is the same
recipe printed on the cards above. A coach connection is handed seven by name. A
gym owner connection is handed three. A manager account is handed none of them,
the same as the tools.
Coach tools
The five that wait on the current agreement
These five are named here so you can see exactly what is on the other side of
that acceptance and hold us to it. None of them reaches a connection until the
coach on it has accepted the current agreement.
A gym owner can ask where their branded app is, and that is the only
thing about the app Claude can do. One tool reads the step the
build is on, whether that step is moving, and whether anything is waiting on
you. It reads the same record your console shows on the same card, so the two
can never tell you different things.
Everything else about the app is a person at a keyboard, permanently.
Enrolling with Apple, submitting a build, and the review Apple runs afterwards
are acts on Apple's side, and Marrow holds no switch over any of them. There is
no tool that submits, no tool that uploads, and no half of one behind a flag.
The server refuses to start if a tool is ever added whose name reaches that
surface, which is a check on the way in rather than a promise in a document.
And the read never claims Apple has approved anything: it says a build was sent
for review, it prints no date it cannot know, and when it cannot reach the
record it says so rather than telling you nothing has started.
Gym owner tools
Where the rules actually live
-
The two upsert tools have no writable field for making a price live. It is
not filtered out of your request. There is nowhere for it to go.
-
The copy tool walks a fixed list of fields. A template, a layout, a section,
or a media mode is refused because it is not on the list.
-
The restyle tool clamps colour against a contrast check on the server, so an
unreadable page cannot be saved even if it was asked for.
-
The read tools return totals and opaque pointers. There is no tool that turns
a pointer back into a person, on either registry.
-
The lead read never selects a name, an address you write to, or a phone
number. It does not read those columns at all, so a lead reaches your
Claude as an opaque pointer with a stage and a set of waiting times, and
the follow up it drafts is addressed to that pointer. You open the lead in
Marrow to see who it is.
-
The schedule reads select no identity column at all. Not a member id, not a
booking id, not a slot id, and neither the coach's nor the member's notes on a
session. A schedule comes back as counts, clock times and durations, so there
is not even a pointer to mint. That is stronger than the rest of the read
surface, not the same as it.
-
The three schedule proposals write one pending row into a staging table and
can reach nothing else. There is no path from this connection to your real
sessions, your real slots or your real bookings, so a proposal is not a
cancellation that is waiting politely. Your calendar is untouched until you
press it on a Marrow screen.
-
The five money tools are the only ones held on your own decision. Everything
else that answers unavailable is missing a table or a login. These are missing
nothing. They are refused until the connection's own coach has accepted an
agreement whose text covers them, and the refusal is a check in Marrow's own
code that runs before your request reaches the tool, not a line in a prompt
asking it to behave. It is read per connection, so it answers for your account
and never for everybody's at once.
-
None of the five is a way to move money, and that is true in every state of
that check. The two reads only ever read, and never select who paid. The
refund and the price change write a proposal and stop, exactly like the
schedule proposals, so the press that issues a refund or puts a price live is
yours on a Marrow screen and nowhere else.
-
Every write records what was there before, and the undo replays through the
same field list as the original write.
-
The job list is served by the connection, so every connection that opens is
handed the same jobs with the same steps and the same stopping points. You
cannot talk a tenth job into existence, and a job cannot be handed a step
that has no tool behind it.
-
Your token lasts ninety days and you can revoke it from your dashboard at any
time. Judgement lives in Marrow's code, not in the text of your request, so
every connection gets the same answers and the same refusals.
Lamella supplies the business truth and the drafts. What you and your own
Claude do with them elsewhere is between the two of you, and Marrow is not
in that loop.