One config block, eleven tools
Paste one config block into your MCP client and the same eleven tools Alan uses become callable inside it.
Alan, your operator
Your AI tools, plugged straight into your shop.
Connect Cursor, Claude Desktop, or anything that speaks MCP, and your AI queries your live inventory, BOMs, orders, and schedule.
Cursor config · settings.json
{
"mcpServers": {
"turingdock": {
"url": "https://mcp.turingdock.com/mcp",
"headers": {
"x-workspace-slug": "elastic-energy"
}
}
}
}Then, inside Cursor
You: what should I count today on the Elastic Energy shop?
Cursor: Pulling your top count recommendations…
EM-100, SCREW-M3, VREG-3V3, HEATSHRINK-3, ATMEGA328P. PCB-RAW is also urgent (current 24 vs reorder 60); you counted it 3 hours ago though.
The new way
How this works in the future of MRP.
Before TuringDock, pulling live inventory or BOM data into Cursor or Claude Desktop meant exporting a CSV or copying numbers by hand. Now those tools query and act on your real shop directly over MCP.
How it works
Acts on your live shop
A cycle count from Cursor writes the same event the app would. It’s the real action surface, not a read-only mirror.
Workspace-scoped
Each connection is bound to one workspace by a slug in your config, so calls only ever touch that shop.
Premium beta
This surface is part of the premium beta. Book a call with the founder to shape what your team would use it for.
Related features
Build what’s next.
Leave the MRPing to our AI. Free to start, set up in an afternoon.
Get started for freeLast updated 2026-05-25