Koddex MCP Server
Your LLM client, wired straight into the model.
Connect Claude, ChatGPT, or Gemini to the Koddex MCP server and let them read, build, and edit your engineering data, under the exact same permissions and audit trail as your team.
Build entire models from a prompt.
Ask in plain language and the agent assembles the full structure through Koddex tools: assemblies, sub-components, linked requirements and certifications, created as native governed entities, not text in a chat window.
- 6-axis robot arm ISO 10218-1
- └Base assembly
- └Axis 1 · Shoulder ISO/TS 15066
- └Servomotor 750 W
- └Harmonic reducer
- └Absolute encoder
- └Axis 2 · Lower arm
- └Servomotor 400 W
- └Axis 3–6 + end effector
AI and engineers on the same canvas.
Agents and humans work the live model side by side. Every edit is attributed, permission-checked, and traceable. The AI is just another principal on your engineering graph.
Agents that act inside your model.
Spin up agents that read, write, and propose changes on your engineering graph, scoped to the entities they're allowed to touch, fully audited.
Impact Analyst
Computes downstream impact of any proposed change
Compliance Scanner
Maps requirements to ISO 13485, MDR, AS9100 clauses
Test Drafter
Generates test cases from requirement specifications
Same access model as humans.
An AI agent is just another principal. Give it scoped read/write rights on specific entities, in specific projects, gated by the same approval workflow you use for engineers.
- Read-only on Released baselines
- Write on draft Requirements (subsystem: Powertrain)
- Cannot modify Risk items (ISO 14971)
- Must request approval for entities under Baseline v1.2
Engineering workflows, no-code.
Trigger anything from anything. "When requirement changes → notify reviewers, recompute coverage, flag impacted tests." All inside the model.
Requirement edited
- Recompute coverage
- Flag impacted tests
- Notify lead
Baseline frozen
- Lock all entities
- Hash + archive
- Export DHF section
Change request opened
- Run impact analysis
- Route to reviewers
- Block conflicting edits
Automate what should never have been manual.
Baselines propagating to downstream programs. Compliance reports generating themselves. Traceability matrices staying in sync. The mechanical work of engineering ops, done.