Arclyn AV Studio

From system connections to delivery documents

Build AV schematics, manage device and port definitions, and generate equipment and cable schedules. Connect a compatible AI assistant through MCP to help with project tasks.

MCP: connect AI to engineering data

  • Search device models and port definitions in your library. Review equipment candidates before adding them to a project.
  • Add devices, connect ports, and update drawings in visible steps. Review the result in Arclyn and undo individual steps when needed.
  • Use local MCP to keep an editable .avpoj project and export DXF drawings, equipment lists and cable schedules. For Copilot Studio, save and export in the desktop app.

Requires a configured MCP-compatible AI client and an activated, running version of Arclyn with MCP support. AI service comes from your chosen client. An engineer must review designs and deliverables.

Structured Project Model

  • Project workspaces with schematic, library, and signal layers.
  • Dedicated formats for project, schematic, library, and backup files.
  • Single data source drives drawing, reports, and PDF outputs.

Drawing Environment

  • Device placement, cable drawing, annotations, and zone objects.
  • Grid snap and route editing with manual control points.
  • Context-aware properties for drawing, device, cable, and note editing.

Device Library and I/O

  • Template-based equipment library with reusable device definitions.
  • I/O editor for inputs, outputs, connector types, and signal mapping.
  • Dictionary growth for manufacturers, categories, and connector sets.

Cable and Connector Logic

  • Signal-aware cable numbering and style rules.
  • Support for connector markers and special link semantics.
  • Persistent routing data to keep paths stable across reopen cycles.

Reports and Data Validation

  • Export BOM CSV, Cable CSV, and Project JSON outputs.
  • Data environment for consistency checks before delivery.
  • Aligned naming and field mapping across canvas and exports.

PDF Delivery and Reliability

  • Project title block standards and batch PDF generation.
  • Auto-save, backup strategy, and close-guard save confirmation.
  • License token workflow with local integrity checks.

Which MCP connections does Arclyn provide?

Arclyn includes connection setup for Codex and Claude Desktop, plus a dedicated Microsoft Copilot Studio interface. This describes the current application implementation; use a release with these settings.

SoftwareBuilt into ArclynArclyn connection pathWhere to configureAvailable operations
CodexAutomatic configurationLocal MCP · stdioSettings → AI Assistant Connection → CodexLocal MCP: library search, project reading, incremental drawing edits, validation, file imports and delivery exports.
Claude DesktopAutomatic configurationLocal MCP · stdioSettings → AI Assistant Connection → Claude DesktopLocal MCP: library search, project reading, incremental drawing edits, validation, file imports and delivery exports.
Microsoft Copilot StudioDedicated interface · deployment requiredRemote · Streamable HTTPSettings → AI Assistant Connection → Microsoft Copilot StudioOpen project only: read, library search, preview and edit, validate, undo/redo, and canvas navigation. Save and export in the Arclyn desktop app.

Codex / Claude Desktop: configure in Arclyn, then fully quit and reopen the AI client. Arclyn provides configuration viewing, copying, backups and an MCP service test. Passing that test does not confirm the client has loaded the tools.

Copilot Studio: Arclyn provides Streamable HTTP and API key authentication. Configure your own HTTPS gateway or tunnel to the local interface and keep an activated Arclyn editor and project open. Entering a URL does not establish cloud connectivity.

Other stdio clients may be configured manually in their own format; they are not listed as built-in Arclyn integrations. Claude Desktop automatic setup does not configure Claude Code or the web app.

View Pricing Download Info Contact Sales