Beta

Ask Claude who's working Saturday.

crewmuster connects to Claude, ChatGPT, and any other AI app that speaks MCP. Sign in once and approve it. From then on it reads your stores, crew, schedule, availability, sales, timesheets, and time off as you. Allow it, and it makes the same changes you could. It shows you each one before it happens.

Start free trial How to connect

Off until the owner turns it on · read-only unless you choose otherwise · every change previewed

What it can do

The week you'd open in the app, in a conversation.

A connected assistant has the permissions of the person who approved it, and no more. A manager's assistant sees drafts, wages, and sales. A crew member's sees the published schedule and their own availability.

Reading

Your stores and your crew. Everyone on the roster at each store, with job role and target hours.
Any week's schedule. Day by day, with who's on each shift and hours per person.
Availability. Standing weekly rules. Managers see everyone's, crew see their own.
Daily sales. Net, gross, transactions, and labor percent where it's known, for any date range. Managers only.
Timesheets. A week of punches, worked against scheduled hours per person, overtime, and missed clock-outs. Managers only.
Labor cost. Planned against actual, and your POS's own labor figure where it sends one, with labor percent, over up to 52 weeks. Cost from wages is hours times each person's base rate, so it's an estimate. Managers only.
Time off requests. Who asked for what, and whether it was approved, pending ones first. Managers only.
One person's details. Contact, hire date, access, base wage, and their new hire checklist if one is open. Managers only.
A suggested schedule. The same scheduler as the one-tap suggestion in the app. It writes nothing. You decide what goes on.

Changing, if you allow it

Shifts. Add one, change its day or times, put someone on it or take them off, or delete it. New shifts are drafts. Managers only.
Publishing a week. Everyone newly on the schedule gets an email and a push, exactly as if you'd pressed Publish in the app. Managers only.
Availability. Your own, or as a manager, anyone's at your store. When a manager sets it, that person is told.
A day's sales. Recorded by hand, the same as typing it into the sales page. Managers only.
Your roster. Add someone and they're emailed an invite and their new hire checklist starts, as in the app. Change a person's role, pay, target hours, or phone, or take them off the roster. Managers only.
New hire checklists. Start one, add a step, or tick one off with a note. A new hire can tick their own steps.

Tasks and reports aren't connected yet, and time off is read only. Email addresses, kiosk accounts, and checklist templates are changed in the app.

In practice

You ask in your own words. Changes wait for you.

"Who's on Saturday night?" It reads the week and answers with names and hours. Nothing is changed and nothing needs confirming.

"Move Jordan's Tuesday to 12 to 6." It shows you the shift before and after, and stops there. Nothing moves until you confirm that exact change.

"What did we take last Friday?" A manager gets the day's figures. A crew member's assistant is refused, because sales are manager business in the app too.

"What did labor run last week?" Planned against actual, what your POS says, and labor percent. It tells you overtime isn't priced in the wage figure, so a week with overtime reads low.

"Put next week out." The preview names everyone who will be emailed and pushed. Confirm it and they are. A week with compliance warnings isn't published from a conversation. You're sent to the schedule builder to look at them.

A confirmation is tied to the change it was issued for. It works once and expires after ten minutes, so an assistant can't reuse yesterday's yes on something else.

Who decides

You decide what it can touch.

Off until the owner says so

Each store has an Outside access switch, and it starts off. Only the account owner, or someone they've made a billing admin, can turn it on. Until then no connected app can read that store, let alone change it. Other managers see where it stands.

Read-only by default

When you approve an app, you choose read only or read and make changes. Read only is what you get unless you pick the other.

Every change previewed

Asking for a change returns a plain-language preview and changes nothing. Applying it takes a second, confirmed call for that exact change.

It acts as you

A connected app gets your permissions, at your stores. The same database rules apply as in the app, so crew see published shifts only and wages and sales stay with managers.

Every call on the record

The store's managers see each read and each change in Settings: who made it, from which app, and a one-line summary of what it did.

Take it back any time

Remove a connection from your profile and crewmuster refuses it from that moment. Turning the store's switch off stops every connection there at once.

Connecting

One address. Sign in once.

Every app connects to the same address, and there's no key or secret to copy. The app sends you to crewmuster, you sign in with your email code, choose read only or read and make changes, and approve it.

The address https://app.crewmuster.com/api/mcp

Claude

Add a custom connector in Claude's settings and paste the address. Custom connectors need a paid Claude plan.

ChatGPT

Turn on developer mode in ChatGPT's settings, then add a connector with the address.

Cursor and VS Code

One click opens the app with crewmuster already filled in. Each link works only where that app is installed.

Add to Cursor Add to VS Code

Claude Code

Install the crewmuster plugin with two commands, then run /mcp inside Claude Code to sign in. The plugin carries the connection and a skill that teaches Claude how crewmuster works: start with your stores, preview before applying, and remember that publishing reaches real people.

claude plugin marketplace add nschwalb1/crewmuster-plugins
claude plugin install crewmuster

Or add the connection on its own, without the skill:

claude mcp add --transport http --scope user --callback-port 3118 crewmuster https://app.crewmuster.com/api/mcp

Keep the callback port if you add it by hand. The sign-in checks the return address exactly, port included, and without a fixed one it can't find its way back to Claude Code. The plugin sets it for you.

Any other app that speaks MCP over HTTP and signs in with OAuth can use the same address. The same steps are inside crewmuster too, in Settings under Integrations and on your profile. Whichever app you use, the owner still has to turn on Outside access at the store before anything connects there.

What the assistant sees, and where it goes

Answers go to the AI company you chose. What a tool returns, a week of shifts or a day's sales, goes to the app you connected, under your own account with that company. crewmuster doesn't pick the model.
We see the calls, not the chat. crewmuster receives each tool call and what it asked for. The conversation around it stays between you and the assistant.
Nothing happens unless you set it up. The switch starts off at every store. A store that never turns it on sends nothing anywhere through this.

This is separate from crewmuster's own use of Claude, which reads an emailed sales report in a layout it hasn't seen before. That's covered on the reporting page and in our DPA.

Read this part

Where it stops, for now.

It's beta

The sign-in runs on Supabase's OAuth server, which is itself in beta. Expect the odd rough edge, and tell us when you hit one. Each person gets 60 reads and 20 change requests a minute. Past that, the assistant is told how long to wait.

Publishing is real

Publish a week from a conversation and your crew are emailed and pushed, the same as from the app. The preview says so before you confirm.

Most of the app, not all of it

Schedule, crew, availability, sales, timesheets, labor cost, time off, and new hire checklists are connected. Tasks and reports aren't yet, and time off is read only.