Deneb Design MCP

Design by talking. Your agent, our analysis.

An MCP server for Deneb Design. Your AI agent creates and refines a UAV or drone design with the app’s own code: the geometry, the vortex lattice with section polars, the mass, the performance, the modes and the checks. Then it hands you a file to open in Deneb Aero.

Ask in words. Get numbers you can check.

The agent does not guess how an aircraft flies. It asks the same code the Design workspace runs, reads the numbers and the views, and changes the design until it does what you asked.

The agent's chat beside the design it made: get_template, analyze and render done, the survey plane in 3D, its best L/D 23.5, 156 minutes, stall 13.1 m/s and 13.6% static margin, and its lift curve and drag polar
  • 1

    Start from a sentence

    A template or the design written from scratch: wings, tails, bodies, motors, the battery and the mass.

  • 2

    Analyse and check

    Lift and drag, stall, static margin, the dynamic modes, flight time and range, and the app’s checks with their fixes.

  • 3

    Open it in Deneb Aero

    A file that opens as it was checked, to edit by hand, run in CFD or fly in the simulator.

Show it a drawing. It builds to match.

Give the agent a three-view and ask for something similar. It draws the design over your picture, view by view, and measures the match until each view reaches its target.

The three-view the user sent: a small fixed-wing UAV with a V-tail, 1500 mm span, top, front and side views
The drawing sent
The design the agent built to it, in 3D: a 1.5 m UAV with a slim pod, tapered wing with winglets and a V-tail
The design built, 1.5 m and 1.5 kg
From above: the design's outline drawn over the drawing's top view, a match of 0.999
From above: 0.999
From the side: the design's outline over the drawing's side view, a match of 0.945
From the side: 0.945
From ahead: the design's outline over the drawing's front view, a match of 0.79; the drawing's front view shows the V-tail wider than its top view
From ahead: 0.79. The drawing’s front view shows the V-tail wider than its top view does.

Four requests, four checked designs.

A UAV built to a drawing, then a survey plane at 7 kg in three steps. Every number on screen is the server’s own answer, worked out with section polars.

The UAV built to the drawing
Built to the drawing
The first survey plane: 2.4 m, conventional tail
The first design, 2.4 m
The survey plane with a 3.0 m wing
Flies longer: 3.0 m
The survey plane with its tailplane on top of the fin
A T-tail for harsh landings
RequestThe designBest L/DLongest flightStallStatic margin
“Can you build something similar?”, with a three-view1.5 m V-tail; matches the drawing 0.999 from above, 0.945 from the side17.8205 min8.6 m/s12.6%
First design2.4 m, conventional tail23.5156 min13.1 m/s13.6%
“Make it fly longer”3.0 m wing, aspect ratio 1526.4187 min12.5 m/s12.6%
“A T-tail for harsh landings”Tailplane on the fin, 288 mm higher26.2187 min12.4 m/s13.5%

Open it in Deneb Aero, and carry on by hand.

The agent’s file opens as a new design in the Design workspace. The same numbers, worked out again by the app: best L/D 26.2, stall at 12.4 m/s, a 13% static margin. Then edit it, run it in CFD or fly it.

The T-tail survey plane open in Deneb Aero's Design workspace: the lift drawn along the wing, its parts on the left and its numbers underneath: cruise CL 0.67 at 3.2°, L/D 26.1, stall 12.4 m/s, static margin 13%
The agent's turn for the T-tail: patch_design, check_design and save_design done; the design from two sides, best L/D 26.2, 187 minutes, stall 12.4 m/s, 13.5% static margin, and All checks good

The tools your agent gets.

Each tool takes a design and returns numbers, findings, pictures or a file. Every edit returns a new version, so the agent can compare and go back.

design_schemaThe design format: units, axes, conventions and the names a design may use.
list_templates, get_templateThe built-in designs to start from, with their span, area and parts.
analyzeTrim and stall, polar slopes, stability and modes, flight time, range, climb and glide, the mass.
check_designThe app’s own checks, each finding with the fix the app would apply.
renderTop, side, front and 3/4 views at a known scale, parts coloured by role.
compare_referenceA drawing or photo against the design, view by view, with a match score.
patch_designEdits as the app makes them: spans, chords, sweep, airfoils, bodies, CG, fixes.
save_designA file that opens in Deneb Aero exactly as it was checked.
parameters, featuresNamed parameters that drive parts, and the build order.
hardware and print_kitFittings, fasteners and a printable kit with its plates and print time.

On your computer, with the agent you use.

The server runs locally and talks to the agent over standard input and output. Nothing is hosted by us. Your agent sees what the tools return, as with any MCP server.

  • Any MCP client

    Claude Code, Claude Desktop, OpenAI Codex, Cursor, VS Code, Windsurf, Gemini CLI or any other client that speaks the Model Context Protocol.

  • What it cannot do yet

    Run the panel method, the Stress tab, Optimise or the CAD exports, or change a design that is open in the app: it writes a file to open.

  • In early testing

    The MCP server is not in the download yet. Join the beta and tell us you want to try it.