
MCP server that gives AI assistants a real production scheduler (OR-Tools CP-SAT). Plan machines
MCP server that gives AI assistants a real production scheduler (OR-Tools CP-SAT). Plan machines, downtime and due dates from Claude, ChatGPT or Cursor.
·
A small real production scheduler for AI assistants.
AI assistants can guess production plans; this server gives them a real solver so the plan fits machines, down times and due dates. It is a small, local MCP tool from ArchiPlan.
Language models can write plans that look right but break real limits: machines get double-booked, downtime is ignored, and due dates are missed. A model cannot prove the plan works. Constraint solvers do this math well, but usually need code. This server joins them: you talk, the solver plans. OR-Tools CP-SAT is the constraint solver used here, the same kind of solver used in industry.
It is for:
It assigns ordered job steps to eligible machines, avoids machine conflicts and downtime, and minimizes priority-weighted lateness before finish time. It returns a plan per machine, late-order reasons, utilization, and a Mermaid Gantt chart. It runs locally over stdio.
You: Schedule the sample shop and protect the urgent pump's due date.
Assistant: The urgent pump finishes at 2026-01-05 11:30, before its 13:00 due time. Housing A is late by 1 hour. Reason: “Assembly-1 was busy with Urgent pump until 2026-01-05 11:30 before this step.”
gantt
dateFormat YYYY-MM-DD HH:mm
axisFormat %H:%M
section CNC-1
Flange A step 1 :CNC-1_0, 2026-01-05 08:00, 2026-01-05 10:00
Valve A step 1 :CNC-1_1, 2026-01-05 10:00, 2026-01-05 12:00
Housing B step 1 :CNC-1_2, 2026-01-05 12:00, 2026-01-05 14:30
Flange B step 1 :CNC-1_3, 2026-01-05 14:30, 2026-01-05 16:00
section CNC-2
Urgent pump step 1 :CNC-2_0, 2026-01-05 08:00, 2026-01-05 09:30
Valve B step 1 :CNC-2_1, 2026-01-05 09:30, 2026-01-05 11:00
Bracket B step 1 :CNC-2_2, 2026-01-05 14:00, 2026-01-05 16:00
section CNC-3
Housing A step 1 :CNC-3_0, 2026-01-05 08:00, 2026-01-05 11:00
Panel step 1 :CNC-3_1, 2026-01-05 11:00, 2026-01-05 13:00
Bracket A step 1 :CNC-3_2, 2026-01-05 13:00, 2026-01-05 15:30
section Assembly-1
Urgent pump step 2 :Assembly-1_0, 2026-01-05 09:30, 2026-01-05 11:30
Housing A step 2 :Assembly-1_1, 2026-01-05 11:30, 2026-01-05 13:00
Housing B step 2 :Assembly-1_2, 2026-01-05 14:30, 2026-01-05 15:30
section Assembly-2
Valve B step 2 :Assembly-2_0, 2026-01-05 11:00, 2026-01-05 12:00
Valve A step 2 :Assembly-2_1, 2026-01-05 12:00, 2026-01-05 13:00
Panel step 2 :Assembly-2_2, 2026-01-05 13:00, 2026-01-05 14:30get_example returns this five-machine, ten-order shop, with CNC-2 down for three hours. It finishes in 8.0 hours.
Only uv is needed. uvx fetches the package and a compatible Python interpreter if needed.
Claude Desktop — add under mcpServers in claude_desktop_config.json:
{"mcpServers": {"production-scheduling": {"command": "uvx", "args": ["production-scheduling-mcp"]}}}Claude Code — run:
claude mcp add --transport stdio production-scheduling -- uvx production-scheduling-mcpCursor — add to .cursor/mcp.json:
{"mcpServers": {"production-scheduling": {"command": "uvx", "args": ["production-scheduling-mcp"]}}}Hours are decimals from plan start; values are rounded to whole minutes. start is an optional ISO datetime for labels (default 2026-01-05T08:00). Steps run in the order supplied and list duration plus eligible machines. Priority defaults to 1; higher values give an order more weight when reducing lateness.
{
"start": "2026-01-05T08:00",
"machines": [{"name": "CNC-1"}, {"name": "CNC-2", "down_times": [[3, 6]]}],
"orders": [{"name": "Urgent pump", "due_hour": 5, "priority": 10, "steps": [{"hours": 1.5, "machines": ["CNC-1", "CNC-2"]}, {"hours": 2, "machines": ["Assembly-1"]}]}]
}For small and medium shops. Solve time is capped at about ten seconds. It does not model shifts, labor, inventory, setup times, or every production constraint. Check the result against your shop rules before using it.
ArchiPlan adds support for larger plans, saved plans, and team use.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add production-scheduling -- uvx production-scheduling-mcp{
"mcpServers": {
"production-scheduling": {
"args": [
"production-scheduling-mcp"
],
"command": "uvx"
}
}
}code --add-mcp '{"name":"production-scheduling","args":["production-scheduling-mcp"],"command":"uvx"}'[mcp_servers.production-scheduling]
command = "uvx"
args = ["production-scheduling-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/production-scheduling-mcp to learn what the "Production Scheduling MCP" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
claude mcp add --transport stdio production-scheduling -- uvx production-scheduling-mcpThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/production-scheduling-mcp)Nothing comparable is listed yet.
No tagged releases on record.
Connect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "production-scheduling-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.