Developer · Local MCP server
ParCAD
Parametric CAD as code: model 3D-printable parts on an exact B-rep kernel, measured.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ierehon1905/parcad- Version
- 0.0.11
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- MCP Bundle (.mcpb)
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- ierehon1905 (GitHub)
- Website
- github.com/ierehon1905/parcad
- Repository
- github.com/ierehon1905/parcad
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| MCP Bundle (.mcpb) | https://github.com/ierehon1905/parcad/releases/download/v0.0.11/parcad-mcp-aarch64-apple-darwin.mcpbSHA-256 checksum stated | — | stdio |
| MCP Bundle (.mcpb) | https://github.com/ierehon1905/parcad/releases/download/v0.0.11/parcad-mcp-x86_64-unknown-linux-gnu.mcpbSHA-256 checksum stated | — | stdio |
| MCP Bundle (.mcpb) | https://github.com/ierehon1905/parcad/releases/download/v0.0.11/parcad-mcp-x86_64-pc-windows-msvc.mcpbSHA-256 checksum stated | — | stdio |
How to connect ParCAD
ParCAD runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/ierehon1905/parcad/releases/download/v0.0.11/parcad-mcp-aarch64-apple-darwin.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
ParCAD runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/ierehon1905/parcad/releases/download/v0.0.11/parcad-mcp-x86_64-unknown-linux-gnu.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
ParCAD runs locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/ierehon1905/parcad/releases/download/v0.0.11/parcad-mcp-x86_64-pc-windows-msvc.mcpb. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| PAPI: Persistent Adaptive Project IntelligenceAdaptive plan/build/review cycles for AI coding assistants, persisted across sessions. | Remote & Local · HTTP, stdio |
| ParallelSandboxRemote Linux boxes for coding agents: Docker, a browser, screenshots, logs, human takeover. | Remote & Local · HTTP, stdio |
| ParaView MCP ServerControl ParaView through arbitrary Python code. | Local · stdio |
| parbakedScaffold invite-only Python/FastAPI apps: auth, admin dashboard, dev server, deploy to fly.io. | Local · stdio |
| Pare CargoPare Cargo ג€” Structured Rust cargo operations (build, test, clippy, fmt, doc) as typed JSON. | Local · stdio |
| Pare DockerPare Docker ג€” Structured Docker operations (ps, images, logs, build, compose) as typed JSON. | Local · stdio |
| Pare GitPare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON. | Local · stdio |
| Pare GithubPare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON. | Local · stdio |