CutOptim Engine
Cutting optimization: 2D panels, 1D bars, timber and true-shape nesting via the CutOptim API.
Connect it
Settings → Connectors → Add custom connector
URL: https://api.cutoptim.com/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://api.cutoptim.com/mcp{
"mcpServers": {
"engine": {
"url": "https://api.cutoptim.com/mcp",
"headers": {
"Authorization": "<YOUR_AUTHORIZATION>"
}
}
}
}claude mcp add --transport http engine https://api.cutoptim.com/mcp --header "Authorization: <value>"{
"servers": {
"engine": {
"type": "http",
"url": "https://api.cutoptim.com/mcp",
"headers": {
"Authorization": "<YOUR_AUTHORIZATION>"
}
}
}
}{
"mcpServers": {
"engine": {
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp@0.1.0"
],
"env": {
"CUTOPTIM_API_KEY": "<value>"
}
}
}
}claude mcp add engine -- npx -y @cutoptim/mcp@0.1.010 tools, pulled live
optimize_2dMetered: one Engine API call. Cut rectangular parts from sheets (panels, plywood, glass, sheet metal) and get the layout, cut plan and yield. 2D panel optimization. Nest rectangular parts into rectangular sheets. Returns the placement of every part, the remaining offcuts, the guillotine cut plan and the yield metrics. Parts named in `matchedSets` (grain matching) are cut side by side from one piec
optimize_1dMetered: one Engine API call. Cut lengths from bars, tubes, profiles or rolls and get the cutting pattern per bar. 1D / linear optimization (bars, profiles, tube). Cut parts of a given length from stock bars. Returns the rods used, the position of every part along each rod, the leftover length and the yield metrics.
optimize_woodMetered: one Engine API call. Cut timber parts grouped by cross-section from matching stock lengths. Timber optimization (cross-section-aware 1D). Cut lengths from bars that have a CROSS-SECTION. Unlike `/v1/optimize/1d`, where every bar can serve every part, a 50×150 part can only come out of 50×150 stock — so the job is split by cross-section, each section is matched to its own stock and solved
optimize_nestMetered: one Engine API call (needs an API key; not available with the demo key). Nest free-form polygon parts on sheets. True-shape (irregular / polygon) nesting. Pack ARBITRARY POLYGONS onto fixed sheets, letting parts interlock into each other's concave pockets — an L-bracket, a gasket, a laser-cut profile. This is a different class from the rectangular modes: a part is an outline (`polygon`, o
validate_2dread-onlyFree, no key needed: checks a 2D request without solving it. Same arguments as optimize_2d (field descriptions there). Validate a 2D request — free, no key, no quota, no solve. Schema-validate the SAME body `/v1/optimize/2d` takes, WITHOUT solving or spending a call. 200 `{valid:true, warnings}` (warnings flag parts that fit no stock — an approximate, solve-free probe), or 400 with the exact bad f
validate_1dread-onlyFree, no key needed: checks a 1D request without solving it. Same arguments as optimize_1d (field descriptions there). Validate a 1D request — free, no key, no quota, no solve. Schema-validate the SAME body `/v1/optimize/1d` takes, WITHOUT solving or spending a call. See `/v1/validate/2d`.
validate_woodread-onlyFree, no key needed: checks a timber request without solving it. Same arguments as optimize_wood (field descriptions there). Validate a wood request — free, no key, no quota, no solve. Schema-validate the SAME body `/v1/optimize/wood` takes, WITHOUT solving or spending a call. Warnings flag parts with no matching-section stock long enough. See `/v1/validate/2d`.
validate_nestread-onlyFree, no key needed: checks a nesting request without solving it. Same arguments as optimize_nest (field descriptions there). Validate a nest request — free, no key, no quota, no solve. Schema-validate the SAME body `/v1/optimize/nest` takes, WITHOUT solving or spending a call. Reports `engineEnabled` (whether the nesting engine is built into this deployment) and warns about parts whose bounding b
get_jobread-onlyFree (needs the key that submitted the job). Reads an engine "max" job; when it succeeded, the plan is in result. Poll an async max-engine job. Fetch the status (and, when finished, the plan) of a job submitted with `engine: "max"`. A job is `queued`, then `running`, then `succeeded` (with `result` = the same response shape a synchronous solve of that `mode` returns, carrying `engine: "max"` — a 2
get_usageread-onlyFree (needs an API key). Shows the plan, the calls used and left this month, and when the period ends. The account's current-month usage and quota. Read-only. Does not consume quota and does not send rate-limit headers. The period is the UTC calendar month.
Alternatives in Developer Tools
Compare →SMSentry MCPOfficialA
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
Compiler ExplorerA
Compile code with thousands of compilers, inspect the assembly, and share godbolt.org links
MIMiroOfficialA
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
Context7A
Up-to-date docs for AI agents
OMOmnaraA
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
AAAirbyte AgentsOfficialA
Let AI agents query data and act across all your business apps via MCP.