Troubleshooting

A short list of "things that surprised us, so they'll probably surprise you".

The model says it can't find the tool

1. Restart the client. Claude Desktop only re-reads claude_desktop_config.json on launch.
2. Check the command path. Open the JSON config and run the command string by hand. If nix run ... errors, fix it before reopening the client.
3. Tail the client log. macOS: ~/Library/Logs/Claude/. Linux: ~/.config/Claude/logs/.

I get "no points found in collection"

The server only reads features whose geometry.type == "Point". Polygons, lines, and GeometryCollections are ignored. Convert your input to a point set first.

Output looks like one giant cluster

Your eps is too large. Halve it. DBSCAN is sensitive — start narrow and widen.

Output is empty

Your eps is too small or minPts is too large. Try eps = 5000 and minPts = 2 to confirm the pipeline works, then tighten.

The polygon "circles" look squashed

The polygons are drawn in WGS84 lon/lat. Near the poles, a planar regular polygon is no longer a true circle. Re-project to a local equal-area CRS (UTM, Albers, …) in your map client if visual fidelity matters at high latitudes.

I want to know which input point went into which cluster

The current response returns polygons only, not point-to-cluster assignments. Track this in GH issue #1 (we plan to add an assignments mode).

Something else?

Open an issue at github.com/kartoza/kartoza-mcp/issues — include your input GeoJSON (or a redacted slice), the parameters you used, and the response you got back.

Need commercial support?

Kartoza offers paid support, training and bespoke spatial-analytics work. Get in touch via kartoza.com.