MCP Connector for Civil 3D Documentation
Complete guide to installing, configuring, and using MCP Connector for Civil 3D - 296 tools by default, including the 43 free read-only tools, driven by Claude Desktop, ChatGPT Desktop, Cursor, or Claude Code.
Supported Civil 3D Versions
- Civil 3D 2022
- Civil 3D 2023
- Civil 3D 2024
- Civil 3D 2025
- Civil 3D 2026
- Civil 3D 2027
Civil 3D 2021 and earlier are not supported. Use a 64-bit Windows installation supported by your Civil 3D release.
If you work in plain AutoCAD rather than Civil 3D, use MCP Connector for AutoCAD instead. That one covers AutoCAD 2022 to 2027. This connector already contains the AutoCAD drawing tools, so inside Civil 3D you do not need both. Each connector has its own licence.
AI Applications
- Claude Desktop
- ChatGPT Desktop
- Cursor
- Claude Code
- VS Code (GitHub Copilot agent mode)
- Visual Studio 2022 17.14+ / 2026 (GitHub Copilot)
- GitHub Copilot CLI
- Grok Build (xAI CLI)
Installation
Make sure all running instances of Autodesk Civil 3D are closed before starting the installation.
.exe file and follow the installation wizard, accepting the licence agreement and privacy policy. One install covers every supported Civil 3D release, so there is nothing to choose.MCPCONNECTORC3D_STATUS at the command line confirms it is running, and MCPCONNECTORC3D_START starts it if it is not.
Enabling MCP Connector for Civil 3D
After installation, click the MCP Connector button in the Add-ins tab to open the connector dialog, then toggle Enable MCP to start the connection. No licence key is needed for the free tools - the key only unlocks the Pro set.
The dialog shows the status of detected AI applications:
- Ready (Running) - The AI application is configured to reach Civil 3D and is currently open
- Ready - Configured, but the application is not running right now
- Detected - The application is installed but not yet configured; toggle Enable MCP to configure it
- Not Detected - The AI application is not installed on this machine
The indicator at the top of the dialog reads Disabled, Waiting, or Active. Toggling Enable MCP off again removes the connector from every detected client's configuration.
Configuration
MCP Connector for Civil 3D includes one-click auto-configuration for supported AI applications. Toggling Enable MCP in the connector dialog writes the configuration for every detected application at once. The installer also registers the server on install, so in most cases there is nothing to do by hand.
Claude Desktop
The config file is located at:
%APPDATA%\Claude\claude_desktop_config.json
The Microsoft Store build never reads %APPDATA%\Claude - Windows redirects that folder into a sandboxed package location. MCP Connector for Civil 3D detects the Store package and writes to both paths, so the Store build is configured automatically. The redirected file lives here:
%LOCALAPPDATA%\Packages\Claude_<hash>\LocalCache\Roaming\Claude\claude_desktop_config.json
If tools still do not appear, fully quit Claude from the system tray (closing the window is not enough) and reopen it.
ChatGPT Desktop
ChatGPT appears in the dialog when it is installed on your machine. The config file is located at:
%USERPROFILE%\.codex\config.toml
This file is shared with the Codex CLI, so configuring ChatGPT Desktop makes the Civil 3D tools available in Codex CLI as well. After configuring, fully quit ChatGPT and reopen it. With Civil 3D open and a drawing loaded, a quick test is to ask ChatGPT to "Check the connection to Civil 3D".
Use a local Work conversation on the computer running Civil 3D. In ChatGPT Desktop, open Settings > MCP servers and check that AUTOM8LABS_Civil3D is enabled, then select Restart. Type /mcp in the conversation to check the connection. ChatGPT in a web browser does not read this local configuration. See the official MCP setup guide.
Cursor
The config file is located at:
%USERPROFILE%\.cursor\mcp.json
GitHub Copilot
GitHub Copilot appears in the dialog when VS Code, Visual Studio, or the Copilot CLI is installed on your machine. The config files are located at:
%APPDATA%\Code\User\mcp.json
%USERPROFILE%\.mcp.json
%USERPROFILE%\.copilot\mcp-config.json
Grok Build
Toggle Enable MCP and the connector writes its entry into xAI's Grok Build CLI configuration automatically. The config file is located at:
%USERPROFILE%\.grok\config.toml
Grok Build also reads Claude Code's and Cursor's MCP config, so if you have already configured either of those the connector shows up in Grok Build with no extra step.
Claude Code & other MCP clients
MCP Connector for Civil 3D exposes a standard MCP stdio server, so it also works with Claude Code, VS Code, and any other MCP-compatible client. The server is a single executable installed with the plug-in bundle:
C:\Program Files\Autodesk\ApplicationPlugins\AUTOM8LABS.MCPConnectorCivil3D.bundle\Contents\Bridge\MCPConnectorCivil3D.Bridge.exe
Register it in Claude Code from a terminal:
claude mcp add AUTOM8LABS_Civil3D -- "C:\Program Files\Autodesk\ApplicationPlugins\AUTOM8LABS.MCPConnectorCivil3D.bundle\Contents\Bridge\MCPConnectorCivil3D.Bridge.exe"
Manual configuration (any MCP client)
Add this to your client's MCP server configuration:
{
"mcpServers": {
"AUTOM8LABS_Civil3D": {
"command": "C:\\Program Files\\Autodesk\\ApplicationPlugins\\AUTOM8LABS.MCPConnectorCivil3D.bundle\\Contents\\Bridge\\MCPConnectorCivil3D.Bridge.exe"
}
}
}
VS Code
VS Code uses a slightly different shape. Add the server to your MCP configuration (for example .vscode/mcp.json in a workspace):
{
"servers": {
"AUTOM8LABS_Civil3D": {
"type": "stdio",
"command": "C:\\Program Files\\Autodesk\\ApplicationPlugins\\AUTOM8LABS.MCPConnectorCivil3D.bundle\\Contents\\Bridge\\MCPConnectorCivil3D.Bridge.exe"
}
}
}
After changing MCP configuration, restart the AI client completely for the changes to take effect.
Optional: raw command execution
Two tools can drive the host directly: execute_command runs a raw command string as if
typed at the command line, and execute_lisp evaluates an AutoLISP expression. Because they
can drive anything, both are disabled by
default: they are neither listed nor callable until you opt in on that machine by
setting MCP_CONNECTOR_ENABLE_COMMAND_EXEC=1 in the MCP client configuration.
Even when enabled, code-loading and shell verbs (NETLOAD, APPLOAD, SCRIPT, SHELL, AutoLISP
load) are blocked. Both tools are Pro, so a licence is needed as well as the opt-in.
After saving the configuration, fully quit and reopen your AI client - quit it from the system tray rather than just closing the window, or it keeps the old environment and the two tools still will not appear. To turn them off again, remove the setting and restart the client the same way.
{
"mcpServers": {
"AUTOM8LABS_Civil3D": {
"command": "C:\\Program Files\\Autodesk\\ApplicationPlugins\\AUTOM8LABS.MCPConnectorCivil3D.bundle\\Contents\\Bridge\\MCPConnectorCivil3D.Bridge.exe",
"env": {
"MCP_CONNECTOR_ENABLE_COMMAND_EXEC": "1"
}
}
}
}
Optional: read-only session
A read-only session withholds every tool that can change a drawing, leaving the 43 free tools: query, inspect, measure and navigate. Civil-specific tools are also withheld in this mode, including Civil queries, even with a Pro licence. A withheld tool is not listed to the AI client at all, and is refused by name if it is called anyway, so the AI cannot reach a write.
It is worth using whenever the drawings belong to a client rather than to you. DWG is usually the format that arrives from someone else. An in-session change can still be undone in Civil 3D, but the folder tools save each drawing as they go, so those edits are on disk already - and an unwanted change does not always announce itself on screen.
Turn it on with the Read-Only Session checkbox in the connection
dialog, or by running MCPCONNECTORC3D_READONLY at the Civil 3D command line.
Either way, reconnect your AI client afterwards so it refreshes its
tool list.
Locking it on for a team. An administrator can enforce read-only for a computer or selected users. See Administrator Tool Permissions for the settings and deployment examples.
Local AI Setup
Connect a local AI model to Civil 3D through an MCP-compatible app. These steps are for Windows, on the same computer as Civil 3D.
1. Prepare Civil 3D
- Install MCP Connector for Civil 3D and open a sample drawing.
- On the Add-ins tab, click MCP Connector and turn on Enable MCP. Keep Civil 3D open.
- In your AI app, download or select a local model that supports tool calling.
2. Configure your app
Use this entry for Civil 3D 2022 to 2027.
{
"mcpServers": {
"AUTOM8LABS_Civil3D": {
"command": "C:\\Program Files\\Autodesk\\ApplicationPlugins\\AUTOM8LABS.MCPConnectorCivil3D.bundle\\Contents\\Bridge\\MCPConnectorCivil3D.Bridge.exe"
}
}
}
For separate fields, use AUTOM8LABS_Civil3D as the name, stdio as the transport, and the command path with single backslashes and no quotes. Leave Arguments blank for this example.
Edit an existing connector entry rather than adding a duplicate. Keep its arguments, environment and tool settings. In an existing JSON file, add only AUTOM8LABS_Civil3D inside mcpServers, preserving other entries.
Choose your app below. Connection tested means registration, tool discovery and reconnection were checked using the Revit connector. These Civil 3D steps use the same app settings; they have not been tested end to end with every app and model.
- Open Settings > Agent Skills once to create the configuration file.
- Click the app version number > Open storage. Open
plugins/anythingllm_mcp_servers.jsonand add the entry. - Return to Agent Skills and click Refresh. Check the connector is running.
- Start your test prompt with
@agent.
- Open MCP connections and look for
AUTOM8LABS_Civil3D, including paused entries. - Use that connection if present. Otherwise, add one using the name and command above.
- Enable the connection and choose your local model.
- Open Settings > MCP > MCP Servers > Add > Import from JSON.
- Paste the JSON, enable the server and check its tools appear.
- Open Work > your Agent's menu > Edit > MCP and enable the connector for that Agent.
- Select your local model and start a conversation with that Agent.
- Open Settings > MCP Servers > Add MCP Server.
- Select STDIO and enter the name and command above.
- Save, then enable the server. A green indicator confirms it is active.
- In the right sidebar, open Program > Install > Edit mcp.json.
- Add the connector inside
mcpServersand save. - Check the connector is available and enabled for your chat.
- Sign in to your local installation. Open MCP settings > Import JSON.
- Paste the JSON. The import applies immediately.
- Enable the connector and MCP tool use for your chat.
These steps apply to 2026.9.11. Other versions may differ. See Unsloth's current guide.
3. Test the connection
With your sample drawing open, ask:
Use the Civil 3D connector to tell me the active drawing name and Civil 3D version. Do not change anything.
In AnythingLLM, prefix this with @agent. Confirm a connector tool runs and the answer matches your open drawing.
Tool loading and model limits
If available, enable tool selection or on-demand loading and start with a few read-only tools. Large tool lists can exceed a local model's context. A larger context setting alone does not guarantee reliable tool use.
Claude Desktop Settings
MCP Connector for Civil 3D exposes 296 tools, plus two optional command-execution tools that stay disabled until you opt in. In Claude Desktop, enable Load tools when needed so tools are loaded on demand rather than all at once.
Use Chat, not Cowork
Claude Desktop has a mode selector at the bottom of the message box: Chat and Cowork. MCP connectors run in Chat conversations. In Cowork, your Civil 3D requests will not reach the connector and Claude behaves as if Civil 3D is not connected - even though the connector is configured correctly. Before you start, check the selector is set to Chat.
Note this is the opposite way round to ChatGPT Desktop, where the Civil 3D tools are available in Work rather than regular Chat.
Operator Skill
An operator skill is a plain text playbook Claude reads before touching your drawing. It teaches Claude to use the connector efficiently: read in bulk instead of one entity at a time, verify answers with counts, batch edits in one call, and say so instead of guessing when something cannot be done. The result is fewer calls, fewer dead chats, and far less of your usage allowance burned on a single question.
The free AutoCAD operator skill covers the drawing tools this connector inherits, which is most of the tool set, so it is worth installing. A skill for the Civil design tools is in progress.
Install in Claude Desktop:
- Download the skill: autocad-connector.zip
- In Claude Desktop, go to Settings > Skills > Add > Upload a skill and select the zip.
- That is it - Claude picks the skill up automatically in new chats. If you ever find it has not, mention it in your prompt, for example "Follow the autocad-connector skill".
Using Claude Code or Cursor instead? Install steps for both are in the mcp-connector-skills repository, which also hosts free skills for the rest of the MCP Connector family.
Quickstart
MCPCONNECTORC3D_STATUS confirms it is running.ping tool. You should get back a confirmation that it is connected.Power BI Dashboard
A free browser dashboard and Power BI report for tool-use records. MCP Connector Pro is required to record audit logs.
Tool Use Audit dashboard
Review AI-assisted work in Civil 3D using a browser dashboard or Power BI.
Requires: MCP Connector for Civil 3D Pro 1.2.0+ and administrator rights to enable logging.
Download: Tool Use Audit v1.0.0 (.zip)
1. Enable logging
Logging is off by default. On each computer, open Registry Editor as administrator. Create this key if needed, then set its values:
HKEY_LOCAL_MACHINE\SOFTWARE\AUTOM8LABS\MCPConnectorCivil3D
| Value name | Type and setting |
|---|---|
AuditLog | DWORD (32-bit): 1 |
AuditLogFolder | String (REG_SZ): your log folder, e.g. C:\AuditLogs |
Create the log folder and give Civil 3D users write access. For multiple computers, use a network share. Restart Civil 3D.
2. Open a dashboard
Extract the ZIP to C:\AuditDashboard or another short path. Keep its files and folders together.
- Open
audit-dashboard.htmlin Chrome or Edge. - Select Open audit folder, choose your
AuditLogFolderand allow read access.
The dashboard reads files locally and refreshes automatically.
- Open
AUTOM8LABS Connector Audit.pbipin Power BI Desktop for Windows (September 2026 or later). - Under Transform data > Edit parameters, set AuditLogFolder to your log folder.
- Select OK > Apply changes > Refresh.
Select Refresh whenever you want the latest records.
3. Check logging works
Ask your AI assistant to run get_drawing_info in your open Civil 3D drawing. Wait around 30 seconds, then check for the call. Select Refresh in Power BI.
Time, user, computer, host and release, drawing, AI app, tool, read/write type and outcome, plus the first 300 characters of its arguments. Chat messages, full tool results and bridge-only connection calls are excluded.
Write means the tool can change a drawing; it does not prove a change occurred. Optional: set AuditReason (DWORD) to 1 in the same registry key, then restart Civil 3D, to request a short explanation from the AI.
CSV files are saved under %LOCALAPPDATA%\AUTOM8LABS\MCPConnectorCivil3D\Audit, then copied into month folders under AuditLogFolder every 30 seconds and when Civil 3D closes. Failed copies retry automatically for files updated within the last seven days.
Local copies are kept for 90 days. Files in your chosen folder are not automatically deleted. See the included README for more detail.
Want your company branding? Contact us.
Tool Reference
MCP Connector for Civil 3D includes the whole tool set of MCP Connector for AutoCAD: drawings, layers, blocks, annotation, layouts and plotting, external references and the Management Pack, with a read-only free tier that works without a licence. Those tools work the same way in Civil 3D and are not repeated here. See the AutoCAD Tool Reference for the list.
The tools below are the Civil design tools, grouped by category. Every tool name shown is the exact identifier exposed to your AI client. The Edition column shows whether a tool is available in the free edition or needs a Pro licence. Under each description is an example prompt showing how to ask for it in natural language - click any prompt to copy it, paste it into your AI client, and adjust the names and numbers to suit your drawing.
Civil design objects
These tools exist only because the host is Civil 3D. Every one of them needs a Pro
licence. Bulk edits default to a preview (dry_run: true): pipe, structure and
COGO point properties, pipe run regrading, renaming, layer and style tables, property
set values, survey standards and Civil style purging. Review the proposed changes
before asking the AI to apply them. Tools that create a single object, such as a
surface, an alignment or a pipe run, change the drawing immediately.
Civil: Alignments
| Tool | Example prompt | Edition |
|---|---|---|
| Create an alignment from an existing polyline, line or arc in the drawing, named by its handle | ||
create_alignment_from_entity | Turn the polyline I have selected into an alignment called DUCT-02 | Pro |
| Create an alignment offset a fixed distance from an existing one | ||
create_offset_alignment | Create an alignment 3 metres left of DUCT-01 for the second duct run | Pro |
| Return the horizontal geometry of one alignment as an ordered list of sub-entities (lines, arcs, spirals) with start and end station, length, start and end point, and for arcs the radius, delta angle and direction | ||
get_alignment_geometry | Break down the geometry of alignment DUCT-01, entity by entity | Pro |
| Convert between plan coordinates and station/offset along an alignment | ||
get_alignment_station_offset | What station and offset is easting 412500, northing 287300 on DUCT-01? | Pro |
| List the alignments in the drawing with their type (centreline, offset, curb return, rail), site, length, start and end station, style, and whether design criteria or design checks are in force | ||
list_alignments | List the alignments in this drawing with their start and end stations | Pro |
Civil: COGO points
| Tool | Example prompt | Edition |
|---|---|---|
| Calculate the station and offset of COGO points against an alignment and record them on each point, so a set of surveyed assets - poles, luminaires, manholes - can be scheduled by chainage | ||
add_station_offset_to_points | Add the station and offset along DUCT-01 to every point in the Manholes group | Pro |
| Create COGO points from coordinates supplied directly, each with an optional description | ||
create_cogo_points | Add a point at easting 412500, northing 287300, elevation 43.2, described as LP for a lighting column | Pro |
| Create or update a COGO point group defined by a membership query: include or exclude by raw description (wildcards allowed), by point number range, by point name, or include every point | ||
create_point_group | Create a point group called Lighting that collects every point with a description starting LP | Pro |
| Export COGO points to a delimited coordinate file using one of the drawing's point file formats | ||
export_cogo_points | Export the Manholes point group to a CSV for the setting-out team | Pro |
| Read COGO points with their number, name, northing, easting, elevation, and raw and full description | ||
get_cogo_points | List the points in the Manholes group with their coordinates and descriptions | Pro |
| Import COGO points from a delimited coordinate file (CSV or TXT) using one of the drawing's point file formats | ||
import_cogo_points | Import the survey CSV at C:\Project\Survey\topo.csv as COGO points | Pro |
| List the COGO point file formats available in this drawing, with each format's delimiter, file extension and column layout | ||
list_point_file_formats | What point file formats can I import from? | Pro |
| List the COGO point groups in the drawing with their point count, description, lock state, whether they are out of date, and which point or label style overrides each group applies | ||
list_point_groups | List the point groups in this drawing and how many points each holds | Pro |
| Bulk-edit COGO points: apply a point style, a label style, a raw description, or an elevation offset | ||
set_cogo_point_properties | Move every point in the Lighting group onto our standard point style, and preview it first | Pro |
Civil: Corridors, parcels and feature lines
| Tool | Example prompt | Edition |
|---|---|---|
| Create a feature line from 3D points supplied directly, or from an existing line, arc, polyline or 3D polyline named by its handle | ||
create_feature_line | Turn the polyline I have selected into a feature line called PAD-EDGE | Pro |
| Edit an existing feature line: raise or lower the whole line, set individual point elevations, drape it onto a surface, or change its name, style or layer | ||
edit_feature_line | Drape the PAD-EDGE feature line onto Existing Ground, and preview the levels first | Pro |
| List the assemblies in the drawing with their type and the subassemblies inside each group, including which side each subassembly sits on | ||
list_assemblies | What assemblies are in this drawing and what subassemblies do they use? | Pro |
| List the corridors in the drawing with their baselines (each with its alignment, profile and regions), the assemblies each region applies, the corridor surfaces built from them, and whether the corridor is out of date and needs a rebuild | ||
list_corridors | List the corridors in this drawing with their baselines and regions | Pro |
| List the feature lines in the drawing, both inside sites and siteless, with their style, point counts, elevation range, and minimum and maximum grade | ||
list_feature_lines | List the feature lines in this drawing with their lengths and elevation ranges | Pro |
| List the parcels in the drawing grouped by site, with parcel number, name, area, style, address and tax id | ||
list_parcels | List the parcels in this site with their areas | Pro |
Civil: Crossings and clearance
| Tool | Example prompt | Edition |
|---|---|---|
| Find where pipes cross in plan and report the vertical clearance at each crossing | ||
check_pipe_crossings | Check DUCTBANK-B against the existing services for crossings, 300mm hard clearance and 600mm soft, measured from invert | Pro |
Civil: Export and utility
| Tool | Example prompt | Edition |
|---|---|---|
| Export the Civil model to a spreadsheet, one sheet per requested section: pipes (with length, size, slope, inverts, cover and the structures at each end), structures (rim, sump, station and offset, connected pipes), points (number, coordinates, description), alignments (length, station range), parcels (number, area) and surfaces (area statistics and volumes) | ||
export_civil_quantities | Export the pipes, structures and points in this drawing to a spreadsheet, one sheet each | Pro |
| Find autosave and recovery files left behind by a crash, including ones the Drawing Recovery Manager does not list | ||
find_recoverable_drawings | Are there any recoverable drawings or autosaves for this project folder? | Pro |
| Restore an autosave file found by find_recoverable_drawings to a real .dwg at a location you choose | ||
recover_drawing | Recover the damaged drawing at C:\Project\DWG\Site-Plan.dwg | Pro |
| Zoom the current view to a named Civil object: an alignment, profile view, surface, pipe network, structure, pipe, parcel or sample line group | ||
zoom_to_civil_object | Zoom to the DUCTBANK-A network so I can see it | Pro |
Civil: Labels
| Tool | Example prompt | Edition |
|---|---|---|
| Add major and minor station labels along one alignment or every alignment matching a filter | ||
label_alignment_stations | Add major and minor station labels to DUCT-01 | Pro |
| Label Civil objects in bulk by rule, using the drawing's own label styles | ||
label_civil_objects | Label every 150mm duct in DUCTBANK-A with our small duct label style, and show me what would be labelled first | Pro |
| Label the pipes and structures of a gravity network in plan | ||
label_pipe_network | Label every pipe and structure in DUCTBANK-A with our standard label styles | Pro |
Civil: Overview
| Tool | Example prompt | Edition |
|---|---|---|
| Remove a saved setup by name and tool, from your own setup folder or a shared one. Nothing in the drawing changes | ||
delete_civil_setup | Delete the saved setup called Old UK rules | Pro |
| Summarise the Civil design data in the drawing: counts of surfaces, alignments, profiles, profile views, corridors, assemblies, pipe networks, point groups, COGO points, sites, parcels and feature lines | ||
get_civil_document_info | What Civil objects are in this drawing? Give me the counts before we start | Pro |
| List the saved setups that grading, rule checks, labelling and earthwork keep under a name, for running again in another drawing or sharing with a team | ||
list_civil_setups | Which saved setups do we have for the pipe rule check? | Pro |
| List the sites in the drawing with the count of parcels, feature lines and alignments each one owns | ||
list_sites | List the sites in this drawing and what each one owns | Pro |
Civil: Pipe and duct networks
| Tool | Example prompt | Edition |
|---|---|---|
| Lay a run of structures and the pipes connecting them along a path | ||
add_pipe_run | Run 150mm duct along DUCT-02 from a start invert of 42.30 falling at 1 in 200, with a handhole every 50 metres | Pro |
| Check pipes and structures against design limits and list what fails: slope outside a minimum and maximum, cover to a ground surface outside a range, a pipe longer than a maximum, a drop across a structure outside a range, an outlet above an inlet, a pipe that falls against its set flow direction, and a pipe crown above the structure rim | ||
check_pipe_rules | Check DUCTBANK-A for any duct flatter than 1 in 200 or with less than 600mm of cover | Pro |
| Create an empty gravity pipe network, optionally tied to a reference alignment and reference surface | ||
create_pipe_network | Create a new network called DUCTBANK-B using our LV duct parts list | Pro |
| Draw a pipe run in profile in one call | ||
create_pipe_run_profile | Draw the run from MH12 to MH18 in profile with the Existing Ground line, and place the view at easting 413000, northing 287000 | Pro |
| Read a pipe's invert, crown and centreline level at any position along it, not just at its ends | ||
get_pipe_invert_at | What is the invert of the duct between MH12 and MH13 at station 215? | Pro |
| Read the pipes in a gravity network with their start and end invert elevations, slope, length, inner and outer diameter, cross-sectional shape, flow direction, cover at each end, the start and end station along the network's reference alignment, and the structures at each end | ||
get_pipes | List every pipe in DUCTBANK-A with its length, size, inverts and cover | Pro |
| Read the structures in a gravity network with their rim and sump elevation, insertion point, northing and easting, station and offset along the network's reference alignment, bounding shape, connected pipe count and names, and whether the rim tracks the reference surface automatically | ||
get_structures | List the manholes in DUCTBANK-A with their rim and sump levels | Pro |
| Apply an edited pipe schedule back to the model | ||
import_pipe_network_data | Apply my edited schedule at C:\Project\Schedules\DUCTBANK-A.xlsx back to the network, and list every change first | Pro |
| List the rule sets a network's pipes and structures carry, which parts override them, and the limits inside each rule | ||
list_part_rules | Which rule set does STORM-01 use, and what cover and slope limits does it set? | Pro |
| List the pipe and structure part families in a parts list, each with the number of sizes it offers | ||
list_parts_list | What parts lists are in this drawing, and what sizes does the LV duct family offer? | Pro |
| List the gravity pipe networks in the drawing with their parts list, pipe and structure counts, and the reference alignment and reference surface each network is tied to | ||
list_pipe_networks | List the pipe networks in this drawing with pipe and structure counts | Pro |
| Regrade the connected run between two parts as one piece | ||
regrade_pipe_run | Regrade the run from MH12 to MH18 at 1 in 200 holding the downstream end, and show me every level before you change it | Pro |
| Rename the pipes and structures of a network in bulk | ||
rename_network_parts | Renumber the manholes in DUCTBANK-A as MH-001, MH-002 and so on in station order, and preview the names first | Pro |
| Edit pipes in a network: set start and end elevations against the invert, crown or centreline datum, regrade to a slope holding either end, shift both ends, swap the part size, or set the description | ||
set_pipe_properties | Drop the invert of the run between MH12 and MH13 by 150mm, and show me the change before you make it | Pro |
| Edit structures in a network: set rim and sump elevation, drop the rim to a reference surface, set the sump a fixed depth below the lowest connected pipe, swap the part size, or set the description | ||
set_structure_properties | Set the rim level of every manhole in DUCTBANK-A to the Existing Ground surface | Pro |
| Follow the connections of a gravity network | ||
trace_pipe_run | Trace the run from MH12 to MH18 in DUCTBANK-A and give me each pipe's slope and the drop across each manhole | Pro |
Civil: Pressure networks
| Tool | Example prompt | Edition |
|---|---|---|
| Lay a run of straight pressure pipes end to end along a path of points, from one size in the network's parts list, named by description or by nominal diameter | ||
add_pressure_pipe_run | Lay a 300 mm ductile iron main in WATER-01 through 1200,450 at 42.30, 1200,780 at 42.10 and 1450,780 at 41.95 | Pro |
| Create an empty pressure pipe network from a pressure parts list, optionally tied to a reference alignment and a reference surface | ||
create_pressure_network | Create a pressure network called WATER-01 from the Water parts list, referenced to the MAIN-ST alignment and the EG surface | Pro |
| Read a pressure network's pipes with their size, diameters, levels, length, slope, cover and end fittings, and its fittings and appurtenances with position and station | ||
get_pressure_parts | List every pipe in WATER-01 with its size, inverts and cover, and tell me where the valves are | Pro |
| List the pressure pipe networks in the drawing with their parts list, part counts, reference alignment and surface, and elevation range | ||
list_pressure_networks | What pressure networks are in this drawing, and which parts list does each use? | Pro |
| List the pressure parts lists in the drawing and, for one list, the pipe, fitting or appurtenance sizes it offers with description, family, nominal diameter and material | ||
list_pressure_parts_list | Which pipe sizes does the Water parts list offer in ductile iron? | Pro |
Civil: Profiles and profile views
| Tool | Example prompt | Edition |
|---|---|---|
| Create a design profile on an alignment from explicit PVIs, each a station and elevation, with optional vertical curve lengths | ||
create_profile_by_layout | Create a duct invert profile on DUCT-01 held 1.2 metres below the existing ground profile the whole way | Pro |
| Create a profile along an alignment by sampling a surface, which gives the existing ground line for that route | ||
create_profile_from_surface | Create an existing ground profile on DUCT-01 from the Existing Ground surface | Pro |
| Create a profile view for an alignment at a given insertion point | ||
create_profile_view | Draw a profile view for DUCT-01 showing both the ground and the duct invert | Pro |
| Sample a profile at one or more stations, returning elevation and grade at each | ||
get_profile_elevation | What is the design profile elevation at station 340 on DUCT-01? | Pro |
| Return the vertical geometry of one profile: every PVI with station, elevation, grade in and grade out, plus the ordered tangent and vertical-curve entities with their length, start and end elevation and minimum K values for stopping, passing and headlight sight distance | ||
get_profile_geometry | Show me the PVIs and grades on the DUCT-01 design profile | Pro |
| List the profile views in the drawing with their parent alignment, style, station range, elevation range and whether the view is split | ||
list_profile_views | List the profile views in this drawing and what each one shows | Pro |
| List the vertical profiles in the drawing, grouped by the alignment that owns them | ||
list_profiles | List the profiles on DUCT-01 and tell me which surface each one came from | Pro |
Civil: Property sets
| Tool | Example prompt | Edition |
|---|---|---|
| Create a property set definition, or add properties to an existing one | ||
create_property_set_definition | Create a property set called Asset Data for pipes and structures, with Asset ID, Inspection Status and Cost Code | Pro |
| Read the property set data (Extended Data) attached to objects: each property set, its properties and their values, and whether a value is calculated automatically | ||
get_property_set_data | Export the property set values on every pipe and manhole in DUCTBANK-A to a spreadsheet | Pro |
| Write property set values (Extended Data) onto objects | ||
set_property_set_data | Fill in the Asset Data values from my edited spreadsheet, and list each value before it changes | Pro |
Civil: Sample lines and sections
| Tool | Example prompt | Edition |
|---|---|---|
| Create a sample line group on an alignment and cut sample lines along it, either at a regular station interval or at explicit stations | ||
create_sample_line_group | Cut sample lines along DUCT-01 every 20 metres, sampling Existing Ground and DUCTBANK-A | Pro |
| Create a section view for each sample line in a group, laid out on a grid from an insertion point | ||
create_section_views | Draw the section views for the DUCT-01 sample lines | Pro |
| Grade a design surface from a typical section set out along a route | ||
grade_from_sections | Preview a 3 metre wide track with 1 in 2 side slopes along DUCT-01, tied into Existing Ground | Pro |
| List the sample line groups in the drawing with their parent alignment and, for each group, the sample lines with station, number and style | ||
list_sample_line_groups | List the sample line groups in this drawing and what they sample | Pro |
Civil: Styles, layers and standards
| Tool | Example prompt | Edition |
|---|---|---|
| Read the current drawing's layer table as rows: name, on, frozen, locked, plot, colour, linetype, lineweight, transparency and description, with a blank 'New name' column for renaming | ||
export_layer_table | Export this drawing's layer table to a spreadsheet so I can edit it | Pro |
| Find where layers, linetypes, text styles, dimension styles or hatch patterns are used across a drawing or template: which Civil style components point at each one (as the path Kind/Style/Component), which object layer settings name it, which other table records depend on it, and how many drawn objects use it | ||
find_template_references | Is the layer C-OLD-PIPE safe to delete? Show me everything that still uses it | Pro |
| Read what is inside Civil styles as a table, one row per component and property: the display components of object styles in plan, model, profile and section (visibility, layer, colour, linetype, linetype scale, lineweight, plot style), the text, line, block, tick and arrow components of label styles including child styles, and the settings of table styles | ||
get_civil_style_properties | Show me which layer every pipe style puts its plan components on | Pro |
| Read a survey figure prefix database: each prefix with whether its figures act as breaklines and as lot lines, and the layer, figure style and site they are given | ||
get_figure_prefixes | List the prefixes in our survey figure prefix database with their layers and styles | Pro |
| Read the object layer settings: which layer each kind of Civil object is created on, plus any prefix or suffix modifier and whether the setting is locked | ||
get_object_layer_settings | What layers do new Civil objects get created on in this drawing? | Pro |
| Apply layer edits from a spreadsheet written by export_layer_table, or from rows supplied directly | ||
import_layer_table | Apply my edited layer spreadsheet to this drawing, and list each change before you make it | Pro |
| List the Civil object styles in the drawing by kind (surface, alignment, profile, profile view, corridor, pipe, structure, parcel, point, feature line, section, section view, sample line, marker, link, shape and more), with each style's name, description and whether anything in the drawing uses it | ||
list_civil_styles | List the Civil styles in this drawing by type so I can see what we inherited | Pro |
| List the point description key sets and their keys: the field code each matches, and the point style, label style, layer and format it applies | ||
list_description_keys | What description key sets are in this drawing and what do they match? | Pro |
| List the drawing's layer filters as the Layer Properties Manager shows them, with their expressions, their layers and their nesting | ||
list_layer_filters | Show me the layer filters in this drawing and how many layers each one holds | Pro |
| Delete Civil object styles that nothing in the drawing uses, across one style collection or all of them | ||
purge_civil_styles | Show me which Civil styles are unused, then purge them | Pro |
| Swap one layer, linetype, text style, dimension style or hatch pattern for another everywhere it is used: in Civil style components, in the object layer settings, in the table records that depend on it and on the drawn objects themselves | ||
reassign_template_references | Replace the linetype DASHED2 with HIDDEN everywhere it is used in this template, and count the changes first | Pro |
| Rename layers in bulk: replace text within the names, add a prefix, add a suffix, or any combination | ||
rename_layers | Add the prefix C- to every layer whose name starts with ROAD, and preview the new names first | Pro |
| Edit Civil styles in bulk | ||
set_civil_style_properties | Put the plan display components of every pipe style on layer C-DUCT-PIPE, and preview every change first | Pro |
| Create or update point description keys: the field code each matches and the point style, label style, layer and format it applies | ||
set_description_keys | Copy the description key sets from our survey template into this drawing, and preview the changes first | Pro |
| Create or update a survey figure prefix database | ||
set_figure_prefixes | Add a figure prefix KERB to our survey figure prefix database, drawn as a breakline on layer V-KERB, and preview it first | Pro |
| Set which layer each kind of Civil object is created on | ||
set_object_layer_settings | Move Civil object creation onto our company layers, and preview every change first | Pro |
Civil: Surfaces
| Tool | Example prompt | Edition |
|---|---|---|
| Add data to an existing surface's definition: a COGO point group, an outer or hide boundary polygon, breaklines from drawing entities, or drawing objects (3D polylines, points, blocks) | ||
add_surface_definition | Add the point group Survey 2026 to the Existing Ground surface as a definition | Pro |
| Calculate cut and fill between an existing and a proposed surface, for the whole surface or for named regions | ||
calculate_earthwork | Work out cut and fill between Existing Ground and Proposed, stripping 150mm of topsoil first | Pro |
| Create a new TIN surface a fixed vertical distance above or below an existing one, by copying its triangulation and shifting every vertex | ||
create_offset_surface | Create a surface 0.5 below Existing Ground so I can check formation level | Pro |
| Create a TIN surface and optionally build it in the same call from a COGO point group, a coordinate file, or a DEM file | ||
create_surface | Create an empty TIN surface called Proposed using our standard surface style | Pro |
| Create a TIN volume surface between a base (existing) and a comparison (proposed) surface, and return its cut, fill and net volumes | ||
create_volume_surface | Create a volume surface comparing Proposed against Existing Ground | Pro |
| Convert TIN surfaces into 3D solids for coordination or clash detection, in one pass over several surfaces | ||
extract_surface_solids | Extract the volume between Existing Ground and Proposed as a solid I can hand to the contractor | Pro |
| Sample a surface at one or more plan positions, returning elevation, slope and aspect direction at each | ||
get_surface_elevation | What is the elevation of Existing Ground at easting 412500, northing 287300? | Pro |
| Full detail for one surface: elevation and coordinate extents, point count, TIN triangle statistics, and the ordered list of definition operations that build it (boundaries, breaklines, point files, DEM, drawing objects) | ||
get_surface_info | Show me how the Existing Ground surface is built, operation by operation | Pro |
| Report earthwork volumes | ||
get_surface_volume | Give me the cut and fill between Existing Ground and Proposed | Pro |
| List the surfaces in the drawing with their kind (TIN, grid, TIN volume, grid volume), style, point count, elevation range and whether they are out of date | ||
list_surfaces | List every surface with its point count and elevation range, and tell me which ones are out of date | Pro |
| Rebuild one surface by name, or every surface in the drawing that is out of date | ||
rebuild_surface | Rebuild Existing Ground, it is showing as out of date | Pro |
| Sample a surface along a route and return elevation, slope and running chainage at each station | ||
sample_surface_along_line | Walk Existing Ground along my selected polyline at 5 metre intervals and give me the elevations | Pro |
Troubleshooting
The AI says it is not connected to Civil 3D
- Civil 3D must be running with a drawing open. The connector talks to a live session; it cannot open Civil 3D for you.
- In Civil 3D, run
MCPCONNECTORC3D_STATUSto check the plug-in state. If it reports not running, runMCPCONNECTORC3D_START. - Ask your AI to run the
pingtool. It reports whether the link is up and, if not, why.
The plug-in did not load
- The plug-in auto-loads when Civil 3D starts. If the AUTOM8LABS ribbon is missing, restart Civil 3D, then run
MCPCONNECTORC3D_STARTat the command line. - Confirm the bundle exists at
C:\Program Files\Autodesk\ApplicationPlugins\AUTOM8LABS.MCPConnectorCivil3D.bundle. If it is missing, re-run the installer. - Check that your Civil 3D release is 2022, 2023, 2024, 2025, 2026 or 2027. Earlier releases are not supported.
Pro tools are missing after activating
- The MCP server reads the edition once, when the AI client starts it. Restart the AI client after activating and the full tool list appears.
- Confirm the licence state in Civil 3D via Manage Licence on the AUTOM8LABS ribbon.
- If only the 43 free tools appear despite an active Pro licence, check whether Read-Only Session is enabled. This mode also hides the Civil inspection tools.
The AI client does not list the server
- Restart the client completely after installing; a window reload is not always enough.
- Check whether your AI application is detected in the connector dialog and enable MCP. If it is not supported by automatic setup, use the manual configuration.
execute_command or execute_lisp is not available
- Both tools are off by default and do not register at all until you opt in. Set
MCP_CONNECTOR_ENABLE_COMMAND_EXEC=1in the MCP client configuration, then fully quit and reopen the client from the system tray. See Raw command execution. - They are Pro tools, so they also need an active licence. If the opt-in is set and they still do not appear, check the licence first.
FAQ
MCPCONNECTORC3D_LICENCE command, then restart your AI client.
Changelog
- Civil 3D 2022 and 2023 join 2024 to 2027: one installer, six releases
- 296 tools, 43 of them free, 45 more than the first release: 95 Civil tools alongside the 203 tools of the current AutoCAD connector
- Section grading. Grade from a polyline, a feature line, an alignment or a corridor feature line: section points by slope, distance, elevation, daylight or to a named feature line, breaklines, outlines placed anywhere along the route, parallel joins and nested sections, several placements in one call, and a re-run that replaces the earlier result
- Earthwork. Cut and fill for a whole surface or by region, groups of regions each with their own surface pair, stripping and subgrade depths, a table in the drawing and a spreadsheet
- Pipe networks. Regrade a run holding either end, trace a run, draw it in profile in one call, check pipes and structures against your limits or against each part's own Civil 3D rule set, rename parts in bulk, import network data from a spreadsheet, and edit the parts selected on screen
- Pressure networks. List networks and parts lists, read pipes, fittings and appurtenances, create a network and lay a run of pipes from a parts list size, and label them
- Labels. One labelling tool across alignments, profiles, sections, surfaces, pipes, pressure parts, parcels, catchments, intersections and notes, with conditions, a style per call, a dry run, labels kept where you dragged them, and the same run across other open drawings, closed files or a whole folder
- Standards. Read, edit and rename Civil styles in bulk, find and reassign template references, export and import the layer table with its layer filters, rename layers with find and replace, carry description keys and figure prefixes between drawings, and read and write property sets
- Saved setups. Keep a grading, rule check, labelling or earthwork setup under a name and run it again in any drawing, or share it from a team folder
- Feature lines created and edited from the chat
- Working across drawings. List, switch between and close open drawings, write a selection to a new DWG, and import layouts and PDFs
- Administrator controls. Tools switched off by name, an approved list, or read-only sessions, by computer or by person through Group Policy, with an optional audit log. All of it is off unless an administrator sets it
First release
- Civil design objects. Surfaces, alignments, profiles and profile views, corridors and assemblies, pipe networks, COGO points, sample lines and sections, parcels, feature lines and sites
- Underground services. Route a run at a fixed cover depth below an existing profile, grade a whole run from a start invert and a slope, and read the invert at any station
- Crossing checks with separate hard and soft clearances, measured from invert, crown or centreline
- Survey and reporting. COGO point import and export through delimited text, point groups and description keys, and a spreadsheet export covering pipes, structures, points, alignments, parcels and surfaces
- Standards. Read and apply object layer settings, list and purge Civil styles, label alignments and pipe networks
- The full AutoCAD drawing tool set is included, so inside Civil 3D this is the only connector you need
- Every bulk edit previews before it writes and reports what it would change
- Civil 3D 2024, 2025, 2026 and 2027