WildDatum MCP server

WildDatum

WildDatum is a local-first ecological data workbench exposed as a standard Model Context Protocol server. It lets Codex, Claude, and other MCP agents discover, materialize, query, visualize, select, and cite scientific data without putting credentials, private paths, or millions of rows into model context.

NEON plus public ERDDAP services from EMSO ERIC, ICOS Carbon Portal, and Euro-Argo/Ifremer are built-in remote providers. Local tabular, raster, vector, point-cloud, image, hyperspectral, and N-dimensional array sources use the same provider-independent manifest, query, view, selection, and provenance model.

“Compare this NEON LiDAR tile with its hyperspectral cube. Show them together,

let me select an individual return or image pixel, then query the exact source

point or spectrum behind my selection.”

A real WildDatum browser session using Rerun Web Viewer: a 6.6-million-point NEON LAS tile, a 500×500×107 reflectance cube, immutable provenance, and a verified selection mapped back to LAS source row 2,543,044.

<!-- mcp-name: io.github.krnzt/wilddatum -->

The human–agent loop

scientific question
    → discover products, sites, and local assets
    → construct and approve a reproducible data plan
    → materialize immutable, checksum-verified sources
    → query and render a bounded multimodal Rerun view
    → human clicks, brushes, filters, or selects
    → WildDatum records that interaction as scientific state
    → agent queries the exact selected source data
    → export results, transformations, provenance, and citation

The visualization is not just a picture for the model to inspect. EcoViewSpec is authoritative view state and SemanticSelection is authoritative interaction state. A Rerun recording is a regenerable rendering artifact. For verified WildDatum point batches, an instance pick maps back to an exact LAS/LAZ source row; for a mapped cube, an image click maps back to the complete source spectrum. For linked trajectories and vertical profiles, a map or profile point maps back to the exact physical CSV/TSV, Parquet, or Arrow record, including provider-native QC values.

What works in the alpha

materialization, checksum, release, license, and citation handling.

• A normal MCP 2026-07-28 stdio server registerable with Codex and Claude Code.
• Public NEON catalog discovery plus reproducible plan, approval, background

tabledap/griddap subsets, redirect-aware approval, streaming materialization, license, citation, and live-source provenance.

• Public EMSO, ICOS ERDDAP, and Euro-Argo catalog discovery plus validated

dataset IDs.

• Out-of-band local imports with streaming fingerprints and opaque agent-facing

reads, and bounded HDF5/NetCDF/Zarr N-dimensional slices.

• Arrow/DataFusion tabular queries, spatial raster/vector queries, indexed COPC

mapped scientific cubes, and linked geographic trajectories/vertical profiles.

• Native and browser Rerun views for tables, images, GeoTIFFs, vectors, LiDAR,

queries and exported as CSV, Parquet, COG, or RO-Crate where applicable.

• Durable human selections that can be converted into provenance-linked source

JSON-RPC contract; an RI contributor can work in Rust, Python, R, Go, or another language without adding provider-specific MCP tools.

• Language-neutral community provider subprocesses with a provider-neutral v2

Alpha.3: linked scientific views

Shortened. The full README is on GitHub.