CutOptim Engine

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 电脑或云端
• 传输方式: stdio, Streamable HTTP
• 分类: 其他
• 你需要填写：CUTOPTIM_API_KEY, Authorization

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接
• npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

{
  "mcpServers": {
    "engine": {
      "command": "npx",
      "args": [
        "-y",
        "@cutoptim/mcp"
      ],
      "env": {
        "CUTOPTIM_API_KEY": "your-value"
      }
    }
  }
}

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/mcp

{
  "mcpServers": {
    "engine": {
      "url": "https://api.cutoptim.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "mcpServers": {
    "engine": {
      "command": "npx",
      "args": [
        "-y",
        "@cutoptim/mcp"
      ],
      "env": {
        "CUTOPTIM_API_KEY": "your-value"
      }
    }
  }
}

{
  "servers": {
    "engine": {
      "type": "http",
      "url": "https://api.cutoptim.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "engine": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cutoptim/mcp"
      ],
      "env": {
        "CUTOPTIM_API_KEY": "your-value"
      }
    }
  }
}

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• CUTOPTIM_API_KEY 机密 env
  Your CutOptim API key (co_live_…, co_test_…, or the public demo key). Not needed for validate_*.
• Authorization 机密 HTTP header
  Bearer followed by your CutOptim API key (co_live_…, co_test_…, or the public demo key). Not needed for validate_* and tools/list.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• optimize_2d

  Metered: 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_1d

  Metered: 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_wood

  Metered: 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_nest

  Metered: 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_2d

  Free, 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_1d

  Free, 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_wood

  Free, 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_nest

  Free, 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_job

  Free (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_usage

  Free (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.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ✓ 通过

  作者与仓库一致

  注册名称已通过 GitHub 账户 cutoptim 验证，该账户拥有此仓库

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 700 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 10 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 18372 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 18372 个服务器的 72% 更新
• 基础检查结果等于或优于此分类中其他 18372 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{