Evidence-led infrastructure for engineering agents.
Open-source MCP servers and supporting tools for system models, simulation, manufacturing checks, and operational workflows.
Website · Repositories · LinkedIn · Contact
Casys is an independent R&D studio based in Taiwan. We build focused, composable infrastructure around engineering and business systems.
Our products favour explicit contracts, reproducible execution, and structured results that can move across models, solvers, agents, and teams.
system architecture → geometry → physics → measured checks → reviewable evidence
- mcp-syson — SysON-backed SysML v2 modelling, queries, diagrams, requirements tracing, and constraint workflows.
- mcp-build123d — parametric CAD with OCCT measurements and verifiable STEP, STL, and GLB exports.
- mcp-onshape — access to Onshape CAD and PDM workflows.
- mcp-calculix — STEP-based finite-element analysis with Gmsh and CalculiX.
- mcp-modelica — OpenModelica execution of qualified simulation kits.
- mcp-spice — ngspice operating-point and transient observations from content-addressed circuit netlists.
- mcp-chrono — prescribed rigid-body kinematics with Project Chrono and recorded run evidence.
- mcp-dfm — measured DFM checks on STEP geometry against caller-declared limits.
- mcp-prusaslicer — time and material statistics from exact STL and caller-owned PrusaSlicer profiles.
- mcp-tolerance — deterministic ISO 286-1 fits and one-dimensional tolerance stacks.
- constraint-solver — unit-aware constraint evaluation, satisfiability, and optimisation.
- mcp-server — a TypeScript framework for MCP middleware, OAuth integration, concurrency, observability, and MCP Apps.
- mcp-erpnext — ERPNext/Frappe documents, workflows, and interactive MCP App viewers.
- mcp-einvoice — French e-invoicing workflows and structured invoice formats through configurable provider adapters.
Casys also maintains acpx, a headless client for stateful ACP sessions.
Our extraction toolkits cover e-commerce storefronts and learning platforms. Browse all public repositories.
Start with one capability, then connect others as the workflow grows. Follow each repository for its setup and examples.