Civil 3D MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level (debug, info, warn, error) | info |
| CIVIL3D_HOST | No | Civil 3D plugin host | localhost |
| CIVIL3D_PORT | No | Civil 3D plugin port | 8080 |
| CIVIL3D_COMMAND_TIMEOUT | No | Command execution timeout (ms) | 120000 |
| CIVIL3D_CONNECT_TIMEOUT | No | Connection timeout (ms) | 5000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| civil3d_healthA | Checks if the Civil 3D MCP plugin is running and responsive. Use this to verify connectivity before performing other operations. |
| civil3d_drawingA | Manage the active Civil 3D drawing. Actions: info (get drawing info), settings (get drawing settings), save, new, undo, redo, list_object_types (list available Civil 3D object types), get_selected (get info about selected objects). |
| civil3d_surfaceB | Manage Civil 3D surfaces. Actions: list, get (by name), get_elevation (at X,Y), get_statistics, create, delete, add_points, add_breakline, add_boundary, extract_contours, compute_volume (between two surfaces). |
| civil3d_alignmentC | Manage Civil 3D alignments (horizontal geometry). Actions: list, get (by name), create (from polyline), delete, station_to_point (convert station+offset to X,Y), point_to_station (convert X,Y to station+offset). |
| civil3d_profileA | Manage Civil 3D profiles (vertical geometry). Actions: list (by alignment), get (by alignment + name), get_elevation (at station), create_from_surface, create_layout, delete. |
| civil3d_corridorB | Manage Civil 3D corridors (3D road models). Actions: list, get (by name), rebuild, get_surfaces, get_feature_lines, compute_volumes. |
| civil3d_pipeA | Manage gravity pipe networks. Actions: list_networks, get_network, get_pipe, get_structure, create_network, add_pipe (between structures), add_structure (at X,Y), check_interference. |
| civil3d_pointA | Manage COGO (Coordinate Geometry) points. Actions: list (optionally by group), get (by point number), create (single or batch), delete, list_groups, import (from file). |
| civil3d_geometryB | Create basic AutoCAD geometry in Civil 3D. Actions: create_line (from start/end XYZ), create_polyline (from 2D vertices), create_3d_polyline (from 3D vertices), create_text, create_mtext. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct Civil 3D domain (alignments, corridors, surfaces, etc.) with no overlapping purposes. The health check tool is clearly separate for connectivity verification.
All tools follow a consistent 'civil3d_' prefix followed by a singular noun representing the domain (e.g., civil3d_alignment, civil3d_corridor). No mixing of conventions.
9 tools is well-scoped for a complex CAD environment like Civil 3D, covering major object types without being excessive.
Covers core workflows for alignments, corridors, surfaces, profiles, pipe networks, and points. Minor gaps (assemblies, subassemblies, annotation) but not critical for most operations.