ShapeItUp MCP server
Commit 13 Okt 2026Memungkinkan AI agent untuk membuat, me-render, memverifikasi, dan mengekspor model 3D CAD parametrik menggunakan TypeScript dan OpenCascade.
Juga dikenal sebagai asbis/ShapeItUp
- Stars
- 6
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- —
- Commit terakhir
- 13 Okt 2026
- Lisensi
- MIT
Apa itu ShapeItUp MCP?
ShapeItUp adalah MCP server. Memungkinkan AI agent untuk membuat, me-render, memverifikasi, dan mengekspor model 3D CAD parametrik menggunakan TypeScript dan OpenCascade.
Ringkasan dibuat dari README proyek
Tentang ShapeItUp MCP server
ShapeItUp menyediakan toolkit khusus bagi AI agent untuk menangani pemodelan 3D CAD parametrik menggunakan TypeScript dan OpenCascade. Tool ini memungkinkan workflow end-to-end di mana agent dapat membuat, me-render, memverifikasi, dan mengekspor model 3D melalui interface headless. Server ini beroperasi via stdio dan kompatibel dengan berbagai client MCP termasuk Claude Code, Cursor, Claude Desktop, Codex, dan Mistral Vibe. Anda memerlukan Node 20 atau versi yang lebih tinggi untuk menjalankannya.
Developer dapat menggunakan 29 tools yang tersedia untuk mengelola seluruh siklus desain. Ini mencakup pembuatan dan modifikasi bentuk, me-render preview dalam format PNG, serta melakukan verifikasi geometris seperti pengecekan collision atau stack. Sistem ini mendukung ekspor file dalam format STEP, STL, dan 3MF. Karena menggunakan WASM, ShapeItUp tidak memerlukan GPU atau native graphics stack, sehingga sangat cocok digunakan di lingkungan CI seperti GitHub Actions atau container Docker.
Apa yang bisa Anda lakukan dengannya
- 1Verifikasi integritas geometrisDeveloper dapat memberikan tugas kepada AI untuk memeriksa apakah komponen dalam sebuah desain mengalami collision atau apakah sambungan (joints) sudah valid.
- 2Iterasi pada parameter desainAlih-alih menulis ulang seluruh file, agent dapat menyesuaikan nilai spesifik menggunakan slider overrides untuk menyempurnakan model.
- 3Ekspor model untuk manufakturAI agent dapat mengonversi desain berbasis script menjadi format file 3D standar untuk kebutuhan produksi.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauasbis/shapeitup is public and reachablegithub.com/asbis/shapeitup ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-13github.com/asbis/shapeitup ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubShapeItUp is an MCP server that turns Replicad / OpenCascade into AI-agent-grade CAD tooling. It writes, renders, verifies, and exports parametric 3D models from TypeScript .shape.ts files, headlessly — from the terminal, from Claude Code / Codex / Cursor / Claude Desktop / Mistral Vibe, or from CI. A VSCode extension is available as an optional interactive viewer for humans who want to watch the renders happen live.
Install for Claude Code
claude mcp add shapeitup -- npx -y @shapeitup/mcp-server
That's it. claude mcp add registers the server in your Claude Code config so agent sessions pick it up automatically. See the Claude Code MCP docs for scoping options (-s user for all projects, -s project for just this repo).
Install for Codex
codex mcp add shapeitup -- npx -y @shapeitup/mcp-server
Then raise the timeouts in ~/.codex/config.toml, under the entry that command wrote:
[mcp_servers.shapeitup]
command = "npx"
args = ["-y", "@shapeitup/mcp-server"]
startup_timeout_sec = 60
tool_timeout_sec = 180
Keep both. Codex gives a server 10 s to start, and the first npx run downloads the package, which can take half a minute. It gives a tool 60 s, and a cold render of complex geometry can need more. The Codex CLI, the IDE extension and the ChatGPT desktop app share this file. Check with codex mcp list, or /mcp inside Codex.
For the Replicad API reference, save SKILL.md where Codex looks for skills:
mkdir -p ~/.agents/skills/shapeitup && curl -fsSL https://raw.githubusercontent.com/asbis/ShapeItUp/master/skills/shapeitup/SKILL.md -o ~/.agents/skills/shapeitup/SKILL.md
Install for Cursor / Claude Desktop / other MCP clients
The generic MCP-config snippet:
{
"mcpServers": {
"shapeitup": {
"command": "npx",
"args": ["-y", "@shapeitup/mcp-server"]
}
}
}
Where to put it:
- Cursor —
~/.cursor/mcp.json, or Settings → MCP → Add new server to drop it in through the UI. - Claude Desktop —
~/Library/Application Support/Claude/claude_desktop_config.jsonon macOS,%APPDATA%\Claude\claude_desktop_config.jsonon Windows. Restart the app after editing. - Mistral Vibe — TOML rather than JSON; see below.
- Any stdio MCP client — hand it
npx -y @shapeitup/mcp-serveras the server command.
Mistral Vibe
Append to ~/.vibe/config.toml, then run /reload in Vibe:
[[mcp_servers]]
name = "shapeitup"
transport = "stdio"
command = "npx"
args = ["-y", "@shapeitup/mcp-server"]
startup_timeout_sec = 60
Keep startup_timeout_sec: Vibe's default of 10 s is shorter than the first npx download. For the Replicad API reference, save skills/shapeitup/SKILL.md as ~/.vibe/skills/shapeitup/SKILL.md. More options, including vibe mcp add, are in the MCP server README.
Node 20+ required. No native build step; everything ships as WASM.
What you get
A CAD toolkit agents can drive end to end:
- Authoring —
create_shape,modify_shape,read_shape,list_shapes,setup_shape_project - Rendering —
render_preview,preview_shape,get_preview(SVG-first, resvg-backed PNGs),open_viewer/close_viewer(interactive browser viewer) - Verification —
verify_shape,check_collisions,check_stack,sweep_check,run_simulation,describe_geometry,validate_joints - Iteration —
tune_params(slider overrides),set_render_mode,toggle_dimensions - Export —
export_shape(STEP / STL / 3MF) - stdlib —
holes,screws/bolts/washers/inserts,bearings,extrusions,patterns,threads,joints+assemble,printHints, and more — all importable from"shapeitup"inside any.shape.ts
29 MCP tools in all — the above plus helpers such as validate_syntax, preview_finder, get_api_reference and open_shape — covering the create → preview → verify → tune → export loop.
Quick example
Prompt to the agent: "I want a mounting bracket, 60×40×4 mm, four M3 through-holes in the corners." The agent calls create_shape and writes:
// bracket.shape.ts
import { drawRoundedRectangle } from "replicad";
import { holes, patterns } from "shapeitup";
export const params = { width: 60, depth: 40, thickness: 4, holeInset: 6 };
export default function main({ width, depth, thickness, holeInset }: typeof params) {
const plate = drawRoundedRectangle(width, depth, 3)
.sketchOnPlane("XY")
.extrude(thickness);
// holes.through() returns a cutter whose opening sits at Z=0 and drills -Z;
// lift it to the top face, then cut one at each corner of a 2×2 grid.
return patterns.cutAt(
plate,
() => holes.through("M3", { depth: thickness + 2 }).translate(0, 0, thickness),
patterns.grid(2, 2, width - 2 * holeInset, depth - 2 * holeInset),
);
}
Then it calls render_preview and gets back a PNG it can inspect, plus bounding-box + volume metadata to sanity-check against the spec. If the user wants the holes bigger, the agent calls tune_params — no file rewrite needed.
Running in CI / containers
npx -y @shapeitup/mcp-server works anywhere Node 20 runs — Docker, GitHub Actions, GitLab CI. Renders go through @resvg/resvg-wasm; no GPU, no headless Chromium, no native graphics stack required. A cold boot on a stock Node image typically takes ~3 s for the first render (OCCT WASM compile) and < 200 ms thereafter.
VSCode extension (optional)
There is a VSCode extension that subscribes to the MCP server's event bus and shows a live Three.js viewer in the side panel — useful when you want to watch an agent work, or to drive ShapeItUp interactively. Install it from the VS Code marketplace (search for "ShapeItUp") or build from source (see Development).
The extension is entirely optional: the MCP server is headless on its own, does not require VSCode to be running, and produces the same renders whether or not a viewer is attached.
Development
git clone https://github.com/asbis/ShapeItUp.git
cd ShapeItUp
pnpm install
pnpm build # builds extension, viewer, worker, and mcp-server
pnpm dev # watch mode
pnpm lint # tsc -b across packages
Then press F5 in VS Code to launch the Extension Development Host if you want to iterate on the viewer.
Project layout:
packages/
mcp-server/ -- standalone MCP server (this is the npm package)
core/ -- Replicad wrappers, stdlib, execution engine (bundled into mcp-server)
shared/ -- cross-package types (bundled into mcp-server)
extension/ -- VSCode extension (optional viewer)
viewer/ -- Three.js viewer surface for the extension
worker/ -- OCCT WASM web-worker for the extension viewer
See CONTRIBUTING.md for contribution guidelines.
License
MIT
Pertanyaan tentang ShapeItUp MCP
Format file apa saja yang bisa diekspor oleh ShapeItUp?
Server ini mendukung ekspor model 3D dalam format STEP, STL, dan 3MF.
Apakah ShapeItUp memerlukan GPU atau graphics stack tertentu?
Tidak, server ini berjalan secara headless tanpa memerlukan GPU, headless Chromium, atau native graphics stack, karena menggunakan WASM untuk rendering.
Bisakah saya menggunakan ShapeItUp di lingkungan CI/CD?
Ya, ShapeItUp dapat berjalan di lingkungan apa pun yang menjalankan Node 20, termasuk Docker, GitHub Actions, dan GitLab CI.