Overview This MCP server exposes csv2shp, a GIS conversion tool that reads a CSV file containing point coordinates, auto-detects the column delimiter and decimal separator, and writes the data to an ESRI Shapefile with the specified coordinate reference system.

Tool: csv2shp Description Converts a CSV file with X/Y coordinate columns into an ESRI Shapefile (.shp). All CSV columns are preserved as attribute fields. The delimiter (comma, semicolon, tab, etc.) and decimal separator (dot or comma) are detected automatically.

Parameters Parameter Type Required Description file string Yes Path to the input CSV file. X string Yes Name of the column containing the X-coordinate (easting / longitude). Y string Yes Name of the column containing the Y-coordinate (northing / latitude). epsg integer Yes EPSG code for the coordinate reference system (e.g. 28992 for Amersfoort / RD New, 4326 for WGS 84). out string Yes Output path for the Shapefile (e.g. output/points.shp). Output An ESRI Shapefile consisting of .shp, .shx, .dbf, .prj, and .cpg files written to the specified output path. Each row in the CSV becomes a point feature.

Example usage Supported coordinate systems Any CRS with a valid EPSG code is supported. Common examples:

EPSG CRS Name 4326 WGS 84 (lat/lon) 28992 Amersfoort / RD New (Netherlands) 32631 WGS 84 / UTM zone 31N 3857 Web Mercator Dependencies pandas geopandas rasterio shapely Limitations Input must be a CSV file with consistent delimiters and at least one row of data. Coordinate columns must contain numeric values; non-numeric entries will cause errors. Output overwrites existing files at the target path without warning. The decimal separator auto-detection uses the first occurrence of . or , in the file, which may be incorrect for files that use commas as both delimiter and decimal separator. This covers what GITMCP needs to index the tool: a clear description, typed parameter table, output specification, and usage example. The llms.txt that GITMCP generates from this README will give Copilot Studio enough context to match user intent and populate the parameters correctly.