Tools & integrations

Drop an .odio file and instantly see its standardized I/O table. Export SVG or a self-contained HTML page. Nothing is uploaded.

Build a valid .odio device file from a form — identity, ports, signals, power — with a live I/O-table preview. The fastest way to publish a device.

Adds the ODIOIMPORT command to AutoCAD (2018–2024): enter a device id and it draws the schematic block into your drawing, fetched live from the API. Source + build/install instructions on GitHub.

Source scaffold (.NET Framework 4.8) — build in Visual Studio against your AutoCAD. A signed release will follow.

Draws ODIO blocks onto the active Visio page via the Visio API (no stencil files) — fetched live from the API. Same draw-instruction backend as the AutoCAD add-in.

Installable MSI (from Releases) — run with Visio open; an in-ribbon add-in is planned.

A UXP panel that places the standardized I/O table onto your spec-sheet layout straight from a device id — author once, render onto your datasheet.

Downloadable .ccx (Creative Cloud installs it); Adobe Exchange listing planned. InDesign 2023+.

TypeScript SDK: generated types, an Ajv validator, bundle/chassis flattening, and the I/O-table model. The schema is the source of truth.

Renderers/adapters: the standardized I/O table (SVG/HTML), AutoCAD DXF blocks, EasySchematic, and the host-agnostic DrawProgram the native add-ins consume.

Pull any registry device by id — the raw .odio, or render-ready projections via ?format=draw (DrawProgram), table, or svg. CORS-enabled, no key.

@opendeviceio/mcp — a Model Context Protocol server so Claude and other agents search devices, fetch .odio documents and I/O tables, and validate designs (incl. chassis slot fit) as tools. Ground truth for AV/IT design assistants.