What changed. And where to read about it.
A focused log of the most recent capabilities added to the engine, each linked back to the feature page that documents the protocols, boundaries and integration seams behind it.
Four additions that change the operating model.
Dates reflect the release in which each capability landed in the shared backend. Validate any capability against your evaluated build before relying on it for production.
-
Aug 2026
Event-driven data with DuckDB triggers
Author SQL predicates against attached
.gpkg/.sqlite/.duckdbfiles and fire alerts the moment rows match. The DuckDBeventsextension re-evaluates rules on each commit for near-instant detection, with a 5-second poll fallback when the extension is unavailable. Two trigger types: data-content rules (carry the matched payload) and lifecycle events (raw database activity into the feed). -
Aug 2026
MCP Server Wizard and preset catalog
A guided wizard with one-click presets for the common open-source MCP servers—QGIS (socket), ArcGIS Pro (stdio), the Filesystem and Git reference servers, GitHub, and
duckdb_mcp. Pick a preset, edit the pre-filled fields, and connect; tools surface undermcp:<server>:<tool>. All three transports (socket, HTTP, stdio) are supported, with absolute-path commands rejected by default. -
Aug 2026
Async COPY TO cloud filesystems
The bundled DuckDB
cloudfsextension lets the server write query results straight to SharePoint, OneDrive, Google Drive, Dropbox, SFTP or a VPS—no separate sync pipeline. Exports run as tracked, cancellable async jobs and can emit GeoPackage, GeoParquet, CSV/JSON or a styled bundle per consumer. -
Aug 2026
Secure multi-user web platform
The server build becomes an ArcGIS-Enterprise-style platform: cookie-session auth (httpOnly, SameSite=Strict) that secures JSON APIs and tile/image URLs, optional OIDC SSO, a Portal app registry with URL slugs and sharing levels, a sandboxed file manager, and a WebDAV mount. All wiring is behind
//go:build server; desktop builds are byte-identical and unaffected.
Platform foundations already in place.
These capabilities shipped in prior cycles and underpin the new work above.
-
Jul 2026
Dynamic MVT and remote-COG ImageServer
View-dependent Mapbox Vector Tiles generated from live DuckDB spatial queries, and remote Cloud Optimized GeoTIFFs exposed as an Esri-compatible ImageServer via byte-range reads—both keeping the authoritative source in open storage.
-
Jul 2026
GeoAgent and bidirectional MCP
Natural-language execution against the governed capability catalog, plus an opt-in authenticated MCP server (external AI calling in) and an MCP client (GeoAgent calling out to QGIS/ArcGIS tools).
-
Jun 2026
Production deployment assets
Helm chart and Kubernetes manifests, reusable Terraform modules for EKS/AKS/GKE, GitHub and GitLab release pipelines, multi-architecture images, SBOMs, signing and checksums.
Compatibility is a migration strategy, not a claim of vendor affiliation.
3DGeoServEngine implements and consumes documented service patterns so existing GIS clients and applications can transition incrementally. Every capability listed here should be validated against your organization’s actual layers, editing workflows, renderers, security rules and extensions before production reliance.
Try 3DGeoServEngine in the browser—no sign-in required.
3DGeoServEngine is a web platform. There is no Windows GeoServEngine installer. Open the hosted web client for dynamic MVT, imagery and FMV exploitation, live feeds, GeoAgent, and the service plane. Want a native desktop app for Windows, macOS, or Linux? That is Field Sentinel.