One moment while we verify your PhysBox session.
Sign in to see every job your machines have run — across Volt, Mesh and Etch — with the settings each one was cut at, and live status for anything running right now.
New here? Read about PhysBox Pro.
Your simulators, your machine control and your local saves all keep working exactly as they do now — nothing here is being taken away.
What Pro adds is memory. Every job gets archived as it runs: how long it took, how far it got, the feed and spindle trace, the line an alarm stopped it on, and the material and power it was cut at. Then it is all readable from this page, from inside the apps, and by your own AI agent — so “what did I cut that walnut at in March” has an answer.
Signed in as .
Every run across every machine on your account.
No machine has reported in yet. A job appears here within a few seconds of starting.
| When | App | Machine | Job | Duration | Outcome | Material |
|---|
A read token lets your own AI agent query this archive over physbox-mcp with no browser open. It can read your runs and documents; it cannot drive a machine.
Add it to your MCP config:
That file is .mcp.json in your project, or your MCP client's own config —
%APPDATA%\Claude on Windows, ~/.config on Linux,
~/Library/Application Support/Claude on macOS. If you run
physbox-mcp inside WSL while browsing on Windows, the token belongs on the
WSL side, where the server actually runs. Alternatively, hand the token to your agent
once and ask it to call physbox_set_token.