Civil 3D MCP connects an AI assistant to Autodesk Civil 3D with an architecture that is more powerful, and riskier, than classic CAD MCPs. The barbosaihan/civil3d-mcp repository is not limited to a fixed tool list: it lets the assistant write C# code, compile it through Roslyn, and execute it inside Civil 3D with API access. The README clearly describes three meta-tools: civil3d_execute for write access, civil3d_query for read-only access, and civil3d_skills for browsing code templates.
For a pure architecture firm, Civil 3D MCP will rarely be a priority. For a site works, infrastructure, surveying, or civil engineering office, the topic is much more serious: surfaces, alignments, COGO points, geometry, drawing information, and complex workflows are exactly the objects used daily. The right framing is not "an assistant that draws", but "an assistant able to produce and execute Civil 3D C# from templates".
Contents
- What Civil 3D MCP does
- Code execution architecture
- Professional use cases
- Comparison with AutoCAD MCP and Revit MCP
- Security and limits
- Educasium's position
- Sources and next reading
What Civil 3D MCP does
Key point: Civil 3D MCP gives access to the Civil 3D API through generated code, not only through prewritten commands. That difference changes both the level of control and the level of risk.
Three meta-tools
The README documents civil3d_execute as a C# execution tool with write access and a committed transaction. It documents civil3d_query as read-only C# execution, with no commit. The third tool, civil3d_skills, browses, searches, and reads code templates in the skills library.
This organization is more flexible than a list of functions such as draw_line or create_room. The assistant can read a template, adapt it, combine patterns, and send code to the Civil 3D plugin. The tradeoff is clear: the more flexible the tool, the stricter the governance required.
Skills library
The repository contains skills folders for surfaces, alignments, points, geometry, drawing, and workflows. The README describes them as documented C# code templates. This library acts as a partial guardrail: the assistant does not necessarily start from a blank page, it can rely on structured snippets.
Globals available to executed code include Document, CivilDoc, Database, Transaction, and Editor. According to the README, all Civil 3D namespaces are auto-imported. For a technical team, this makes the project much more expressive than a 2D drawing connector.
Code execution architecture
Key point: the chain goes through a TypeScript server, a Civil 3D plugin, and a Roslyn engine. This is not simple click automation.
MCP server and Civil 3D plugin
The README describes communication between the MCP client and a TypeScript server over stdio, then between the server and Civil 3D plugin over TCP/JSON-RPC on port 8080 by default. The verified package.json shows a civil3d-mcp package at version 1.0.0, depending on the MCP SDK, ws, and zod, with TypeScript 5.8.2 for development.
Setup requires building the server with npm install and npm run build, building the .NET plugin after copying Civil 3D DLLs into C_References, then loading Civil3dMcpPlugin.dll in Civil 3D with NETLOAD. The README then gives C3DMCPSTATUS to verify that the plugin is running. This flow is clearly for a technical workstation, not an unsupported user.
Read-only and write access
The split between civil3d_query and civil3d_execute is the most important design point. In read-only mode, the assistant can query surfaces, objects, layers, or parameters without committing a transaction. In write mode, it can modify the Civil 3D drawing. That separation should be mirrored in every firm procedure.
A good first phase should use civil3d_query only. It verifies that the assistant understands the drawing, returns usable JSON, and modifies nothing. Write operations should only come after template review and copy-based testing.
Professional use cases
Key point: Civil 3D MCP mainly interests infrastructure, site works, and surveying teams already manipulating structured Civil 3D objects. It is too specialized for general usage.
Surfaces, alignments, and COGO points
The README cites skills for surfaces, alignments, and points. In practice, those are the foundations of a Civil 3D workflow: reading existing surfaces, querying alignments, working in station/offset, or analyzing COGO points. The README example shows a surface query returning each surface name and layer.
These use cases are credible in read mode. An assistant can help inventory objects, check presence, or prepare a summary for a technical meeting. In write mode, the stakes rise: creating or modifying Civil 3D objects can affect profiles, drawings, quantities, and deliverables.
Geometry and workflows
The geometry, drawing, and workflows folders indicate a wider scope: lines, polylines, text, drawing information, and multi-object operations. The project can therefore build contextual Civil 3D scripts instead of calling one fixed function. That is powerful for teams that can already read C# or at least review a script's intent.
For a non-technical team, the same design can become opaque. A correct JSON result does not prove that executed code is safe for the drawing. Complex workflows should therefore remain under the responsibility of a Civil 3D referent.
Comparison with AutoCAD MCP and Revit MCP
Key point: Civil 3D MCP is the most flexible CAD/BIM connector reviewed here, but also the one that demands the most discipline.
| Option | Natural use | Main strength | Main risk |
|---|---|---|---|
| Civil 3D MCP | Executing Civil 3D C# through templates | Very flexible API access, read or write mode | Generated code affecting Civil 3D drawings |
| AutoCAD MCP | Automating AutoCAD LT and DXF | Documented backends, consolidated tools | execute_lisp and operations on DWG drawings |
| Revit MCP | Acting on a Revit model | Ready-to-use BIM tools | Write commands on a building model |
Civil 3D MCP versus AutoCAD MCP
The AutoCAD MCP exposes consolidated tools for drawing, entities, layers, blocks, annotations, P&ID, view, and system. Civil 3D MCP instead exposes meta-tools that execute code. AutoCAD MCP is more bounded; Civil 3D MCP is more extensible.
The professional difference is just as important. AutoCAD MCP mostly manipulates 2D drawings or DXF files. Civil 3D MCP manipulates civil engineering objects, with surfaces, alignments, points, and model logic. The choice depends on project type, not only installed software.
Civil 3D MCP versus Revit MCP
The Revit MCP exposes a more directly readable command set: creating levels, rooms, dimensions, grids, and extracting quantities. Civil 3D MCP asks the assistant to produce C#, often from a skill. That opens more possibilities, but makes review more technical.
For an architecture firm, Revit MCP is closer to building BIM. For an infrastructure or site works office, Civil 3D MCP is closer to the field. They are not direct competitors: they serve different modeling domains.
Security and limits
Key point: executing C# code inside Civil 3D should be treated as a high-privilege capability. Read-only mode helps, but does not make every usage safe.
Roslyn sandbox
The README says the sandbox blocks Process.Start, File.Delete, network requests through HttpClient or sockets, registry access, and dynamic assembly loading. That is a positive signal, because those actions sit outside normal Civil 3D scripting needs. But the README also states that all Civil 3D API operations are allowed.
In other words, the sandbox reduces some system risks, not professional drawing risks. Allowed code can still modify a drawing, create wrong objects, apply wrong layers, or commit an unsuitable transaction. Security has to be handled at drawing level as well as IT level.
Maintenance signals
The repository is recent and smaller than the verified AutoCAD or Revit connectors: 26 stars and 13 forks at GitHub check time, with recent activity. The README and GitHub show MIT licensing, but package.json says ISC and includes repository metadata pointing to civil3d-mcp/civil3d-mcp. That kind of mismatch is not necessarily blocking, but should be watched before adoption.
A firm should not integrate this connector without version pinning, model copies, rollback procedure, and review of the templates used. civil3d_query should remain the default entry point.
Educasium's position
Key point: Educasium can analyze Civil 3D MCP as an advanced tool, but should not present it as already validated on a client project.
Available experience
Educasium has not yet deployed Civil 3D MCP in a client site works, surveying, or infrastructure office, nor measured real gains on Civil 3D drawings. This analysis relies on the README, package.json, skills tree, and verified GitHub metadata. It is a capability review, not a case study.
This level of caution is required because the tool executes code. Serious training should not start with civil3d_execute on a production file. It should start by understanding Civil 3D drawing structure, professional objects, then the difference between read queries and write transactions.
Hypothetical implementation
Hypothetical implementation. For an Educasium pilot, the first step would be building the TypeScript server, loading the plugin into a test Civil 3D installation, verifying C3DMCPSTATUS, then querying the drawing only through civil3d_query. First questions should cover surfaces, layers, COGO points, and drawing information.
The second step would pick a simple skill, read it, understand the generated code, then run it on a copy. civil3d_execute should only be available to a referent able to review C# or at least validate the technical intent. The right result is a reliable protocol, not a spectacular demo.
Sources and next reading
Key point: the information on this page comes from GitHub and was verified on August 26, 2026. Meta-tool, sandbox, port 8080, skills folder, and setup details come from the README and repository tree.
What to read next
For building workflows, compare with the Revit MCP. For more classic DWG flows, also read AutoCAD MCP and CAD-MCP. These three connectors cover different realities: building BIM, Civil 3D infrastructure, and 2D CAD drawing.
To place these tools in a broader AI strategy, read the AI software comparison for architects and the Mastering AI in Architecture course.