SmartCut

dev.smartcut由 smartcut.dev 发布官方发布者v1.0.0更新于 Nov 2, 2026

Cutlist optimization for sheet, linear and roll stock, with grain, kerf, nesting and saw exports.

已验证Streamable HTTP可网页运行开发者工具商业与电商

概览

AI 生成的概览

托管式 SmartCut MCP 服务器，让助手对板材、线材和卷材进行下料优化，并导出可直接上锯的排版结果。

可以做什么
  • 提交、校验和取消下料优化任务，查询状态并获取排版结果
  • 将结果导出为 PDF、CSV、DXF、SVG、PTX、Biesse XML 或 Mayer .may，并列出锯机及其支持的格式
  • 根据结果生成可打印的零件标签
  • 查询 API 用量统计
  • 把从 PDF 或切割图照片中提取的零件推送到打开的 Cutlist Evolution 编辑器中供用户确认
适用场景
适用于报价、按尺寸切割订单处理、电商下单和 CAM 交接等场景，希望获得高质量优化和机器可读的锯切输出，又不想自行维护几何引擎。若需要无需联网、无需账号的进程内排样库，则不适合。
运行要求
远程 streamable HTTP 端点 api.smartcut.dev，无需本地安装包。需要 SmartCut API 密钥，以原始值放在 Authorization 请求头中，不能加 Bearer 前缀。需要付费订阅账号，并能访问该服务的网络。
安装前请注意
API 密钥是可计费的凭据，须保密并以原始形式发送，加 Bearer 前缀会返回 401。该服务为订阅制，调用可能消耗付费额度，可用 usage 工具查看用量。import_parts 会向打开的 Cutlist Evolution 编辑器写入零件，calculate 会把任务提交给第三方托管服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 SmartCut，将其添加到工作区。
  2. 连接 Authorization token 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/dev.smartcut%2Fcutlist-optimizer/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "smartcut": {
      "type": "http",
      "url": "https://api.smartcut.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

SmartCut API

SmartCut is a hosted cutting-optimisation (cutlist / nesting) API for sheet, linear and roll stock. This repository holds the OpenAPI specification, runnable examples and MCP configuration for integrating it into your own software.

[Licence: MIT] [OpenAPI 3.0] [Docs]

What it does

  • Sheet optimisation — guillotine (edge-to-edge, saw-cuttable) and efficiency modes for plywood, MDF, glass, plastic and sheet metal.
  • Linear (1D) optimisation for timber, bar, pipe and extrusion.
  • True-shape nesting for irregular parts from DXF, for laser, plasma, waterjet and CNC routing.
  • Grain direction and per-part orientation locks, so a part can be pinned to the length or width of the grain, or left free to rotate.
  • Edge banding, face finishes, blade kerf and stock trim as first-class inputs, not post-processing.
  • Machine-ready exports — PDF, CSV, DXF, SVG, and native saw formats including PTX (Homag), Biesse XML and Mayer .may.
  • Printable part labels generated from the same result.

Quickstart

Get a key at https://smartcut.dev/account, then:

bash
curl -X POST https://api.smartcut.dev/v3/calculate \  -H "Authorization: $SMARTCUT_API_KEY" \  -H "Content-Type: application/json" \  -d @examples/requests/guillotine.json

That returns a job id. Poll until it is ready, then fetch the result:

bash
curl "https://api.smartcut.dev/v3/result/ready?id=$JOB_ID" -H "Authorization: $SMARTCUT_API_KEY"curl "https://api.smartcut.dev/v3/result?id=$JOB_ID"       -H "Authorization: $SMARTCUT_API_KEY"

The result carries one entry per stock piece, each listing the parts placed on it with their positions, the cuts needed to produce them, and the offcut left over. Complete runnable versions in four languages are in examples/.

Authentication

Pass the raw API key in the Authorization header:

Authorization: YOUR_API_KEY

There is no Bearer prefix. This is the single most common integration mistake — a Bearer prefix returns 401.

Endpoints (v3)

methodpathwhat it doessync
POST/v3/calculateSubmit calculationasync
POST/v3/validateValidate inputs without calculatingsync
POST/v3/model/analysisAnalyse a 3D model into partssync
GET/v3/result/readyCheck if calculation is completesync
GET/v3/resultRetrieve calculation resultsync
GET/v3/export/pdfExport result as PDFsync
GET/v3/export/csvExport result as CSVsync
GET/v3/export/ptxExport result as PTXsync
GET/v3/export/dxfExport result as DXFsync
GET/v3/export/svgExport result as SVGsync
GET/v3/export/mayerExport result as Mayer .maysync
GET/v3/export/biesseExport result as Biesse XML CutListsync
GET/v3/sawsList saws and the export formats each offerssync
POST/v3/labelsGenerate printable part labelssync
POST/webhooks/resultCalculation result delivery— your endpoint
GET/v3/callsGet API usage statisticssync

Full reference: https://smartcut.dev/api-docs/v3

How the async model works

Optimisation takes longer than a request should block for, so /v3/calculate returns a job id immediately. You then either poll /v3/result/ready until it reports done, or register a webhook and let SmartCut POST to you when the result is available. Either way you fetch the payload from /v3/result.

Webhook registration, signature verification and retry behaviour are documented at https://smartcut.dev/docs/webhooks.

MCP server

SmartCut runs a hosted Model Context Protocol server, so an agent can run optimisations directly with your existing API key.

POST https://api.smartcut.dev/mcp

Streamable HTTP transport. Authentication is the same raw key in the Authorization header, without a Bearer prefix. Configuration for Claude Desktop and other clients is in mcp/.

Tools: calculate, validate, status, result, cancel, usage, export, labels, list_cut_types — plus import_parts, which is different from the rest: it pushes parts an agent has extracted (from a PDF or a photo of a cutting plan) into an open Cutlist Evolution editor for the user to confirm, rather than calling the optimisation API.

The calculate tool waits for the result in-call (about 25 seconds by default, overridable with waitMs) and falls back to returning a job id if the optimisation is still running, so an agent usually gets a layout in one call.

Generating a client

There is no official SDK, and that is deliberate. The API is a JSON body and one header, so fetch is already the client — and a generated client in your own idiom will fit your codebase better than a hand-written one would. Point any generator at the spec:

bash
npx openapi-typescript openapi/v3.json -o smartcut.d.tsnpx @hey-api/openapi-ts -i openapi/v3.json -o src/smartcutopenapi-generator-cli generate -i openapi/v3.json -g python -o ./smartcut-python

Examples

languagefile
curlexamples/curl/optimise.sh
Nodeexamples/node/optimise.mjs
Pythonexamples/python/optimise.py
PHPexamples/php/optimise.php

Each reads a payload from examples/requests/, which is generated from the specification — so the examples cannot drift from the schema.

What this is, and is not

SmartCut is a hosted service with a subscription, not a self-hosted library. It suits quoting, order processing, e-commerce cut-to-size checkout and CAM hand-off, where you want optimisation quality and saw-format output without maintaining a geometry engine. If you want an in-process bin-packer with no network call and no account, this is the wrong tool and an open-source packing library is the right one.

Links

Support

Issues here are for the specification and the examples only. For API access, billing, quota or integration support, use the contact form at https://smartcut.dev/contact. Specification files are generated and cannot be changed by pull request — see openapi/README.md.

来源：README.md，提交 46b15af

工具

0
该服务器需要 API 密钥等凭据，因此 SourceWeft 无法在没有凭据的情况下读取其工具，也未收录。

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。