mcp · Global

cloudcompare-mcp

Cross-platform MCP server for CloudCompare point cloud processing

Claim this listing

Represent cloudcompare-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: point cloud metadata (point count, bounding box, extent, density, RGB/intensity/normals presence) · top/front/side rendered views with metadata panel (PNG) · CloudCompare info and file statistics · subsampling (random, spatial, octree) · cloud-to-cloud nearest-neighbour distances · cloud-to-mesh signed distances · ICP registration · surface normal estimation · scalar field threshold filtering · statistical outlier removal · merging clouds · format conversion · arbitrary CloudCompare CLI commands
Formats docs-verified: LAS · LAZ · PLY · PCD · XYZ · ASC · TXT · E57 · OBJ · BIN · SHP
Access llm-inferred: MIT licence. Native tools need no extra software. CloudCompare tools need CloudCompare ≥ 2.12 installed separately (CLOUDCOMPARE_PATH or PATH, or default install location).

Use cases llm-inferred: As-built vs design QA: cloud-to-mesh distances between a laser scan of an earthwork or structure and its design surface · Survey clean-up before deliverables: statistical outlier removal and spatial subsampling of lidar or scan data · Multi-epoch change detection: cloud-to-cloud distances between repeat scans of a slope, bank or channel · Scan registration: ICP alignment of survey scans taken from different setups
Audience llm-inferred: BIM/civils engineers · geotechnical engineers · GIS analysts · surveyors

Constraints llm-inferred: Most tools need a local CloudCompare ≥ 2.12 install; only read_cloud_metadata and visualize_cloud work without it · Requires Python ≥ 3.10 and uv or pip · run_cloudcompare_command is a raw CLI escape hatch and is not constrained by the server · SHP is listed as a supported file format but not among the convert_format targets · Single open-source GitHub project; maintenance and long-term support are unknown · Output quality depends on input cloud quality and CloudCompare's own behaviour, which the docs do not cover

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Geospatial deep dive (Glama/Smithery/GitHub). Tools/install/auth auto-extracted from README.

Metadata observed 15/10/2026 · research sweep: geo-deep-dive (geo-deep-dive:github-search-geo)