7shifts

@7shifts list all shifts for location 12345 next week that are still open or unassigned

Found 8 open shifts across 3 departments at location 12345 for the week of January 13-19. The breakdown: 4 server shifts (Tuesday dinner, Wednesday lunch, Friday dinner, Saturday brunch), 2 kitchen prep shifts (Monday morning, Thursday morning), and 2 host shifts (Friday evening, Saturday evening). Each shift includes the scheduled hours, department, role, and whether it's published to the team. All shifts are currently unassigned and available for pickup.

This example uses the List Shifts tool with location, date-range, and open-shift filters. The MCP requires a valid location ID from your 7shifts account. Results are paginated—if you have more than one page of shifts, you'll need to request subsequent pages using the returned cursor. The MCP does not auto-fetch all pages in a single call.

@7shifts create a new department called 'Catering' at location 98765 and make it the default department for that location

Created department 'Catering' with ID 44332 at location 98765. This department is now set as the location's default, meaning new roles and shifts will automatically associate with Catering unless another department is specified. The department is active and ready to receive role assignments and scheduled shifts. You can now use department ID 44332 in subsequent shift-creation or user-assignment calls.

This example demonstrates the Create Department tool with the optional default-department flag. Creating a department is a write operation that immediately affects your 7shifts account structure. If you later delete this department, you'll need to transfer its roles and shifts to another department or they will be orphaned. Requires API key with write permissions.

@7shifts pull the user assignments for employee ID 55678 and summarize which locations and roles they're currently authorized to work

Employee 55678 is assigned to 2 locations with 3 distinct roles. At the Downtown location, they're authorized as Server and Bartender. At the Airport location, they're authorized as Server only. All assignments are active. Based on this configuration, the employee can be scheduled for server shifts at both locations, but bartender shifts only at Downtown. No department-level restrictions are in place—assignments span all departments at each location.

This example pairs the Get User Assignments tool with AI reasoning to interpret access scope. The MCP returns raw assignment data (location IDs, department IDs, role IDs); the AI translates those into human-readable context. Useful for auditing permissions before scheduling or troubleshooting why an employee can't pick up a shift. Requires the employee's numeric user ID, not their email or name.

When 7shifts wins for scheduling ops at 3-8 locations

A 6-person ops team managing shift schedules across five retail stores hits this daily: someone calls out, they need to see who's available at nearby locations, then text the right people. The 7shifts MCP pulls live shift data filtered by location and time range, so the team can ask Switchy 'who's scheduled tomorrow at the downtown and west-side stores' and get names in seconds. The List Shifts tool handles publication state and open-shift filters, which matters when you're triaging coverage gaps in real time. This breaks down if you're scheduling fewer than 20 shifts a week—manual Slack pings are faster. But once you're coordinating 50+ shifts across multiple sites, the MCP pays off by collapsing five-tab context-switching into one shared workspace query.

When this MCP handles franchise org-structure reviews

A three-person franchise compliance team audits department and role assignments quarterly to confirm labor-law compliance across 12 franchise locations. They used to export CSVs from 7shifts, then reconcile them in spreadsheets. The 7shifts MCP's Get User Assignments and List Departments tools let them ask Switchy 'show me all users assigned to kitchen roles at the north location' and spot mismatches on the spot. The Delete Department tool with transfer logic means they can consolidate redundant departments without orphaning shifts. This scenario only works if your franchise has standardized department naming—if every location invents its own structure, the MCP can't surface patterns. For teams auditing 8+ locations monthly, the MCP cuts review time from two days to two hours.

When 7shifts MCP speeds new-hire department setup

A two-person HR team at a 40-employee restaurant group onboards 4-6 hires a month, each needing department and role assignments at one or two locations. They used to log into 7shifts per hire, click through location dropdowns, then confirm assignments in a separate checklist. The 7shifts MCP's Create Department and Get User Assignments tools let them run a Switchy prompt like 'set up Sarah in front-of-house at both downtown locations' and verify the result without leaving the workspace. The List Locations tool surfaces the right IDs so they're not guessing. This is overkill if you onboard fewer than three people a month—manual setup is fine. But once you're onboarding weekly and juggling multiple locations, the MCP turns a 20-minute task into a 90-second confirmation.