mcp · Global

Civil3d-mcp-tcce

MCP server that lets Claude work in Autodesk Civil 3D 2027 (.NET 10). TCCE fork of barbosaihan/civil3d-mcp adding road design (alignments, profiles, assemblies, corridors, superelevation), earthwork (Top/Datum surfaces, pads, volumes, mass haul), styles & label sets, blocks and hatches.

Visit source ↗GitHub repository ↗

Feature or claim this listing

Feature this listing — founding Featured slots are 50% off for 6 months

Represent Civil3d-mcp-tcce? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Explore paid sponsorship →

What's in it

Data offered docs-verified: road alignments, profiles, assemblies and corridors · superelevation (experimental) · surface sampling and grid elevations · earthwork: Top/Datum surfaces, pads, cut/fill volumes, mass haul · pipe networks and interference checks · points, geometry, blocks, hatches · styles and label sets
Coverage llm-inferred: Global
Formats llm-inferred: MCP stdio · TCP/JSON-RPC (server to Civil 3D plugin) · CSV · DWG (Civil 3D drawings)
Access docs-verified: MIT licence for this server (per catalogue metadata). Requires a licensed Autodesk Civil 3D 2027 installation and the proprietary Autodesk DLLs copied locally; the DLLs are not in the repository. No API key or OAuth (auth null in catalogue).

Useful for

Use cases llm-inferred: Corridor earthwork: Top/Datum surfaces and cut/fill volumes with mass haul for a highway scheme · Development pad earthworks with daylight slopes and volume balance · Road alignment and profile checks (Rmin, grades, K values) during preliminary design · Drainage pipe network layout and interference checks in Civil 3D
Audience llm-inferred: highway and civils design engineers · BIM/civils engineers · earthworks and quantity surveyors · drainage engineers

Limitations

Constraints docs-verified: Some tools are untested: those marked (to verify) have not been fully tested on a real drawing; apply_superelevation is experimental · Some original actions return 'planned' and are not implemented (e.g. alignment/profile create, surface add_breakline and extract_contours) · Pad daylight is computed geometrically because the Civil 3D .NET API cannot create Grading objects · Volume CY values assume feet · Requires a running Civil 3D session with the plugin loaded and listener started (NETLOAD, C3DMCPSTATUS) · Plugin port is hard-coded to 8080 in PluginRuntime.cs and must be changed in code if it clashes · Civil 3D 2025/2026 need the plugin retargeted from .NET 10 to .NET 8 · Setup steps are Windows/PowerShell-based · Fork of upstream barbosaihan/civil3d-mcp with maintenance risk; no UK-specific datasets or standards are described · Tool list in catalogue metadata does not match the docs (civil3d_road, civil3d_earthwork, civil3d_block, civil3d_style are documented but not listed)

Licence: MIT
Authentication: Unknown — review source docs
GitHub stars: 1
Last commit: 07/10/2026
Last successful page check: 14/10/2026
Page health: healthy
Package: Not recorded
Verification: Not independently verified

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Provenance & evidence

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 16/10/2026 · research sweep: github-search