What your AI runs

Ask for the job, not the click.

Marrow connects the AI you already use, Claude or ChatGPT, to your account. This page is the job list. Each job is one plain sentence you say to your AI, and a set of steps it runs inside your own business using tools Marrow already ships.

It reads your real numbers, does the work, and leaves the results in your dashboard. Anything that touches money or a member waits for your press.

Turn it on in your dashboard See how it works

Eleven jobs. Eight for a coach. Three for a gym owner. Your AI is handed all eleven by name.

Getting going

Turned on from your dashboard.

Connecting happens inside your dashboard after you sign in, and it takes about a minute. Once it is on, you ask for a job in plain words.

The connection hands your AI this job list by name the moment it connects, so you can also just ask it which jobs it has and pick one. If it needs more to go on, read it the steps from the card. The card is the recipe, and it is the same recipe your AI was handed.

Open your dashboard

The honest shape of it

It does the thinking. You press the buttons that matter.

This is the part worth reading twice, because it is the part most tools lie about. Your AI reads, judges, drafts and stages through the connection. It does not go live. A new price arrives switched off. A post arrives as a draft. A plan arrives as a report filed in your dashboard. You are the one who presses Activate and Publish.

The connection also only works while you are in a conversation with your AI. Nothing happens between those conversations, and nothing it does can reach a member. What does carry across is the paperwork. Every job files a checkpoint report before it finishes, so the next conversation opens that report and picks the thread back up instead of starting the job over.

That is a smaller promise than most tools make. It is also the one you will actually get on your first day.

For a coach or trainer

Eight jobs on a coach connection.

Every one of these runs on tools that are live in your account today. Each card says what it reads, what it hands you, and where it stops.

Job 01

Win back the fading.

You say Who is drifting away from me, and write me something that brings them back.

What it does: Reads your business totals, your engagement summary and how often you post to your own community. Finds how many people are close to running out of sessions and how many have gone quiet.
What you get back: A community post draft written to pull those people back, plus a report holding the message it would send and the anonymous pointers it found.
Where it stops: It cannot publish the post and it cannot contact anybody. It never learns who those pointers belong to, because your side of Marrow never tells it. You publish. You reach out.

Job 02

Fix the price ladder.

You say Check my plans and packs and tell me what you would fix.

What it does: Reads your own live plans and session packs, then reads them against your real demand and the health of what you already sell. It looks for the gap in the middle, the pack nobody buys, and the plan priced under the work.
What you get back: Corrected and new plans and packs, written switched off, plus a report with the reasoning and the numbers it used to get there.
Where it stops: Every price arrives switched off. Your AI cannot switch one on, cannot touch your card processor, and cannot change what anybody is being billed today. You press Activate in your dashboard, one at a time.

Job 03

Launch a program.

You say Build me a six week program and the words to announce it.

What it does: Reads what you already run so it does not build you a second version of the same thing. Then it drafts the program, writes the matching copy into the fields on your own page, and drafts the announcement.
What you get back: A program draft, updated copy on your public page, an announcement post draft, and a launch plan report.
Where it stops: It cannot publish the program and it cannot assign it to a single person. It cannot invent a new section or a new page type to hold it either. It writes into what you already have.

Job 04

Build the public page.

You say Build me a website.

What it does: Asks you first, and that is the job rather than the preamble. Who you are and who you train, what you sell and roughly what it costs, what somebody should do when they land on the page, and what you want them to feel in the first few seconds. Then it builds the page out of your answers, picks a shape and a colour from the fixed menus, and writes the words in your voice.
What you get back: A real page carrying your own words, and a plain list of anything on it that is still empty. It will not fill a field with a sample sentence or a guess. An empty field you know about beats a sentence somebody invented for you, and a page of filler is the one thing worse for you than having no page yet.
Where it stops: Going live is a separate question, asked on its own, after the whole page and the exact web address it would live at have been read back to you. A yes to does this look right is not a yes to put it in front of strangers, so you are asked the second question by itself. It cannot pick your web address, invent a section, a colour or a font, or set a link of any kind, and every change it makes can be put back one at a time.

Job 05

Audit and repair the public page.

You say Look at my page and tell me what is missing.

What it does: Reads every copy field on your public page and the readability report Marrow computes on your own colours. Then it rewrites the weak copy and adjusts the styling inside the handful of style points you already control.
What you get back: Rewritten copy in your own fields, a styling pass, and an audit report of what changed and why. Anything structural it wished it could change is listed in the report for you to decide on.
Where it stops: Words land straight on your page, because those fields are yours and you own them already. Every one of those edits is logged, and one instruction puts it back. What it cannot do is change your layout, your template, your navigation or your sections, and it cannot make your page harder to read, because Marrow checks the contrast on the server before the change is accepted.

Job 06

Write the business review.

You say Write this month's business review.

What it does: Reads every total Marrow computes for you. Who is active and who is not, how signups are trending, how fast packs are being redeemed, engagement, the health of what you sell, and the state of your page and brand.
What you get back: One review in plain language, filed as a report in your dashboard. Written for the person who owns the business, not for an analyst.
Where it stops: This one is a read that ends in a report, so there is nothing to approve. It cannot invent a number. Where Marrow does not measure something, the review says so instead of guessing. It sees no member identity, because none is on the connection. Money is the one part that depends on you. A review carries dollar figures only on a connection whose coach has accepted the current agreement, and carries none of them otherwise.

Job 07

Sweep what is waiting on you.

You say What is waiting on me?

What it does: Reads what has been staged and never switched on, what has been drafted and never published, which reports you have not opened, and everything your AI itself changed on your account this week.
What you get back: One report listing every open thread, each with the exact press it is waiting for, ordered by what costs you most to leave sitting.
Where it stops: It lists. It does not execute. It cannot switch anything on, publish anything, or undo a batch of changes in one move. When it thinks something should be put back, it recommends it one change at a time.

Job 08

Get my clients in.

You say Put my clients into Marrow.

What it does: Looks up each client you name before it writes anything, so nobody is created twice, and asks you for the details that live outside Marrow and where they probably are. It needs Client profiles switched on for your own account, and it tells you so if it is off. A client you add appears by name only once they agree in their own Marrow account.
What you get back: One client record per real person, or the empty fields filled on a record you already had, read back to you before it writes, plus a short list of who was added, who was updated and what is still missing.
Where it stops: It writes client records and nothing else. It never creates an account, sends an invite or charges anyone on its own, and it never invents a field. An invite is a separate step you say yes to.

For a gym owner

Three jobs on an owner connection.

An owner connection is a reader and a stager by design. It sees readiness, inventory and counts across your roster. It never sees a member, and it never sees a trainer's own content or a trainer's own prices. A manager account gets no connection at all.

Owner job 01

The monthly owner review.

You say Give me the state of the gym.

What it does: Reads which trainers are set up and which are stalled, how full the next ninety days look, your plans, your fee structures, your events, and everything that changed since the last review.
What you get back: One report on the state of the gym, ranked by what needs your hand first.
Where it stops: Read, then report. Nothing to approve. It never sees a member, never opens a trainer's own work, and never touches a fee structure or an event.

Owner job 02

Fill the quiet week.

You say Which weeks are thin, and who could cover them?

What it does: Reads where the coming weeks are thin, which trainers are ready to sell, and which ones are still missing a setup step that is blocking them.
What you get back: A report naming the quiet windows, the ready trainers who could cover them, and the exact gaps holding the rest of your roster back.
Where it stops: Every move in that plan is made by a person in your console. Your AI cannot create a class, cannot move a session, and cannot contact a trainer or a member to arrange it.

Owner job 03

Stage the offer and the look.

You say Stage new gym plans and a cleaner brand colour.

What it does: Reads the plans the gym owns and the brand colours you run today, then proposes better ones.
What you get back: Gym plans written switched off, a brand colour staged as a draft with its readability already checked, and a report explaining both.
Where it stops: You switch the plan on and you apply the colour, both by hand in your console. It cannot put a plan live, cannot change your live page, and cannot reach into a trainer's own prices.

The same five rules on every job

What it can never do.

It publishes only when you say yes. Your own page can be taken live, and taken back down, after the whole page and its web address have been read back to you and you have said yes. A program or a community post publishes the same way.
It never charges anyone without your yes. Prices arrive switched off. It can take a payment, issue a refund or turn a price on only after you have been shown exactly what will happen and have said yes.
It never messages anyone without your yes. A message goes out only after you have been shown exactly what will happen and have said yes, and Marrow keeps that yes, in your own words, with the time. A text goes only to someone who said yes to texts themselves, in their own Marrow account.
It never sees who your members are unless you switch Client profiles on for your own account and that member has agreed in their own Marrow account, which lets it work with that member by name. Without it, no names and no contact details reach it, only totals, clock times and pointers that carry no identity, and it never sees card details or billing addresses. Dollar amounts reach a connection only once its coach has accepted the current agreement, and an amount is attached to a person by name only while Client profiles is on and that person has agreed.
Every change is logged, and every change can be undone. One instruction puts any single edit back the way it was.

These are not settings. They are the shape of the connection, held in Marrow's own code rather than in the wording of what you asked for. A clever request cannot talk its way past them, and neither can a careless one.

For the reader who wants the real surface

Underneath, it is a small tool list and nothing else.

No hidden agent, no second model, no background process. Every job above is a sequence over the tools your connection carries. If you want to compose your own sequence instead, nothing stops you, and nothing you can compose gets past the five rules.

Open the technical surface

The connection speaks the Model Context Protocol. A coach connection carries one hundred three tools, and five more once the coach on it has accepted the current connection agreement. Accepting it also hands the connection 364 two step tools, listed last below, and 34 of those, the ones that move money, also wait on the same switch as those five. A gym owner connection carries nineteen, on a separate registry, scoped to the roster, and 59 more two step tools once the owner accepts the current gym connection agreement, also listed below. A manager account is handed a list of zero.

Seventy seven of the coach tools are newer than the eleven 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 dashboard 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. Posting a draft is a separate two step tool, listed last below, and it posts only after you have said yes.
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 AI 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 AI. 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 none of these thirty five 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 dashboard. Every one of those services can be written to, and none of these thirty five does it. Sending a broadcast, replying to a message, changing a booking, moving a calendar event, editing a video description or publishing a post is a separate two step tool, listed last below, and each one acts only after you have been shown exactly what will happen and have said yes. 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. The two that use a Google or Meta sign in write only through those same two step tools.

Five more tools are built and finished, and they are not in the one hundred three 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. Sending, posting, booking and charging are separate two step tools, listed last below. Each one shows you exactly what will happen first and acts only after you have said yes, and Marrow keeps that yes, in your own words, with the time. A text goes only to someone who said yes to texts themselves, in their own Marrow account. Your social accounts are yours: linking them is something you would do yourself.

The eleven jobs on this page are not a document you have to keep. They ride on the connection itself, as named jobs your AI 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 eight by name. A gym owner connection is handed three. A manager account is handed none of them, the same as the tools.

Coach tools

lamella_get_overview
lamella_get_site
lamella_get_brand_report
lamella_update_site_copy
lamella_restyle
lamella_set_site_layout
lamella_scaffold_site
lamella_preview_site_publish
lamella_publish_site
lamella_unpublish_site
lamella_list_membership_tiers
lamella_upsert_membership_tier
lamella_list_session_packages
lamella_upsert_session_package
lamella_list_programs
lamella_get_program
lamella_upsert_program
lamella_draft_community_post
lamella_save_report
lamella_list_reports
lamella_get_change_log
lamella_revert_change
lamella_get_attendance_summary
lamella_get_checkin_health
lamella_get_progress_trends
lamella_get_program_progress
lamella_draft_member_checkin
lamella_draft_progress_note
lamella_find_member
lamella_get_member_profile
lamella_create_member
lamella_update_member
lamella_get_business_snapshot
lamella_get_engagement_summary
lamella_get_commerce_health
lamella_draft_social_post
lamella_list_leads
lamella_draft_lead_reply
lamella_get_pipeline_hygiene
lamella_stage_lead_move
lamella_stage_lead_task
lamella_draft_lead_note
lamella_get_retention_risk
lamella_get_checkin_cadence
lamella_draft_retention_outreach
lamella_get_schedule_utilisation
lamella_get_quiet_windows
lamella_get_booking_gaps
lamella_list_staged_schedule_changes
lamella_stage_slot_open
lamella_stage_slot_hold
lamella_stage_session_move
lamella_get_nutrition_library
lamella_draft_nutrition_plan
lamella_list_jobs
lamella_get_job
lamella_list_job_runs
lamella_checkpoint_job
lamella_pause_job
lamella_gbp_status
lamella_gbp_list_reviews
lamella_gbp_queue_review_drafts
lamella_gbp_list_review_drafts
lamella_ayrshare_status
lamella_ayrshare_list_accounts
lamella_ayrshare_list_posts
lamella_ayrshare_draft_post
lamella_ayrshare_list_drafts
lamella_calcom_status
lamella_calcom_list_bookings
lamella_calcom_list_availability
lamella_calcom_draft_booking_change
lamella_calcom_list_booking_drafts
lamella_vimeo_status
lamella_vimeo_list_videos
lamella_vimeo_draft_video_description
lamella_vimeo_list_video_drafts
lamella_kit_status
lamella_kit_list_subscribers
lamella_kit_list_tags
lamella_kit_draft_broadcast
lamella_kit_list_broadcast_drafts
lamella_manychat_status
lamella_manychat_list_conversations
lamella_manychat_draft_reply
lamella_manychat_list_reply_drafts
lamella_gcal_status
lamella_gcal_list_events
lamella_gcal_draft_event_change
lamella_gcal_list_drafts
lamella_meta_status
lamella_meta_list_accounts
lamella_meta_list_posts
lamella_meta_list_comments
lamella_meta_draft_reply
lamella_meta_list_drafts
lamella_twilio_status
lamella_twilio_list_numbers
lamella_twilio_list_messages
lamella_webhook_out_status
lamella_webhook_in_status
lamella_webhook_out_draft_payload
lamella_webhook_out_list_drafts

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.

lamella_get_revenue_summary
lamella_get_revenue_trend
lamella_get_spend_ceiling
lamella_stage_refund
lamella_stage_price_change

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

lamella_gym_overview
lamella_gym_get_app_status
lamella_gym_get_roster
lamella_gym_setup_gaps
lamella_gym_activity_rollup
lamella_gym_list_membership_tiers
lamella_gym_list_fee_structures
lamella_gym_list_events
lamella_gym_list_reports
lamella_gym_get_change_log
lamella_gym_upsert_membership_tier
lamella_gym_get_site
lamella_gym_update_site_copy
lamella_gym_stage_branding
lamella_gym_save_report
lamella_gym_revert_change
lamella_gym_upsert_fee_structure
lamella_gym_stage_event
lamella_gym_growth_trend

The two step coach tools, once the current agreement is accepted

These 364 reach a coach connection only after its coach has accepted the current connection agreement. Each one that sends, publishes, charges or changes a price shows exactly what will happen first and acts only after the coach has said yes, and Marrow keeps that yes, in the coach's own words, with the time.

lamella_preview_program_publish
lamella_publish_program
lamella_unpublish_program
lamella_save_program_week
lamella_save_program_day
lamella_save_program_exercise
lamella_remove_program_item
lamella_reorder_program_items
lamella_get_member_assignments
lamella_preview_program_assignment
lamella_assign_program
lamella_preview_program_assignment_end
lamella_end_program_assignment
lamella_preview_macro_targets
lamella_set_member_macro_targets
lamella_preview_meal_plan_assignment
lamella_assign_meal_plan
lamella_preview_meal_plan_assignment_change
lamella_change_meal_plan_assignment
lamella_preview_dietary_profile
lamella_set_dietary_profile
lamella_preview_measurement
lamella_log_measurement
lamella_preview_photo_estimate
lamella_confirm_photo_estimate
lamella_preview_recalibration_decision
lamella_decide_recalibration
lamella_preview_progression_policy
lamella_set_progression_policy
lamella_preview_nutrition_principle
lamella_save_nutrition_principle
lamella_preview_macro_plan_template
lamella_save_macro_plan_template
lamella_preview_recipe
lamella_save_recipe
lamella_preview_nutrition_settings
lamella_save_nutrition_settings
lamella_preview_meal_plan_days
lamella_change_meal_plan_days
lamella_get_member_measurements
lamella_list_photo_estimates
lamella_get_meal_completions
lamella_get_member_cardio
lamella_get_member_pillar_activity
lamella_get_member_wearables
lamella_get_wearables_overview
lamella_list_member_bloodwork
lamella_get_progression_policy
lamella_import_list_sources
lamella_import_stage
lamella_import_preview
lamella_import_apply
lamella_integrations_list
lamella_integration_setup_guide
lamella_integration_test
lamella_list_threads
lamella_read_thread
lamella_mark_thread_read
lamella_preview_message_send
lamella_send_message
lamella_list_broadcasts
lamella_preview_broadcast
lamella_send_broadcast
lamella_list_checkins
lamella_preview_checkin_reply
lamella_reply_checkin
lamella_preview_checkin_cadence
lamella_set_checkin_cadence
lamella_preview_client_invite
lamella_invite_client
lamella_preview_offline_invite
lamella_invite_offline_client
lamella_preview_invite_resend
lamella_resend_invite
lamella_preview_import_invites
lamella_send_import_invites
lamella_preview_review_request
lamella_request_review
lamella_preview_form_send
lamella_send_form
lamella_preview_specialist_invite
lamella_invite_specialist
lamella_preview_community_invite
lamella_invite_to_community
lamella_preview_program_notify
lamella_notify_program_assigned
lamella_list_team_coaches
lamella_preview_refund
lamella_execute_refund
lamella_preview_price_activation
lamella_set_price_active
lamella_preview_billing_change
lamella_change_client_billing
lamella_preview_charge
lamella_take_payment
lamella_preview_payment_request
lamella_request_payment
lamella_preview_payment_request_cancel
lamella_cancel_payment_request
lamella_preview_price_link
lamella_create_price_link
lamella_preview_event_ticket
lamella_sell_event_ticket
lamella_preview_dispute_evidence
lamella_submit_dispute_evidence
lamella_list_payments
lamella_list_disputes
lamella_save_dispute_draft
lamella_get_connect_status
lamella_get_session_balances
lamella_list_payment_requests
lamella_get_client_billing
lamella_list_invoices
lamella_create_invoice
lamella_list_products
lamella_create_product
lamella_update_product
lamella_archive_product
lamella_list_quick_charges
lamella_record_quick_charge
lamella_get_payout_schedule
lamella_preview_schedule_apply
lamella_apply_schedule_change
lamella_get_schedule_items
lamella_get_calendar_feed_status
lamella_preview_calendar_feed_rotation
lamella_rotate_calendar_feed
lamella_preview_walk_in_booking
lamella_book_walk_in
lamella_list_appointment_offers
lamella_create_appointment_offer
lamella_preview_appointment_offer_change
lamella_change_appointment_offer
lamella_list_bookings
lamella_list_bookable_locations
lamella_preview_booking_change
lamella_change_booking
lamella_preview_client_booking
lamella_book_client
lamella_preview_booking_reschedule
lamella_reschedule_booking
lamella_list_session_plans
lamella_preview_session_booking
lamella_book_session_for_client
lamella_preview_session_change
lamella_change_booked_session
lamella_preview_session_plan
lamella_create_session_plan
lamella_preview_session_plan_stop
lamella_stop_session_plan
lamella_list_classes
lamella_create_class
lamella_preview_class_change
lamella_change_class
lamella_preview_class_session
lamella_schedule_class_session
lamella_preview_class_session_change
lamella_change_class_session
lamella_list_member_group_workouts
lamella_list_training_groups
lamella_create_training_group
lamella_update_training_group
lamella_preview_group_member_change
lamella_change_group_member
lamella_preview_group_session
lamella_book_group_session
lamella_preview_group_deactivation
lamella_deactivate_training_group
lamella_preview_group_reactivation
lamella_reactivate_training_group
lamella_list_roster
lamella_get_client_commerce_view
lamella_get_client_intake
lamella_get_their_view
lamella_add_client_note
lamella_get_client_permissions
lamella_preview_client_permissions
lamella_set_client_permissions
lamella_get_onboarding_questions
lamella_set_onboarding_questions
lamella_list_habits
lamella_preview_habit_change
lamella_save_habit
lamella_list_challenges
lamella_preview_challenge_change
lamella_save_challenge
lamella_list_form_templates
lamella_upsert_form_template
lamella_list_automation_rules
lamella_upsert_automation_rule
lamella_test_automation_rule
lamella_record_achievement_event
lamella_create_prospect
lamella_list_crm_tasks
lamella_update_crm_task
lamella_preview_lead_move_apply
lamella_apply_lead_move
lamella_preview_lead_task_apply
lamella_apply_lead_task
lamella_ayrshare_preview_send
lamella_ayrshare_send
lamella_meta_preview_send
lamella_meta_send
lamella_gbp_preview_send
lamella_gbp_send
lamella_vimeo_preview_send
lamella_vimeo_send
lamella_kit_preview_send
lamella_kit_send
lamella_manychat_preview_send
lamella_manychat_send
lamella_calcom_preview_send
lamella_calcom_send
lamella_gcal_preview_send
lamella_gcal_send
lamella_webhook_out_preview_send
lamella_webhook_out_send
lamella_lead_preview_send
lamella_lead_send
lamella_retention_preview_send
lamella_retention_send
lamella_list_site_pages
lamella_upsert_site_page
lamella_reorder_site_pages
lamella_archive_site_page
lamella_restore_site_page
lamella_preview_site_page_change
lamella_apply_site_page_change
lamella_get_site_arrangement
lamella_arrange_site
lamella_preview_site_arrangement
lamella_apply_site_arrangement
lamella_get_site_offers
lamella_preview_site_offers
lamella_set_site_offers
lamella_get_site_video_gallery
lamella_preview_site_video_place
lamella_place_site_video
lamella_preview_site_video_remove
lamella_remove_site_video
lamella_get_custom_domain
lamella_preview_custom_domain_set
lamella_set_custom_domain
lamella_preview_custom_domain_connect
lamella_connect_custom_domain
lamella_preview_custom_domain_disconnect
lamella_disconnect_custom_domain
lamella_preview_managed_domain_request
lamella_request_managed_domain
lamella_get_profile
lamella_preview_profile_social
lamella_set_profile_social
lamella_preview_modality
lamella_set_modality
lamella_get_reviews
lamella_set_review_settings
lamella_get_referrals
lamella_start_referrals
lamella_get_member_referrals
lamella_get_growth_overview
lamella_get_recommendations
lamella_get_community
lamella_list_community_members
lamella_create_community
lamella_update_community
lamella_preview_community_access
lamella_set_community_access
lamella_revoke_community_invite
lamella_preview_community_promotion
lamella_save_community_promotion
lamella_preview_community_challenge
lamella_save_community_challenge
lamella_list_community_posts
lamella_preview_community_post
lamella_publish_community_post
lamella_preview_post_change
lamella_apply_post_change
lamella_react_to_post
lamella_list_moderation_reports
lamella_preview_moderation_action
lamella_apply_moderation_action
lamella_list_community_groups
lamella_preview_community_group
lamella_create_community_group
lamella_get_area_settings
lamella_preview_area_settings
lamella_save_area_settings
lamella_list_events
lamella_preview_event_change
lamella_apply_event_change
lamella_list_event_attendees
lamella_check_in_attendee
lamella_list_ondemand_classes
lamella_get_ondemand_analytics
lamella_create_ondemand_class
lamella_update_ondemand_class
lamella_preview_ondemand_change
lamella_apply_ondemand_change
lamella_list_paid_templates
lamella_create_paid_template
lamella_update_paid_template
lamella_preview_template_listing
lamella_set_template_listing
lamella_list_template_library
lamella_get_library_template
lamella_list_videos
lamella_get_video
lamella_list_ready_recordings
lamella_list_library_offers
lamella_upsert_video
lamella_archive_video
lamella_preview_video_edit
lamella_edit_video
lamella_preview_video_visibility
lamella_set_video_visibility
lamella_preview_video_assignment
lamella_assign_video
lamella_preview_video_unassignment
lamella_unassign_video
lamella_preview_recording_conversion
lamella_convert_recording
lamella_get_coach_settings
lamella_update_setup_checklist
lamella_set_panel_visibility
lamella_restore_hidden_panels
lamella_set_tab_guide
lamella_dismiss_credential_prompt
lamella_set_role_preferences
lamella_set_email_prefs
lamella_list_customization_requests
lamella_save_customization_request
lamella_list_credentials
lamella_claim_credential
lamella_edit_credential
lamella_preview_credential_delete
lamella_delete_credential
lamella_get_go_live_gate
lamella_list_migrations
lamella_get_migration
lamella_review_migration_item
lamella_preview_migration_signoff
lamella_sign_off_migration
lamella_list_trainer_invites
lamella_preview_trainer_invite_answer
lamella_accept_trainer_invite
lamella_decline_trainer_invite
lamella_get_member_team
lamella_cancel_specialist_invite
lamella_preview_specialist_removal
lamella_remove_specialist
lamella_list_team_trainers
lamella_preview_form_to_trainer
lamella_send_form_to_trainer
lamella_preview_coach_specialist_invite
lamella_invite_coach_specialist
lamella_end_job
lamella_preview_job_create
lamella_create_job
lamella_preview_job_resume
lamella_resume_job
lamella_preview_job_continue
lamella_continue_job
lamella_preview_import_undo
lamella_undo_import

The two step gym owner tools, once the current gym agreement is accepted

lamella_gym_preview_team_fee
lamella_gym_set_team_fee
lamella_gym_preview_billing_split
lamella_gym_set_billing_split
lamella_gym_preview_revenue_split
lamella_gym_set_revenue_split
lamella_gym_preview_plan_switch
lamella_gym_switch_plan
lamella_gym_preview_fee_switch
lamella_gym_switch_fee_structure
lamella_gym_preview_trainer_invite
lamella_gym_send_trainer_invite
lamella_gym_preview_trainer_removal
lamella_gym_remove_trainer
lamella_gym_preview_member_transfer
lamella_gym_transfer_member
lamella_gym_preview_outside_trainer_invite
lamella_gym_send_outside_trainer_invite
lamella_gym_preview_outside_invite_cancel
lamella_gym_cancel_outside_invite
lamella_gym_preview_outside_trainer_end
lamella_gym_end_outside_trainer
lamella_gym_preview_manager_invite
lamella_gym_send_manager_invite
lamella_gym_preview_manager_invite_withdraw
lamella_gym_withdraw_manager_invite
lamella_gym_preview_manager_removal
lamella_gym_remove_manager
lamella_gym_preview_manager_locations
lamella_gym_set_manager_locations
lamella_gym_preview_operator_grant
lamella_gym_grant_operator_access
lamella_gym_preview_operator_end
lamella_gym_end_operator_access
lamella_gym_preview_details_change
lamella_gym_change_details
lamella_gym_preview_public_listing_change
lamella_gym_change_public_listing
lamella_gym_preview_custom_domain
lamella_gym_change_custom_domain
lamella_gym_preview_brand_colour
lamella_gym_apply_brand_colour
lamella_gym_preview_event_status
lamella_gym_set_event_status
lamella_gym_preview_event_announcement
lamella_gym_announce_event
lamella_gym_preview_site_publish
lamella_gym_publish_site
lamella_gym_get_network
lamella_gym_get_payments
lamella_gym_list_members
lamella_gym_list_managers
lamella_gym_list_outside_trainers
lamella_gym_get_access_record
lamella_gym_set_locations
lamella_gym_set_setup_checklist
lamella_gym_get_details
lamella_gym_get_schedule
lamella_gym_get_milestones

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.

Marrow 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.

Not built. Wanted next.

What the connection will do later.

None of the following works today, on any connection, for anybody. Some of it has tools on the connection already, and where that is true it is said plainly below, because a tool that answers that it is unavailable is not a capability. It is here so you can see where this is going and hold us to it. Everything on this list will arrive under the same five rules, or it will not arrive.

Review monitoring. Rating trend and unanswered reviews, with draft replies you post by hand. Every review answered, never filtered by how kind it was. The four tools for this are on the connection and they are not switched on: no review account is joined to Marrow, so each one answers that it is unavailable.
Outside connectors. Nothing outside Marrow is connected today. The first one we build will be read only, and it will get its own security review before a single account is joined to it.
Anything unattended. Your AI does not run overnight, does not watch anything, and does nothing on its own. Five tools for listing and pausing scheduled work are on the connection and they are not switched on: nothing anywhere runs that work, so each one answers that it is unavailable. If that ever changes it will be a deliberate decision with its own approval design, not a quiet upgrade.

Two things are on this list on purpose and may never leave it. The connection will not be given a way to contact your members, and it will not be given a way to move money. Those are the load bearing walls.

Hand it the first job.

Set it up, press Approve, and say the sentence from job four. You will have a real audit of your own page in your dashboard before you have finished reading it.

Turn it on in your dashboard See how it works

Included with your Marrow plan. You use your Claude or ChatGPT account and you pay for it yourself. Read the connection agreement before you approve.