AutoCAD API Skillsby Autodesk Developer Network (ADN-DevTech)
Autodesk Developer Network skills that teach a coding agent to write AutoCAD, Civil 3D and Plant 3D .NET 10 plug-ins.
Plant 3D has no MCP server from Autodesk. Two community servers drive it on Windows: one builds, checks and renumbers P&IDs through the Plant 3D .NET API so lines stay connected, and one treats Plant 3D drawings as ordinary AutoCAD geometry for pipe-support registers. The Autodesk Developer Network skill helps coding agents write Plant 3D plug-ins. Version coverage is narrow: 2026–2027 for the P&ID server, and live tests on 2021 only for the other.
Autodesk Developer Network skills that teach a coding agent to write AutoCAD, Civil 3D and Plant 3D .NET 10 plug-ins.
Builds, checks and renumbers Plant 3D P&IDs through the Plant 3D .NET API, so lines connect and pass validation, with read-only piping queries.
A piping engineer's server for AutoCAD and Plant 3D drawings, live over COM or offline on DXF, built around pipe-support block registers.
Listings are sorted by origin, then by recent activity. GitHub data is refreshed nightly. Nothing here is ranked.
An MCP server or skill can only do what AutoCAD Plant 3D lets programs do. AutoCAD Plant 3D exposes 3 automation interfaces:
Autodesk has no Plant 3D MCP server or Plant 3D-specific AI assistant on record as of this check. Its in-app AutoCAD and Civil 3D MCP server names only those two products, and the Product Help server's coverage appendix doesn't list Plant 3D, though its tool reference uses a Plant 3D Spec Editor search as an example. The Autodesk Developer Network's skill covers the Plant 3D .NET API for plug-in developers.
Checked 4 Nov 2026. Sources: Autodesk AutoCAD and Civil 3D MCP Server (Autodesk Help), Product Help MCP Server, Appendix: Product Coverage (Autodesk Help), Product Help MCP Server, Tools and Language Support (Autodesk Help), ADN-DevTech/acad-api-skill, Plant 3D API notes
Taken from the listings' own documentation. Check each listing for exactly what it supports.
The listings here document setup for Claude Code, Claude Desktop, Cursor and VS Code (GitHub Copilot). Install steps, copied from each project's own documentation, are on each listing's page. Most AutoCAD Plant 3D integrations run on your own computer next to AutoCAD Plant 3D, so you need AutoCAD Plant 3D installed and licensed on the same machine unless the listing says otherwise.
No. Autodesk's in-application MCP server covers AutoCAD and Civil 3D only, and Plant 3D isn't in the Product Help server's coverage appendix. What Autodesk does publish is a developer skill, from its Developer Network, that teaches coding agents the Plant 3D .NET API.
Yes, with Eduardo Mariola's server, which places P&ID components and lines through the Plant 3D API so they pass validation and carry connectivity. It needs Plant 3D 2027 (or 2026 with a rebuilt plug-in) and a .NET plug-in you compile yourself.
They create plain AutoCAD lines and blocks, which Plant 3D's P&ID validation rejects and which carry no project data. Generic servers can still read and update block attributes, as the pipe support server does, but routing, specs and isometrics need the Plant SDK.
Partly. The P&ID server's checks read the project database file directly in read-only mode, and its 3D piping queries report line lists, BOMs and welds. Creating or changing P&ID objects still needs Plant 3D running with the plug-in loaded.
AI-generated models, drawings and results must be checked by a qualified engineer before use.
Sources (checked 4 Nov 2026): ADN-DevTech/acad-api-skill, Plant 3D API notes · The Data Manager (AutoCAD Plant 3D 2026 Help) · Eduardo-Mariola/autocad-plant3d-mcp README · Product Help MCP Server, Appendix: Product Coverage (Autodesk Help)
AutoCAD Plant 3D is a trademark of Autodesk. Tresca is independent and not affiliated with or endorsed by Autodesk.