MCP server

An MCP server for production line design

Connect Claude to Machsizer's MCP server (Model Context Protocol) and ask for a line in plain words: it writes the profile, balances and lays out the line, simulates it and tells you what limits output. The engine runs on our server, under your own account.

What a conversation looks like

“Help me put together a line for a prospective customer: 60 cabinets an hour, these six operations, our press and two welding cells.”

The assistant asks for what it does not know, such as which steps come first and how long each one takes. It does not invent figures. Then it writes a profile, checks it, runs Build layout and reads the result: the number of stations and lines, whether the line meets takt, and which stage limits it. It changes the design and builds again to compare, and gives you the project as a file to open in Machsizer, where you check it, adjust it and present it.

The tools

ToolWhat it doesEngine time
get_profile_guideHow a Machsizer profile is written: products, operations, machines, settings, with examplesnone
validate_profileOpens the profile as the app does and balances it once: is it buildable, which operations no machine can doshort
build_layoutBuild layout: line balancing, machine counts, line copies, factory layout and verification runsseconds to minutes
run_simulationRuns the built line: throughput against target, lead time, WIP, the busiest stationsseconds
explain_bottleneckWhat limits the line and why, stage by stage, with labelled suggestionsseconds

Results come back as short summaries. Results are the same as in the app, because each tool starts the same engine job as the app's buttons.

Connect Claude

You need a Machsizer account: request early access. The server address is https://app.machsizer.com/mcp.

Claude (web and desktop): Settings → Connectors → Add custom connector. Paste the address and sign in with your Machsizer account when Claude asks.

Claude Code:

claude mcp add --transport http machsizer https://app.machsizer.com/mcp

Other assistants that support remote MCP servers with OAuth sign-in connect the same way. We have tested Claude.

Your data and your engine time

The project goes to the server with each call and is not stored there. The server returns a summary and keeps nothing. Each build or run counts against your plan's engine minutes, the same as in the app. The engine itself stays on our server and never runs on your machine.

Try it on your own product.