About
Tools built by someone who uses them.
For now, MD Automation is one person: Marc-Antoine Doyon, an independent developer in Québec, Canada. It exists for one reason: too many hours of CAD work go into tasks a computer should do in one click.
Québec, Canada · 5 plugins shipped · 5 in the pipeline
Principles
What we believe
Plugins should feel native
Commands live in the ribbon and the right-click menu, respect pick-first selection, and undo cleanly. If it doesn't feel like AutoCAD, it isn't finished.
Buying software should be simple
One payment, a perpetual licence bound to your machine, no account to manage. It works entirely offline: the plugin never phones home.
Small and sharp beats big and bloated
Each plugin does one job extremely well, stays fast, and shares a single ribbon tab and licensing experience with the others.
The person who wrote it answers the email
For now there is no support tier and no ticket queue: every plugin was built by one developer who uses them daily, and a question about how something works reaches that developer. That stays true for as long as it can.
Under the hood
Written in C#, on the Autodesk .NET API.
Every MD Automation plugin is managed .NET code, written in C# against the Autodesk .NET API, for AutoCAD 2025 and later on 64-bit Windows. That is what lets a command sit in the ribbon, respect pick-first selection and undo in one step, the way a native command does.
C# · .NET · Autodesk .NET API · AutoCAD 2025+ · Win64
Roadmap
What's shipped, and what's next.
Licence Manager
AvailableTrials, licence requests, and activation in one window, shared by every MD plugin.
How licensing worksAlign & Distribute
AvailableLine up and space out any selection by its bounding boxes.
See what it doesPlugin 06
Q4 2026Not announced yet.
Plugin 07
Q4 2026Not announced yet.
Plugin 08
Q1 2027Not announced yet.
Plugin 09
Q1 2027Not announced yet.
Plugin 10
Q1 2027Not announced yet.