The two location tools are the reason to install it: one question about a place comes back as an ordered stratigraphic history — basement, then each formation with its age range and depositional setting — rather than as a link to a map. The definitions tools matter more than they look, because geological queries fail on vocabulary; resolving the term first is what makes the unit lookup return the right thing. The map tiles are the weakest part and the author says so.
A client for the Macrostrat API — the geological database of stratigraphic columns, rock units, minerals and the geologic timescale. Eight tools, all reads, over a free and public API.
- Stratigraphic columns for any location worldwide — the layered geological history under a point, which is what a question about bedrock or age dating actually resolves to (find-columns).
- The rock units themselves: formations, lithology, mineral content and ages for a location, in a short or long response shape (find-units).
- The controlled vocabularies Macrostrat is built on, so a query uses the terms the database actually holds, plus a fast autocomplete over all definitions capped at 100 results (defs, defs-autocomplete).
- Information about a named mineral, looked up by one property (mineral-info).
- The geologic timescale, so a period name resolves to its bounds (timescale).
- Geological map tiles: convert a latitude and longitude to web-mercator tile x and y for a zoom level, then get the tile URLs from Macrostrat's tile server, defaulting to the carto scale that adapts detail to zoom (lat-lng-to-tile, map-tiles).
Node.js 20 or newer, and nothing else — `npx -y macrostrat-mcp` over stdio, with no API key because the Macrostrat API is free and public.
One command — npx -y macrostrat-mcp