Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Cutting optimization: 2D panels, 1D bars, timber and true-shape nesting via the CutOptim API.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CUTOPTIM_API_KEY, AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"engine": {
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp"
],
"env": {
"CUTOPTIM_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http engine https://api.cutoptim.com/mcp --header 'Authorization: your-value'claude mcp add engine --env CUTOPTIM_API_KEY=your-value -- npx -y @cutoptim/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"engine": {
"url": "https://api.cutoptim.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"engine": {
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp"
],
"env": {
"CUTOPTIM_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"engine": {
"type": "http",
"url": "https://api.cutoptim.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"engine": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp"
],
"env": {
"CUTOPTIM_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
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 gui
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 l
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 on
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,
validate_2dFree, 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:
validate_1dFree, 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/val
validate_woodFree, 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. Wa
validate_nestFree, 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. R
get_jobFree (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 `succee
get_usageFree (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.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account cutoptim, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 700 ms (HTTP 200)
No sign-in needed
Read 10 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: CUTOPTIM_API_KEY, Authorization
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 16 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Qemu MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Boot and drive QEMU VMs from an AI agent: keys, screenshots, serial. No guest agent.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
CutOptim MCP server
Cutting optimization as tools for AI assistants: 2D panels , 1D bars , timber and true-shape nesting ,
through the CutOptim Engine API and the Model Context Protocol.
MCP guide · API reference · Get a free test key
Hosted (no install) — point your MCP client at https://api.cutoptim.com/mcp with the header Authorization: Bearer . Configurations for Claude Code, Cursor, VS Code and Claude Desktop are in the MCP guide.
Local (this package, stdio) — runs on your machine and calls the same API with your key:
{
"mcpServers": { "cutoptim": { "command": "npx", "args": ["-y", "@cutoptim/mcp"], "env": { "CUTOPTIM_API_KEY": "co_test_YOUR_KEY" } } } }
Claude Code: claude mcp add cutoptim --env CUTOPTIM_API_KEY=co_test_YOUR_KEY -- npx -y @cutoptim/mcp
| Variable | Meaning |
|---|---|
CUTOPTIM_API_KEY | your key: co_live_…, co_test_… (never billed) or the public demo key. Without one, only the validate_* tools work. |
CUTOPTIM_BASE_URL | default https://api.cutoptim.com |
Node 18 or newer.
| Tool | What it does | Cost |
|---|---|---|
optimize_2d | rectangular parts from sheets: layout, cut plan, yield | one API call |
optimize_1d | lengths from bars, tubes, profiles | one API call |
optimize_wood | timber parts by cross-section | one API call |
optimize_nest | free-form polygon parts on sheets | one API call |
validate_2d · validate_1d · validate_wood · validate_nest | check a request without solving it | free |
get_job | read an async engine: "max" job | free |
get_usage | calls used and left this month | free |
The arguments of each tool are exactly the request body of its endpoint — the schemas are generated from the OpenAPI document. Every result carries a short summary for the assistant and the API's JSON answer as structuredContent.
One tool call is one Engine API call: the same key, quota, rate limits and billing as calling the REST API yourself. The client sends an Idempotency-Key with every optimize call, so its own retries are never charged twice.
MIT. This repository is published from the CutOptim monorepo; report a bug in Issues or write to support@cutoptim.com.