How to Automate Your Employee Schedule with AI (Using Claude + CrewHR MCP)

196 shifts. 20 employees. One month. Five minutes.

Those are the numbers from the walkthrough below. A coffee shop manager connects Claude to CrewHR through our MCP server and asks it to build an April schedule. Claude fills 95% of the shifts on the first pass. The remaining 5% are blocked by the team's own rules, not by Claude.

This post shows you how to set it up and run the same workflow on your team.

Watch the Walkthrough

What you'll need

A CrewHR account with your team, locations, and roles configured
Claude, desktop or web. Other MCP-compatible tools work too.
About five minutes.

MCP stands for Model Context Protocol. It is the connection layer that lets an AI read and write to CrewHR. You do not need to understand the protocol to use it.

Step 1. Get your CrewHR MCP key

Open CrewHR and go to:

Settings → MCP → Create Key

Copy the key. Treat it like a password.

Step 2. Connect CrewHR to Claude

In Claude, open:

Settings → Connectors → Add Custom Connector

Paste the key. Save.

The Claude interface shifts as the product updates, so the menu labels may move. The flow stays the same. Find the connectors area, add a custom connector, paste the key.

Then restart Claude. A fresh start helps it recognize the new connector reliably.

Step 3. Test the connection

Open a new chat and type:

"Let's test the CrewHR MCP for the Bean & Brew Coffee Shop."

Claude queries CrewHR, pulls some basic information, and confirms the connection is live. If it can see your team and your locations, you are ready.

Step 4. Ask Claude to build a schedule

Ask:

"Create a schedule draft for April 2026."

Claude checks for existing drafts, reviews your coverage requirements, pulls your shift rules, and starts assigning people.

In the demo, Claude generated 196 shifts for a 20-person coffee shop in about a minute. It filled 95% of the month on the first pass.

Step 5. Review the draft in CrewHR

Open the new draft in CrewHR. The review screen shows:

Coverage summary: shifts filled versus shifts open
Shift distribution: whether hours were spread evenly across the team
Rule violations: any shift that bumps against a configured rule

The 5% Claude could not fill is the rule engine at work. In the demo, one Barista shift stayed open because every eligible employee would have broken the "two days off in a row" rule.

Fix the gaps manually in a few clicks, or ask Claude to suggest trade-offs.

Step 6. Review your scheduling rules

CrewHR supports a library of scheduling rules. The common ones:

Minimum rest time between shifts
Maximum consecutive days worked
Required consecutive days off, for example two days off in a row
Role-based coverage requirements per shift block
Per-employee availability and preferences

Edit any of these in Settings → Scheduling Rules. Claude respects the updated rules on the next schedule it builds.

Step 7. Publish and share

When the draft looks right:

Publish the schedule. Notify staff automatically, or hold off and notify them yourself.
Save as a template, if this coverage pattern repeats each month.
Generate a share link. Staff can filter the public, read-only view by their own name. No login required.

You can also view the schedule as a printable list, export it, or keep the team in the CrewHR mobile app.

Time off and vacation are already handled

Claude uses the time-off requests, sick days, and approved vacation already stored in CrewHR. You do not have to remind it. If someone booked a week off in April, they do not get a shift that week.

Why this changes the job

The old scheduling job was two hours of tactical work: finding gaps, juggling rules, remembering exceptions.

With AI and MCP, the job becomes review instead of build. Claude handles the tactical pass. You handle the 5% judgment call. The trade-offs, the "give this shift to Sam because she has been asking for more hours," the things only you know.

That is the version of scheduling that scales across multiple locations without adding admin time.

More than scheduling

CrewHR runs the operational loop beyond the schedule:

Timesheets with clock-in, breaks, and kiosk support
Time-off requests with approval workflows
Attendance tracking and absence reporting
Multi-location and role-based coverage rules

All of it is available to Claude through the same MCP connection. Once connected, you can ask Claude to approve time off, review timesheets, or flag attendance issues. Not only to build schedules.

Try it yourself

Already on CrewHR? Grab your MCP key from Settings → MCP and point Claude at it. A draft schedule will be ready to review in five minutes.

Not on CrewHR yet? Start a free trial at crewhr.com. We will import your team and build your first AI schedule within a day.

Questions or feedback? Reach out. We ship improvements to the MCP server every few weeks based on how real operators use it.