Enables AI assistants to perform 2D panel, 1D bar, timber, and true-shape nesting cutting optimization via the CutOptim API.
Also known as cutoptim/engine-mcp, engine-mcp, @cutoptim/mcp
- Stars
- 0
- Tools
- 6
- Downloads, 30 days
- 391
- Latest version
- 0.1.2
- Last commit
- Nov 10, 2026
- License
- MIT
What is CutOptim Engine MCP?
CutOptim Engine enables AI assistants to perform 2D panel, 1D bar, timber, and true-shape nesting cutting optimization via the CutOptim API. It exposes 6 tools, such as optimize_2d, optimize_1d, optimize_wood.
Summary generated from the project's README
About CutOptim Engine MCP server
CutOptim Engine provides specialized cutting optimization capabilities for AI assistants through the Model Context Protocol. It allows users to calculate efficient layouts for various materials including 2D panels, 1D bars, timber, and true-shape nesting for free-form polygon parts. Developers can integrate these capabilities into clients like Claude Desktop, Cursor, VS Code, or Claude Code.
Users can connect via a hosted setup by pointing their client to the CutOptim API endpoint with a Bearer token or run it locally using npx. The server requires a CUTOPTIM_API_KEY to access optimization tools, though validation tools remain free without one. The system includes specific tools such as optimize_2d, optimize_1d, optimize_wood, and optimize_nest to handle different material geometries. It also provides get_job and get_usage tools to manage asynchronous tasks and monitor monthly quotas.
Written from the project's README. Every use case is checked against a quote from it.
How to install CutOptim Engine MCP
Formats verified 10 Nov 2026Install CutOptim Engine MCP in Claude Code
$ claude mcp add --env CUTOPTIM_API_KEY=<YOUR_CUTOPTIM_API_KEY> engine-mcp -- npx -y @cutoptim/mcpInstall CutOptim Engine MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"engine-mcp": {
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp"
],
"env": {
"CUTOPTIM_API_KEY": "<YOUR_CUTOPTIM_API_KEY>"
}
}
}
}Install CutOptim Engine MCP in VS Code
.vscode/mcp.json
{
"servers": {
"engine-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp"
],
"env": {
"CUTOPTIM_API_KEY": "<YOUR_CUTOPTIM_API_KEY>"
}
}
}
}Install CutOptim Engine MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"engine-mcp": {
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp"
],
"env": {
"CUTOPTIM_API_KEY": "<YOUR_CUTOPTIM_API_KEY>"
}
}
}
}Install CutOptim Engine MCP in Codex
~/.codex/config.toml
[mcp_servers.engine-mcp] command = "npx" args = ["-y", "@cutoptim/mcp"] [mcp_servers.engine-mcp.env] CUTOPTIM_API_KEY = "<YOUR_CUTOPTIM_API_KEY>"
Install CutOptim Engine MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"engine-mcp": {
"command": "npx",
"args": [
"-y",
"@cutoptim/mcp"
],
"env": {
"CUTOPTIM_API_KEY": "<YOUR_CUTOPTIM_API_KEY>"
}
}
}
}CutOptim Engine MCP tools 6
Detected from the READMEoptimize_2doptimize_1doptimize_woodoptimize_nestget_jobget_usage
| optimize_2d | — | |
| optimize_1d | — | |
| optimize_wood | — | |
| optimize_nest | — | |
| get_job | — | |
| get_usage | — |
Configuration
CUTOPTIM_API_KEYSecretYour CutOptim API key (co_live_…, co_test_…, or the public demo key). Not needed for validate_*.
| Name | Description | |
|---|---|---|
| CUTOPTIM_API_KEY | Your CutOptim API key (co_live_…, co_test_…, or the public demo key). Not needed for validate_*. | Secret |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubTwo ways to connect
Hosted (no install) — point your MCP client at https://api.cutoptim.com/mcp with the header
Authorization: Bearer <your API key>. 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.
Tools
| 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.
Quota and billing
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.
License and support
MIT. This repository is published from the CutOptim monorepo; report a bug in Issues or write to support@cutoptim.com.
CutOptim Engine MCP questions
How do I add CutOptim Engine MCP to Claude Code?
Run claude mcp add --env CUTOPTIM_API_KEY=<YOUR_CUTOPTIM_API_KEY> engine-mcp -- npx -y @cutoptim/mcp in your terminal. Add --scope user to make it available in every project.
How do I add CutOptim Engine MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does CutOptim Engine MCP provide?
It exposes 6 tools, including optimize_2d, optimize_1d, optimize_wood, optimize_nest, get_job.
How can I connect to the CutOptim MCP server?
You can connect via a hosted version by pointing your client to the API URL with a Bearer token, or run it locally using npx with your API key.
Are there any free tools available?
Yes, validation tools, reading async jobs, and checking usage are free.
How does billing work for tool calls?
Each optimization tool call counts as one Engine API call, following the same quota and billing rules as the REST API.