Your Claude, working inside your business.

The prompt library

Press a button, get the words.

Every button below hands you a prompt we actually run. Press it and you get what the prompt is for in plain language, what it will change and what it will not, the exact words to paste into Claude, and a control that copies them. Read prompts change nothing at all. Write prompts leave a draft or a staged change sitting there until you press it.

• Only one thing publishes, and only when you say so. Your own public 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. Nothing else publishes: a post lands as a draft and you press Publish.
• Nothing sends. The message tools read and draft. Not one of them can send, to a member or to anyone else.
• Prices land switched off. A staged price charges nobody until you switch it on in Marrow.
• Members come back as counts and opaque refs, never names.
• Anything written can be put back, one change at a time, from the change log.

What it is

You bring Claude. We bring the tools.

Lamella is a connection, not another subscription to another assistant. It speaks the Model Context Protocol, the open standard AI clients use to reach outside systems.

• You bring your Claude account.

  Lamella is built for Claude and connects to Claude only. Sign in with the Claude account you already have, from claude.ai or Claude Code. It hands you over to Marrow, you sign in, you press Approve.

• You pay for Claude yourself.

  Your Claude runs on your account and your usage. We do not resell you a model and we do not sit between you and the company you already pay for one.

• We supply the tools and the guardrails.

  Your Claude can only do what a Marrow tool lets it do. Where there is no tool, there is no ability. That is the whole safety model, and it lives in code, not in a policy page.

Three people read this page for three different reasons. Below, each one gets the sentences they would actually type, what lands in the dashboard when they do, and what stays in their own hands. Every example names the shipped tools it runs on, so you can check the claim instead of trusting it.

Where it lives

It is already in your dashboard.

Lamella is not a separate app to learn or another tab to keep open. It sits in the dashboard you already sign in to. Press the button, sign in, press Approve. That is the whole setup, there is no code to paste, and you do it once.

For trainers at a gym

Your page, your packs, your words. Filled in between clients.

You coach for a living. Nobody signed up for an evening of typing their own bio for the fourth time. Here is what to type instead.

• You type

  Rewrite my bio for busy parents who train before work, and leave the rest of my page alone.

  • What lands

    Your headline, tagline, about text and services change in place, each one recorded next to the wording it replaced.

  • What stays yours

    Your photos, your layout, your booking link and the moment your page goes live. No tool can reach any of them.

  Tools: lamella_get_site, lamella_update_site_copy

• You type

  Fill in three session packs for my area. I will switch on the one I like.

  • What lands

    Three packs in your catalog, switched off, with a report titled New pricing staged for your approval.

  • What stays yours

    Turning one on. The tool can only ever write a pack inactive, so a price it wrote cannot reach a client until you say so.

  Tools: lamella_list_session_packages, lamella_upsert_session_package

• You type

  Warm up my accent color, and tell me whether it still reads.

  • What lands

    Your accent, your theme and your site color move to shipped values, and any color you name is corrected to the readability standard before it is stored. Your Claude is told what was corrected and why.

  • What stays yours

    The design system. Your Claude picks from what Marrow ships. Lamella cannot write CSS, set a font, define a theme or invent a token.

  Tools: lamella_get_brand_report, lamella_restyle

• You type

  Draft a community post about the new early slot.

  • What lands

    A draft in the Lamella tab of your dashboard, with a note to you explaining what it went for.

  • What stays yours

    Posting it. No tool on this server posts, sends a message, or notifies a member. The one thing Lamella can publish is your own page, and only after it reads the page back to you and you say yes.

  Tools: lamella_draft_community_post

• You type

  Show me what you changed this week, and put my old bio back.

  • What lands

    Every change with its before and after value, newest first, and the old wording restored.

  • What stays yours

    The last word. An undo runs through the same field list as the original write, so a revert can never reach something the write could not.

  Tools: lamella_get_change_log, lamella_revert_change

For coaches running the whole practice

The blank page, and the numbers you keep meaning to look at.

Same connection, wider job. If the business is yours, your Claude can read the shape of it as well as write the words, and it reads counts rather than people.

• You type

  Give me a health check of my business.

  • What lands

    A written report in your Lamella tab, sitting next to the ones before it, built from how many members sit in each membership and billing state, how many joined in each of the last six months, your plan mix and price range, the credits sold, left and redeemed on your session packs, and how long it has been since your last community post.

  • What it cannot see

    Who any of those people are. No tool returns a member name, an email address, a phone number, a health record or a payment. There is no argument that could ask one for it.

  Tools: lamella_get_business_snapshot, lamella_get_commerce_health, lamella_get_engagement_summary, lamella_save_report, lamella_list_reports

• You type

  Fill in three membership tiers priced for my market. I will turn on the one I like.

  • What lands

    Three plans written into your catalog, switched off, and a report titled New pricing staged for your approval.

  • What stays yours

    Every activation. The tool cannot set a plan active, and the Marrow platform fee is neither readable nor writable through it.

  Tools: lamella_list_membership_tiers, lamella_upsert_membership_tier

• You type

  How many people are close to running out of session credits, and what should I say to them?

  • What lands

    A count of the purchases near the end of their credits, plus draft wording saved to your Lamella tab.

  • The honest limit

    The pointers it gets back are scrambled on purpose and cannot be turned into a person, so ask Marrow support to identify a flagged purchase. Your Claude cannot look one up anywhere, and it never sends the message.

  Tools: lamella_get_engagement_summary, lamella_save_report

• You type

  Sketch a six week intro program and leave it as a draft.

  • What lands

    A private draft program with a name, a description and a length in weeks.

  • What stays yours

    The training itself. Blocks, days and exercises are not writable by any Lamella tool, and no argument can publish a program or assign one to a member.

  Tools: lamella_list_programs, lamella_get_program, lamella_upsert_program

• You type

  Rewrite my services so a first timer knows what to book, and check my testimonials read like people.

  • What lands

    Your services, your proof lines, your how to start steps and your lead form wording rewritten in place, inside the layout you already have.

  • What stays yours

    The page going live, your gallery, your links and your form fields. Structure is read only to your Claude, so it writes copy that fits your layout instead of changing it.

  Tools: lamella_get_overview, lamella_get_site, lamella_update_site_copy

For gym owners

The roll up, and the setup nobody finished.

Read this before you connect anything. A gym owner connects from the gym console and gets a roll up across their roster, not a coach view. What an owner can and cannot reach is listed below, and the limits are as deliberate as the capabilities: an owner sees roster level numbers and the setup gaps that cost them money, and never an individual member's health record.

An owner does not need another dashboard. An owner needs the two or three things quietly costing the gym money, in a sentence, on a Sunday night.

• You type

  Which of my trainers have no published price and no payout set up?

  • What lands

    The trainers whose setup is unfinished, by name, because your gym console already attributes that to a named trainer. Empty programs and missing public pages come with it.

  • What stays yours

    Fixing it. Gym scope will never write to a trainer's own page, prices, programs or client records. A gym owner is not a trainer's administrator in the product, and Lamella will not become the path that makes them one.

  Gym scope. Built on the same roster reads the gym console already performs.

• You type

  Roll up sessions booked, classes scheduled and attendance across the roster this month.

  • What lands

    Totals across the roster and per trainer, plus capacity use, drawn from the same roster the console builds server side.

  • Where the line is

    No individual member's health, body or nutrition record, ever. A trainer's client never agreed to the gym owner's chosen AI reading their body metrics, so gym scope is built so it cannot.

  Gym scope. Roll ups only, never a named person's health record.

• You type

  Draft three membership tiers for the new location and leave them switched off.

  • What lands

    Gym owned plans staged inactive, exactly the way the coach side already stages a price, with a report telling you they are waiting on you.

  • What stays yours

    Activation, and anything that charges. No tool moves money on either surface.

  Gym scope. Gym owned commerce only, staged inactive.

• You type

  Write me a plain read on where the gym is leaking setup, and what to chase first.

  • What lands

    A report addressed to you, in the console, in language you could hand to a manager.

  • What stays human

    Anything with a bill attached. Inviting, removing or suspending a trainer is an owner decision, so it stays a human act in your console and no tool will ever do it. What Marrow costs is on the pricing page.

  Gym scope. Reports to the owner, never a roster change.

First job to try: "Run my monthly owner review."

Where it stops, on purpose

It fills your business in. It does not rebuild it.

Every tool writes content into a structure Marrow already ships. Not one of them can invent a new structure. That reads like a limit. It is the reason you can hand your Claude the keys at all.

• It writes inside what you already have.

  Memberships, session packs, programs, community posts, your site copy, your bios, your gallery captions, your services, and your own brand colors. All of it is content in a shape Marrow ships, tests and supports.

• It cannot invent a page type.

  No new templates, no new layouts, no new page types, no navigation, no theme entries, no schema changes. Your site cannot be restructured by a sentence you typed at midnight, which is exactly the promise a blank canvas cannot make.

• Your accessibility survives it.

  Any color your Claude names is measured and corrected to the readability standard before it is stored, and the correction is handed back so you are told what changed and why. A restyle cannot leave your page unreadable.

• There is no back door.

  No tool accepts a table name, a file path, raw markup, a layout key, or an account id. There is no general purpose query, file, shell or fetch tool anywhere in the server, and adding one is a blocking defect at review rather than a judgment call.

Works with

The Claude you already pay for.

Lamella speaks an open protocol, so a client either connects or it does not. We put a name on this page only after we have run it ourselves, end to end, against a real account.

• Claude Verified

  The client Lamella is built and tested against. Add the server address below, sign in, press Approve.

• Claude, and nothing else.

  This is a deliberate choice rather than a gap we have not filled yet. One client means one set of behaviour we can actually test against, and every guardrail on this page is proven against it. Other assistants are refused by the server, not merely left undocumented. The setup page is the two minute walkthrough.

Connecting

Three steps, once.

Setup happens one time and it happens inside Marrow, on the account you already sign in to. There is no code to paste. After that you just talk to Claude the way you already do.

1. Step 01

   Add the Marrow server in Claude.

   One address, the one below. Claude asks for it once. The exact click path for whichever Claude you use is on the setup page.

2. Step 02

   Sign in, then press Approve.

   Claude sends you to Marrow. You sign in as yourself, read what the connection can reach and what it cannot, tick the agreement and press Approve. Claude finishes on its own from there.

3. Step 03

   Ask for a job.

   Plain sentences, like the ones above. Reports land in the Lamella tab of your dashboard. Every write lands in the change log with an undo sitting next to it.

{
  "mcpServers": {
    "marrow-lamella": {
      "url": "https://lamella.marrowfitness.com/mcp",
      "headers": {
        "Authorization": "Bearer mct_YOUR_TOKEN"
      }
    }
  }
}