← Directory
mcp · Global
lidar-mcp
MCP server for YDLIDAR USB LiDAR sensors (X2/X4/G1/G4/S series) — scan, stream, status
Claim this listing
Represent lidar-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.
What's in it
- Data offered docs-verified
- 2D point cloud: angle, distance and quality per point from a single 360-degree scan · device info and health (temperature, error codes) · point cloud summary (min/max distance, valid count) · live streaming of scan data · serial port auto-detection for YDLIDAR devices
- Update frequency docs-verified
- 360-degree sweeps at 5–12 Hz
- Formats llm-inferred
- MCP stdio
- Access llm-inferred
- Free and open source under the MIT licence; requires a physical YDLIDAR USB sensor ($30–80); local install with Python 3.12+ and uv
Useful for
- Use cases llm-inferred
- Bench-scale point-cloud capture of a flume or physical model test rig · Prototype obstacle or clearance sensing for an instrumented monitoring robot on a test bed · Quick 2D distance survey of a lab or enclosed space to check clearances
- Audience llm-inferred
- civils engineers building bench-scale test rigs · hydrologists with physical model or flume setups · GIS analysts processing 2D scan data · robotics and sensor prototyping engineers
Limitations
- Constraints llm-inferred
- 2D sensor only: single scan plane, no 3D point cloud · Requires physical YDLIDAR hardware; no simulation or file replay is described · Quick-install example uses Windows paths and COM ports; other platform setup is not detailed · USB 3.0 recommended for G4/S2 high-rate modes · Web console requires v0.4+ and its feature set is version-dependent · Local install only; no hosted or remote service is described
- Licence
- MIT
- Authentication
- Unknown — review source docs
- GitHub stars
- 3
- Last commit
- 13/10/2026
- Last successful page check
- 14/10/2026
- Page health
- healthy
- Package
- Not recorded
- Verification
- Not independently verified
Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.
Provenance & evidence
Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).
Metadata observed 15/10/2026 · research sweep: github-search