Reads your agreement
Proposes each working-time rule with the clause it comes from. The document stays with your assistant.
Connect Claude to the Chrona MCP server and your Dataverse tools. Claude installs Chrona, then sets up Chrona Workforce Scheduler with you.
claude mcp add --transport http chrona https://mcp.chrona365.com/mcp
claude mcp add dataverse -t stdio -- npx -y @microsoft/dataverse mcp https://yourorg.crm.dynamics.com
In Claude Code, run the first command. In Claude Desktop or on the web, add https:// as a custom connector.
In Claude Code, run the second command. In Claude Desktop, add the same npx @microsoft/dataverse command as a local MCP server. Your admin approves the Dataverse CLI once.
Copy the prompt and name your environment. Claude reads your data first and asks before it writes.
Use the Chrona MCP server at https://mcp.chrona365.com/mcp and my Dataverse tools for https://yourorg.crm.dynamics.com. If the server is not connected, help me connect it first. Read the agreement I attached and propose the rules for Chrona Workforce Scheduler, each with its clause number. Show me the list and wait for my OK before you write anything.
Replace yourorg with your environment’s address.
The Chrona MCP server gives your assistant the guides and the steps. Your assistant asks, then makes each change with your Dataverse tools.
Proposes each working-time rule with the clause it comes from. The document stays with your assistant.
Checks how your Excel roster’s codes and columns map to shifts, workers and leave.
Builds the export format and your payroll codes from a sample file you give it.
Prepares the CMS PBJ or PpUGV report with the codes for each role.
Adds on call at the workplace and on call from home as shift types, with their coverage.
Gives you a link to the board on the day you name. Nothing runs until you press Auto Schedule.
The Chrona MCP server gives guidance and plans. It makes no change in your environment.
A roster must keep every Must rule for every worker across the whole period at once. Auto Schedule, a constraint solver built on Timefold, does that. You review its proposal before you publish.
Claude sets Chrona up and opens the board. Auto Schedule, a constraint solver built on Timefold, builds the roster within every Must rule. You review it and publish.
Yes. Claude Code imports the solution, maps your columns and configures the board, and asks you to confirm each choice.
Claude Code, Claude Desktop and Claude on the web. Each one adds the Chrona MCP server; Claude Code and Claude Desktop also reach your Dataverse tools.
The Dataverse CLI, once, in the Power Platform admin center, and consent for its app in your tenant. Microsoft documents both steps.
No. It holds no credentials for your environment and makes no change. Claude makes each change with your Dataverse tools, under your identity.
The Chrona MCP server is free. Your Claude plan applies. Chrona Workforce Scheduler is priced per worker.
Start Chrona Workforce Scheduler, then connect your assistant.