Set up Lamella. Three steps, once.

The setup, in order

Connect once. Ask for the job. Press what matters.

Three steps, numbered, in order. Each one opens by telling you what it is and what it is for, so you always know where you are and why you are there. There is nothing to install. The sign in path asks you to type nothing at all. The settings path asks you to paste one block, and Claude Code, being a terminal tool, uses its own command.

1. Step 1 Connect Marrow to your Claude.

   The one time connection. Pick where you talk to Claude, then follow the one path that appears. About a minute.

   It hands your Claude a key to your own Marrow account and nothing else. The key only acts with your approval, and you can revoke it from your dashboard any time. Lamella is Claude only. One client means one set of behaviour we can actually test, so every guardrail on this page is proven against Claude and nothing else. Our server refuses every other assistant by policy and says so plainly, so time spent connecting anything else is time wasted. The path below is the one almost everybody uses.

   Connect. Press Connect with Lamella, sign in, press Approve. About a minute, once.

   What every path asks for

   Whichever Claude you picked, it asks for the same two things. Where Marrow Lamella lives, and proof that you are you. The address is public and it is right here. The proof is private, so it is made inside your dashboard where you are already signed in.

   A connection is scoped to the account that makes it. A coach connects from the coach dashboard and Lamella covers that coach's own business. A gym owner connects from the gym console and Lamella covers the whole roster: roll ups, setup gaps, and gym owned plans staged for your approval, never an individual member and never a trainer's own content. What Marrow costs is on the pricing page.

   Server address

   https://lamella.marrowfitness.com/mcp Copy

   Choose streamable HTTP if your client asks for a transport. Lamella does not serve SSE, so a client that only offers SSE cannot connect today.

   Your proof, built for you

   On the sign in path there is nothing for you to build. Claude opens a Marrow page, you sign in, you press Approve, and Marrow hands the proof to Claude directly. You never see or handle a token. For the settings path, sign in, press Connect with Lamella, and pick Claude Code. The panel makes the access token on its own side and gives you the finished configuration with the token already inside it.

   A coach connection makes a key prefixed mct_. A gym console connection makes its own key, prefixed mgt_ rather than mct_. Same steps, owner scope.

   The first time, you read and accept the Lamella connection agreement, on the Marrow page before you press Approve. A token lasts 90 days. A connect code, shaped MRWC-XXXX-XXXX-XXXX-XXXX, is needed only by the paste fallback, which is the third card at the end of this step. It lasts ten minutes and works once. Both are revocable from your dashboard, and a connected Claude cannot make either one for itself.

   Naming the connection is up to you

   If you are asked to name this connection, the name is yours to pick and nothing depends on it. Name it after the laptop it lives on, name it the front desk, name it whatever you will still recognise in six months. It is a label for your own list, and it does not change what the connection can reach or what it can do.

   The three grades

   Each path below opens with a grade saying how far we have actually checked it. These are the same three sentences your coach dashboard prints beside every client, word for word, so the page and the dashboard can never drift into two different promises.

   • Written from that vendor's current published documentation.
   • Pending live verification. These steps come from the vendor's own current documentation. Marrow has not yet run this client against Lamella end to end.
   • Status unknown. Marrow makes no support claim here. We have not seen it work and we have not seen it fail.

   Written from that vendor's current published documentation.

   The sign in path, which is the one you want

   A sign in path. Clicks only, and you never touch a token.

   1. In Claude, go to Customize, then Connectors.
   2. Click the plus button, then Add custom connector.
   3. Paste the server address as the remote MCP server URL. It is https://lamella.marrowfitness.com/mcp
   4. Leave Advanced settings alone. Lamella registers the client for you, so no client ID or secret is needed.
   5. Click Add. Claude sends you to a Marrow page.
   6. Sign in with your Marrow password, read the agreement, and press Approve. Claude finishes on its own and hands you back connected.

   On Team and Enterprise plans an Owner adds the connector once under Organization settings, then each person connects it and signs in as themselves. Each connection is bound to the Marrow account that approved it.

   Claude reaches Lamella from Anthropic's cloud, not from your computer, so there is nothing for you to open up on your own network.

   Source: Claude Help Center, custom connectors using remote MCP. Checked 2026-08-16.

   Using Claude Desktop or Claude Code instead? Those two connect a little differently and their full instructions are further down this page.

   Own a gym? Same flow, from your gym console instead of the coach dashboard. An owner connection reads across your roster and comes with its own owner jobs.

   Two ways in. Your Claude picks, not you.

   The sign in path is the one most people get, and it is the shorter one. The third card is the older paste form, kept alive for the rare case where a browser will not open.

   • The sign in path.

     The client sends you to a Marrow page. You sign in with the Marrow password you already have, read the agreement, and press Approve. The client finishes on its own and hands you back connected. There is no code to paste and you never see or handle a token. Prefer this whenever the client offers it.

   • The settings path.

     Claude Code wants an entry in a settings file instead. For that, your dashboard makes the access token on its own side and gives you the finished configuration to copy. Your part is paste and save. The token lasts 90 days and you revoke it from the same panel.

   • The paste fallback.

     If a Marrow sign in page will not load for you, the older paste form is still there. Add &manual=1 to the end of the Marrow address your Claude opened, then paste a connect code from your dashboard. Nothing else about the connection changes.

   The web path and the Desktop path use no command at all. The one command on this page is Claude Code's own /mcp, typed inside Claude Code, because that client lives in a terminal. If any setup anywhere ever asks you to open a terminal to connect Claude on the web or Claude Desktop to Marrow, that instruction did not come from us.

2. Step 2 Prove it worked.

   A ten second check that the connection is real.

   So you never have to wonder. A connection that half worked looks exactly like one that worked until you test it.

   Ask Claude: "Pull my Marrow business snapshot." Real counts from your own account mean you are connected. A refusal, or an answer with no numbers in it, means Step 1 did not finish. The fixes live in the list at the bottom of this page, and none of them are your fault.

3. Step 3 Ask for your first job.

   How you actually use Lamella. Plain sentences, with no syntax to learn.

   The gap between wanting something and knowing what to type is where most people stop. The prompt library closes it. Every button gives you the exact words, says what they will and will not change, and copies them for you.

   Ask for a job, in plain words. Win back the fading. Fix the price ladder. Fill the quiet week. Your Claude reads your real numbers, does the work, and leaves it finished in your dashboard.

   Open the prompt library, press a button, read what it does, copy it, paste it into Claude. Or just say what you want in your own words. Six named jobs, like Win Back the Fading and Fix the Price Ladder, are written out in full on the jobs page.

   First job to try: "Write this month's business review." If you own a gym and you connected from the console, ask for "Run my monthly owner review." instead.

   Open the prompt library See the named jobs What it will never do

Only if you need it

Using Claude Desktop or Claude Code?

The three steps above are the same for everyone. The connecting itself is slightly different on these two, so their instructions are here in full. If you talk to Claude in a browser, you do not need this section at all.

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

True from here on

Press what matters.

If it does not take

Five things go wrong, and none of them are your fault.

• The code will not take.

  Only the paste fallback uses a code at all. Codes are single use and they last ten minutes, so almost every rejection is the clock rather than anything you did. Generate a fresh one in your dashboard and paste it while the countdown is still running.

• Too many attempts.

  Redeeming a code is rate limited. Give it a rest, then come back with a fresh code. Retrying immediately fails the same way.

• Claude asks for an SSE address.

  Lamella does not serve SSE. If the screen in front of you offers no streamable HTTP option, that connection cannot complete today. It is a real limit, not something you configured wrong.

• You are not using Claude.

  Lamella connects to Claude only, and our server refuses other assistants rather than half working with them. A Claude account is the one thing to bring. If you believe you are on Claude and it still will not connect, tell us what you see through Help and we will look at it with you.

• You want to cut it off.

  Open Connect with Lamella in your dashboard and press Disconnect on that row. Access stops immediately. Removing the Marrow server inside Claude stops it asking, but the dashboard is what revokes.