Version 1.2.0, reviewed 12 October 2026.
MCP Connector for Civil 3D lets an AI application inspect and edit Civil 3D drawings on your Windows computer. It supports Civil 3D 2022 to 2027, including surfaces, alignments, profiles, corridors, gravity and pressure pipe networks, COGO points, labels and standards, alongside the AutoCAD drawing tools. You choose and configure the AI application separately.
Tool results go to the AI application you connect. If it uses a cloud AI provider, project information is processed under your account settings and agreement with that provider. A local AI setup can keep inference on your own computer or server. Running the connector locally does not, by itself, make the AI processing local.
The connector does not send model content or tool results to AUTOM8LABS. Your AI application controls what it sends to its provider. Files, images and reports requested through tools can contain project information and can be written to locations available to your Windows account, including network shares.
Saved Civil setups can contain grading, labelling, earthwork and rule-check settings. They are kept in local files or a team folder selected by the user. Export, labelling and folder tools can also process other drawings when requested.
The free edition provides drawing inspection, measurement and navigation. Civil-specific tools require Pro, including Civil queries. Licence enforcement happens inside the Civil 3D plug-in.
Read-Only Session limits this release to the free drawing tools, even with Pro enabled. Civil-specific queries still require a normal Pro session. Reconnect the AI application after changing the setting.
Bulk changes to pipe, structure and COGO point properties, object layer settings, and Civil style purging default to a preview. Other authoring tools can change the drawing immediately. Your AI application's approval settings determine whether it asks before each call; the connector does not require a separate confirmation for every edit.
Drawing edits use Civil 3D's document and transaction mechanisms. A failed multi-step call can leave completed work in place. Use Undo where the operation supports it and keep a separate drawing copy before bulk work. File saves, exports and operations on other drawings are outside the open drawing's Undo history.
Raw command and AutoLISP execution are disabled by default and require both explicit configuration and Pro. When enabled, they have the capabilities available to commands and scripts running under your Windows account.
| Licence activation and validation | Licence key, hashed machine identifier, Windows machine name and client version. These requests go to the AUTOM8LABS licence service over HTTPS. |
|---|---|
| Floating licences | Seat acquisition, renewal and release use licence and machine information plus a session identifier. The licence dialog can retrieve the seat roster. |
| Drawing content | Not included in the connector's licence requests. Drawing information is returned to your chosen AI application. |
Without a licence configured, the connector makes no licence-related request.
With Pro, an administrator can block tools by name or permit only an approved list. These restrictions apply when tools are listed and when a call is executed, including calls inside a batch. They restrict the licensed tools; they do not grant additional access. The controls are off unless configured.
Policies can be assigned by computer or by user through Group Policy or Intune using the supplied template. Where policies overlap, the stricter tool restrictions apply. An administrator can also force Read-Only Session; the user cannot turn that lock off in the connection dialog.
The optional Pro audit log is off by default. When an administrator enables it, the connector records tool calls, including refusals and batch steps. Records contain the Windows user and computer, host version, project name or path, AI app name, tool, outcome, duration and shortened arguments and error text. These fields can contain project information. Tool results are not copied into the audit log.
An administrator can also request a short reason from the AI for each call. This is the AI's account of the request, not a copy of the user's chat. Logs are written locally and can be copied to an administrator-selected folder or network share. Local audit files are retained for 90 days; retention and access at the destination are controlled by your organisation. AUTOM8LABS does not receive them.
Audit recording is best effort. A failed write or unavailable share does not block the tool, so the log is not a guaranteed or tamper-proof record.
The v1.2.0 installer, bridge executable and AUTOM8LABS plug-in DLLs are code-signed as AUTOM8LABS LTD through Azure Trusted Signing. The release payload and signatures were checked on 12 October 2026.
This sheet describes the v1.2.0 website release, based on source review, release checks and the recorded installed-host acceptance. Release dependency checks found no known vulnerabilities in the packages checked on 12 October 2026. A dated check is not a guarantee against vulnerabilities discovered later. CycloneDX SBOMs for this release are available on request from [email protected].
See the Trust Center for company security information and the Privacy Policy for how AUTOM8LABS handles personal information.
Contact [email protected] for security questions or deployment information. Please avoid including project drawings, licence keys or other sensitive information in an initial enquiry.