Artificial Intelligence — MCP Commands

Introduction

tcpMDT 2026 lets you control MDT using natural language from artificial intelligence assistants compatible with MCP (Model Context Protocol). Simply describe what you need: the assistant chooses the appropriate command, fills in its details and runs it on the active drawing in CAD.

The workflow is always the same:

1. Write the instruction in natural language, in your own words.

2. The assistant interprets the request and selects the matching command.

3. The command runs on the active drawing and the assistant shows you the result.

General requirements

• tcpMDT 2026 running on a supported CAD platform.

• An MDT drawing open and active in CAD. All commands act on that drawing.

• An artificial intelligence assistant compatible with MCP, connected to tcpMDT 2026.

• Some commands need data already present in the drawing (an active surface, an alignment, a profile already generated...). Each entry indicates this in its prerequisites section.

Command summary

1. Points

Query points — query_points

Queries the MDT points in the active drawing and shows, for each one, its number, its X, Y, Z coordinates and its code. You can filter by code and by elevation range.

Data you can provide:

Result: a list of points with their number, X, Y, Z coordinates and code.

Example instructions:

• "Show me all the points in the drawing with code BASE."

• "List the points with elevation between 500 and 520 metres."

• "Show me the points with code CUNETA above 480 m."

• "Give me the points in the drawing."

Point information — get_point_info

Shows all the data of a specific point: number, X, Y, Z coordinates, code, level and layer.

Data you can provide:

Result: point record with its coordinates, code, level and layer.

Example instructions:

• "Give me the data of point 125."

• "On which layer is point 40 and what code does it have?"

• "Show me the complete information of point 1502."

• "What is the elevation of point 88?"

List codes — list_codes

Lists all the distinct codes that appear in the points of the drawing, with the number of points of each one. The list is sorted alphabetically.

Data you can provide: no data is required.

Result: alphabetical list of codes, with the number of points of each one.

Example instructions:

• "Which codes are in the drawing?"

• "Give me the list of codes with how many points each one has."

• "List the codes of the survey so I know which ones I can connect."

Draw breaklines by code — draw_breakline_by_code

Draws one or several 3D breaklines connecting the points that have the indicated code, in ascending order of point number. If distance, elevation difference or angle limits are given, the line is cut into separate sections each time one of those limits is exceeded.

Data you can provide:

Result: a 3D polyline in CAD with the points connected. If the filters cut it, several polylines are drawn and the assistant states how many were created.

Example instructions:

• "Draw the breakline of the points with code CAMINO."

• "Connect the points with code BORDILLO in a breakline, cutting it where there is more than 30 metres between points."

• "Draw the points with code CUNETA on layer CUNETAS, in colour 1."

• "Make the breakline of code TALUD on layer ROTURAS and cut the line if the elevation changes by more than 2 metres between consecutive points."

Draw breakline by point number range — draw_breakline_by_range

Draws a 3D breakline connecting the points whose number lies between two values. Both ends are included. Numbers that do not exist in the drawing are skipped.

Data you can provide:

Result: a breakline with the number of vertices and the layer where it was drawn.

Example instructions:

• "Draw a breakline with the points from 100 to 250."

• "Connect points 1 to 80 on layer EJE_TERRENO."

• "Make a breakline with the points from 500 to 520 in colour 3."

Connect points by proximity — connect_points_by_proximity

Connects with 3D polylines the points of the same code, as long as each consecutive point is no further away than the indicated limit. The assistant sorts the points by number, applies the filters and draws the result in a single operation.

Data you can provide:

Result: the polylines created, with the number of vertices and the layer used. If a single polyline is created, its number of vertices is stated.

Example instructions:

• "Connect the points with code BORDILLO as long as they are 15 metres apart or less."

• "Connect the points with code CUNETA with a maximum of 10 m between points and 0.5 m of elevation difference."

• "Connect the points with code MURO at 5 m distance and a maximum angle of 30 degrees, on layer MUROS."

2. Layers and drawing

Create layer — create_layer

Creates a layer in the drawing with the indicated name and, if desired, a colour and a line type. If the layer already exists, the assistant says so without raising any error.

Data you can provide:

Result: confirmation of the layer created, with its colour. If it already existed, the assistant reports it.

Example instructions:

• "Create a layer called ROTURAS in colour 1."

• "Create the layer EJES_PROYECTO with a dashed line."

• "Create the layer CURVAS_NUEVAS in colour 3 with a continuous line."

Drawing summary — get_drawing_summary

Shows a general summary of the active drawing: X, Y and Z coordinate limits, assigned coordinate system, number of MDT points, active surface (name and 2D area) and number of alignments.

Data you can provide: no data is required.

Result: summary of the state of the drawing.

Example instructions:

• "Give me a summary of the drawing."

• "Which coordinate system does the project use and how many points are there?"

• "How many alignments are there and which surface is active?"

• "Show me the general state of the drawing."

Set layer visibility — set_layer_visibility

Shows or hides a specific layer, identified by its exact name, or all the layers of a group.

Data you can provide:

Indicate one layer or one group, but not both at once.

Result: confirmation of the layers that were shown or hidden. If the group indicated has no layers in the drawing, the assistant says so.

Example instructions:

• "Hide layer CURVAS_NORM."

• "Show all the contour lines."

• "Hide the points in the drawing."

• "Show the breaklines."

3. Surfaces

Create surface — create_surface

Creates a triangulated surface (TIN) from the MDT points of the drawing and draws it in CAD. It can take into account the breaklines of the indicated layers, so that the discontinuities of the terrain are respected. The surface file is saved in the same folder as the drawing.

Data you can provide:

Result: number of triangles and vertices, planar (2D) area and real (3D) area, minimum and maximum elevations, drawing layer and generated file.

If a surface file with that name already exists, the command does not overwrite it and the assistant will ask you for another name.

Example instructions:

• "Create the surface of the drawing with the breaklines of layers CAMINO and BORDILLO."

• "Generate the surface called TERRENO_ACTUAL with no triangle side limit."

• "Create a surface called PROYECTO_2 and draw the triangles as lines."

• "Make the surface of the drawing with triangle sides of 20 metres at most."

Surface information — get_surface_info

Shows the state and statistics of the active surface of the drawing.

• If it is a triangulated surface (TIN), it shows the number of triangles and vertices, the planar and real areas, the layer and the elevation range.

• If it is a mesh, it shows the number of valid cells, the planar area and the elevation range.

If there is no active surface, the assistant says so.

Data you can provide: no data is required.

Result: record of the active surface with its statistics, or a notice that there is no active surface.

Example instructions:

• "Which surface is active in the drawing?"

• "Give me the statistics of the surface."

• "What is the minimum and maximum elevation of the terrain?"

• "What is the real area of the surface?"

Generate contour lines — generate_contours

Generates contour lines from the active triangulated surface and draws them as 3D polylines in two layers: one for normal contour lines and another for index (major) contour lines.

Data you can provide:

Result: number of normal and index contour lines, layers used and elevation range (minimum and maximum).

Example instructions:

• "Generate the contour lines every metre."

• "Generate contour lines every 0.5 m with index lines every 5 m."

• "Generate contour lines every 2 metres, without index lines."

• "Regenerate the contour lines, clearing layers CURVAS_NORM and CURVAS_DIR first."

Volumes between two surfaces — calculate_volume

Calculates the cut and fill volumes between two MDT surfaces, using the grid difference method.

Data you can provide:

Result: cut volume (m³) with its area, fill volume (m³) with its area, net volume (m³), area with no volume if any, number of cells processed and cell size used.

Example instructions:

• "Calculate the earthwork between original.sup and proyectado.sup."

• "How much cut and fill is there between the terrain surface and the grade surface?"

• "Calculate the volumes between D:\proyecto\original.sup and D:\proyecto\proyectado.sup with 0.5 m cells."

Earthwork for a platform — calculate_earthwork

Calculates the earthwork of a platform drawn as a closed polyline on a layer. It obtains the cut and fill volumes, both inside the platform and on its slopes, and draws the contact line with the natural terrain. It is the non-interactive equivalent of the MDT command Platform by level (Explanada por cota).

Data you can provide:

Result: elevation used (or balance elevation found), minimum, mean and maximum terrain elevations inside the platform, cut, fill, net volume, areas of the platform and of the slopes, and number of points of the contact line drawn. If a surface is generated, the assistant also gives its file.

Example instructions:

• "Calculate the earthwork of the platform on layer EXP at elevation 530 metres."

• "Find the balance elevation of the platform on layer EXP."

• "What is the mean terrain elevation inside the platform on layer EXP?"

• "Calculate the platform on layer PLATAFORMA with a cut slope of 1 and a fill slope of 2."

4. Alignments and longitudinal profiles

List alignments — list_alignments

Lists all the alignments of the active drawing, with the name, starting station, ending station and length of each one. If the drawing has no alignments, the assistant says so.

Data you can provide: no data is required.

Result: list of alignments with their starting station, ending station and length.

Example instructions:

• "Which alignments are in the drawing?"

• "List the alignments with their length."

• "Between which stations does the road alignment run?"

Find alignment — find_alignment

Finds an alignment by part of its name, ignoring upper and lower case, and zooms in CAD to its surroundings. It shows the name, starting station, ending station and length of the alignment found.

Data you can provide:

If no alignment matches, or if several match, the assistant says so and shows the matching alignments. In that case, make the name more specific.

Result: name, starting station, ending station and length of the alignment, and the CAD view centred on it.

Example instructions:

• "Find alignment eje2 and zoom to it."

• "Locate the road alignment."

• "Show me where the alignment Principal is."

Generate longitudinal profile — generate_profile

Generates the longitudinal terrain profile along an alignment, taking the elevations from the active surface. The result is saved as a file next to the alignment.

Data you can provide:

Result: number of profile points, starting and ending station, minimum and maximum elevations, and path of the generated file.

Example instructions:

• "Generate the longitudinal profile of alignment eje2."

• "Calculate the profile of the road alignment with a point every 5 metres."

• "Generate the profile of the main alignment and then draw it."

Draw longitudinal profile — draw_profile

Draws the longitudinal profile of an alignment with its Numerical Data (data table), at the indicated scale. It is always drawn in model space, with the origin calculated automatically.

Data you can provide:

Result: number of points drawn and scales used.

Example instructions:

• "Draw the longitudinal profile of alignment eje2 at scale 1:500."

• "Draw the profile of the main alignment with horizontal scale 1:1000 and vertical scale 1:100."

• "Represent the profile of the road alignment with its Numerical Data."

5. Cross sections

Generate cross sections — generate_cross_sections

Generates the cross sections of an alignment from the active surface, using the triangulated surface or the mesh as the basis. The result is saved as a file next to the alignment.

Data you can provide:

Result: number of cross sections generated, starting and ending station, minimum and maximum terrain elevations, and path of the generated file.

Example instructions:

• "Generate the cross sections of eje2 every 20 metres, with 15 m on each side."

• "Calculate the cross sections of the road over the active surface."

• "Generate cross sections of the main alignment with 25 m on the left and 10 m on the right."

Draw cross sections — draw_cross_sections

Draws the cross sections of an alignment at the indicated scale, without the data table (Numerical Data). It is always drawn in model space, with the origin calculated automatically.

Data you can provide:

Result: number of points drawn and scales used.

Example instructions:

• "Draw the cross sections of eje2 at scale 1:500."

• "Represent the cross sections of the road at horizontal scale 1:1000 and vertical scale 1:200."

• "Draw the cross sections of the main alignment without Numerical Data."

Draw cross sections with Numerical Data — draw_cross_sections_with_numerical_data

Draws the cross sections of an alignment at the indicated scale, with their Numerical Data (attached data table). It is always drawn in model space, with the origin calculated automatically.

Data you can provide:

Result: number of points drawn and scales used.

Example instructions:

• "Draw the cross sections of eje2 with Numerical Data at scale 1:500."

• "Represent the cross sections of the road with their Numerical Data."

• "Draw the cross sections of the main alignment with Numerical Data, at horizontal scale 1:1000 and vertical scale 1:200."

Volume by cross-section differences — calculate_cross_section_volume

Calculates the cut and fill volumes by difference between two cross-section files (.tra). It compares file 2 (modified or design) against file 1 (terrain or original situation).

The calculation always uses the default values: the whole station range common to both files, vertical slope and no curvature correction. It is always calculated without topsoil.

Data you can provide:

Result: files used, cut volume (m³), fill volume (m³), net volume (m³), clearing area (m²) if any, and number of cross sections measured.

Example instructions:

• "Calculate the volume between the cross sections terreno.tra and rasante.tra."

• "How much cut and fill is there between the terrain cross sections and the design ones?"

• "Give me the net volume between the cross sections original.tra and final.tra."

Pavement layers measurement — calculate_pavement_layers

Measures the pavement layers of a road from its segment file (.seg). For each material (pavement layers and, if any, subgrade replacement and reinforcement) it calculates the thickness and the volume, plus the total volume. By default, the measurement is made at singular points, over the whole road and deducting the structure sections.

Data you can provide:

Result: segment measured, starting and ending stations used, and a table with each material, its thickness (m), its volume (m³) and the total volume.

Example instructions:

• "Measure the pavement layers of the file segmento1.seg."

• "Measure the pavement layers of the segment Eje1 between station 100 and 450."

• "Calculate the material volumes of the segment carretera.seg."

• "Give me the thickness and volume of the pavement layers of the main segment."

6. Stakeout

Analyse points against the surface — analyze_points_surface

Analyses points against the active surface of the drawing. For each point it calculates the elevation of the surface at its position and the difference with the elevation of the point. The points can come from a text file or be the MDT points of the drawing. Optionally, the analysis can also be made against an alignment.

Data you can provide:

Result: list of points with their name, X, Y, Z coordinates, surface elevation and elevation difference. If the analysis is against an alignment, it also shows the station and offset. At the end, a summary shows the number of points analysed, those outside the surface, and the minimum, maximum and mean elevation difference.

The difference is the elevation of the point minus the elevation of the surface: a positive value means the point is above the surface. Points that fall outside the surface appear in the list without surface elevation or difference, and are not included in the statistics.

Example instructions:

• "Analyse the points of the file levantamiento.txt against the surface."

• "Analyse the drawing points with code BASE against the surface."

• "Calculate the elevation difference of the points in file puntos.txt and their position against alignment carretera."

• "Tell me which points are above or below the surface."

Stakeout lines list — stakeout_lines

Calculates the stakeout points of the elements of the section you indicate (for example, lane, ditch or toe of slope), at station intervals. The calculation is made without dialogues, on both sides of the alignment or on just one of them, from a segment file or from the alignment of the drawing.

Data you can provide:

Recognised names: in addition to numbers, the command recognises the names of the elements of the MDT template, such as Carril 1, Arcén Exterior, Arcén Interior, Berma, Mediana or Acera. It also accepts:

• Pie de firme: end of the platform (Explanada).

• Pie de talud: all the codes of the fill slope (terraplén).

• Cabeza de talud: all the codes of the cut slope (desmonte).

• Cuneta: all the ditches.

• Eje: code 0 (alignment).

• Muros: walls.

If a name is not recognised, the assistant shows the list of available names so you can choose the equivalent.

Result: a table with the code, name, station, offset from the alignment, and the X, Y and Z coordinates of each point. Before the table, the header shows the segment (and the alignment, if one was used), the starting and ending station, the interval, the codes, the side and the number of points. The offset is negative to the left of the alignment and positive to the right.

Example instructions:

• "Stake out the Carril 1 of segment Eje1 every 20 metres."

• "Stake out the ditch and the toe of slope of segment Eje1 every 20 metres."

• "Give me the stakeout points of the alignment and the ditches of segment carretera.seg every 10 metres."

• "Calculate the stakeout list of the left side of segment Eje1 between station 100 and 450, every 20 metres."

• "Give me the toe of slope points of segment principal.seg every 25 metres."

7. Plots

List plots — list_plots

Lists the plots of the active drawing with their name, area, cadastral reference, owner, type and centroid. If the drawing has no plots, the list is empty.

Data you can provide:

Result: list of plots with their name, area (m²), cadastral reference, owner, type and centroid. With the vertices option, also the coordinates of each vertex.

Example instructions:

• "How many plots are there in the drawing?"

• "List all the plots with their area and owner."

• "Show only the plots of cadastral type."

• "List the buildings defined in the drawing."

• "Give me the centroid coordinates of each plot."

Plot details — edit_plot

Shows the full details of a plot: name, cadastral reference, area (m²), perimeter (m), number of vertices and the X, Y coordinates of each vertex, numbered from 1.

Data you can provide:

Result: plot record, with its data and the numbered list of its vertices.

Example instructions:

• "Show me the data of plot PCL-001."

• "What is the area and perimeter of plot 5?"

• "Give me the vertex coordinates of cadastral plot 0001."

• "What cadastral reference does plot A have?"

Merge plots — merge_plots

Merges several adjoining plots of the drawing into one. It draws the resulting plot and removes the original plots from the drawing.

Data you can provide:

Result: name, cadastral reference, area (m²), perimeter (m) and number of vertices of the resulting plot.

Example instructions:

• "Merge plots PCL-001 and PCL-002."

• "Join plots PCL-001, PCL-002 and PCL-003 into one, called FINCA-A."

• "Combine these two adjoining plots into a new one called Solar 7."

Split a plot into parallel strips — split_plot_parallel

Splits a plot of the drawing into strips using lines parallel to the side defined by two of its vertices. It supports three split modes.

Data you can provide:

Result: name of the original plot, mode applied, original area (m²), number of sub-plots created and mean area per strip (m²).

Example instructions:

• "Split plot PCL-001 into 4 equal strips, parallel to the side between vertices 1 and 2."

• "Split plot A into strips of 500 m² each."

• "Divide plot 3 into strips 20 metres wide, parallel to the side between vertices 1 and 4."

Locate a plot — find_plot

Locates a plot of the drawing by its name and zooms in CAD to a window around it.

Data you can provide:

Result: confirmation of the plot located and of the zoom window applied, with the coordinates of its two corners.

Example instructions:

• "Locate plot PCL-001 and zoom to it."

• "Show me where plot 5 is in the drawing."

• "Centre the view on cadastral plot 0001."

Export plots to GML — export_plot_gml

Exports one or several plots of the drawing to the GML INSPIRE 4.0 format.

Data you can provide:

Result: number of plots exported, coordinate reference system used (EPSG code) and path of the generated file.

Example instructions:

• "Export plots PCL-001 and PCL-002 to D:\proyecto\parcelas.gml."

• "Generate an INSPIRE GML with all the cadastral plots in the drawing."

• "Export plot 5 to the GML format."

Query the fields of a Shapefile — get_shapefile_fields

Shows the structure of a Shapefile (.shp + .dbf) before importing it: geometry type, number of entities and the fields of the attribute table with sample values. It is the first step of the plot import: it helps you decide which field holds the name, the cadastral reference, the owner and the date.

Data you can provide:

Result: geometry type (polygons, lines, points or other, indicating whether it has Z), number of entities and, for each field, its name, type, width, decimals and the values of the first 3 records (truncated to 50 characters). If the file contains the fields label, localId or beginLifes (INSPIRE cadastre), the assistant suggests them as name, reference and date.

Example instructions:

• "Which fields does the shapefile D:\proyecto\catastro.shp have?"

• "Show me the attributes of D:\catastro\parcelas.shp."

Import plots from a Shapefile — import_plots_shapefile

Imports the polygons of a Shapefile as plots, without dialogs. It is equivalent to the Plots > Import command with a Shapefile: instead of the attribute mapping window, you state in the conversation which .dbf field matches each plot attribute.

Data you can provide:

The same field can be assigned to several attributes (for example, the cadastral reference as both name and reference). Attributes you do not mention are left unassigned. Field names are not case-sensitive.

Result: number of plots imported, number of polygons skipped (those that did not produce a plot, for example because their area is below the configured minimum), layer created and field mapping applied.

Example instructions:

• "Import the plots from D:\proyecto\catastro.shp."

• "Import D:\proyecto\catastro.shp using REFCAT as name and reference, TITULAR as owner and FECHA_ALTA as date."

• "Import the plots from D:\catastro\parcelas.shp with the fields you suggest."

Behaviour:

• The whole file is imported, without a selection window, and the view zooms to the drawing extents at the end.

• The text height is the one configured in MDT; it is not asked.

• A layer named after the file is created and made current.

• Entities excluded by the configured exclusion pattern are not imported and count neither as imported nor as skipped.