Flagship Release

ForgeGIS

GPU-Accelerated Geospatial Compute for the Agent Era

As of May 2026, the only commercially-supported GPU-accelerated geospatial MCP server we have been able to identify. Distributed as pure-Java Maven artifacts — no first-party native code, no GDAL native bindings, no separate native install step. 220 user-facing operations across 11 geospatial categories; 218 callable by AI agents through a native Model Context Protocol server.

220 / 11
user-facing operations across 11 geospatial categories
218 / 220
operations callable by AI agents via the native MCP server
14×–40×
multi-stage pipeline speedup vs GDAL CLI on equivalent workloads

What it is, why it matters, how it's built differently

Three short answers for the technical evaluator.

What it is

ForgeGIS is a GPU-accelerated geospatial compute library and a native Model Context Protocol server, both written in Java. It runs raster, vector, hydrology, visibility, spectral, ML, and point-cloud workloads on the GPU through Java-side compute kernels — and exposes 218 of its 220 operations to AI agents through MCP.

Why it matters

Serious geospatial work has historically meant assembling Python, C++, and native libraries — GDAL, JTS, PostGIS, CUDA — and accepting either CPU-bound throughput or a build pipeline tied to native dependencies. ForgeGIS removes both costs: GPU performance without leaving the JVM, and agent-callable surface without an integration layer.

How it's built differently

Pure-Java Maven distribution. No first-party native code, no GDAL native bindings, no separate native install step. GPU dispatch is via the JOCL OpenCL bindings (JNI bridge bundled in the JOCL JAR, extracted at runtime); the system OpenCL runtime is standard system software bundled with GPU drivers. Deployment is one JAR.

Dual-surface architecture

One library, two surfaces — one designed for agent composition, one for typed single calls.

The MCP server (forgegis-mcp) exposes ForgeGIS through two complementary surfaces, so an AI agent can either compose a multi-stage workflow in a single call or invoke a specific operation directly with typed inputs.

Surface 1 — Pipeline DSL
133 operations

Composable JSON pipeline format. Agents assemble multi-stage workflows (read → reproject → mask → classify → write) inside a single MCP call.

Surface 2 — Typed Intent Tools
54 single-call tools

Strongly-typed MCP tools for the most common operations. One MCP tool per intent, with structured inputs and validated arguments.

62 MCP tools total · 218 of 220 catalog operations reachable from an agent

Performance highlights

Benchmarked against GDAL CLI on equivalent workloads. Numbers are summary — full methodology, dataset descriptions, and per-operation timings live in the Technical Brief.

Full methodology, hardware configuration, and per-operation breakdowns: ForgeGIS Technical Brief (PDF).

Who it's for

Three audiences, three one-pagers. Each leads with the parts of ForgeGIS that matter most to that reader.

Capability catalog

220 operations across 11 categories. The full catalog with operation-level descriptions is in the Technical Brief.

Terrain14
Bathymetry / Ocean14
Hydrology7
Visibility / RF8
Spectral / ML30
Spatial Geometry80
Filtering / Focal / Morphology14
Raster Mgmt / Vectorize / IO39
Routing7
Point Cloud5
Temporal2
Topology completeness. The Spatial Geometry category includes full DE-9IM coverage: the 8 OGC named predicates, 3 JTS extensions, the Relate operation, and the raw 9-character intersection matrix per geometry-type pair. Few GPU libraries surface the full DE-9IM relate matrix — most stop at named predicates.

Downloads

All ForgeGIS collateral. Direct download — no email gate, no form wall.

Talk to us about ForgeGIS

Licensing questions, evaluation access, partnership inquiries — we read every email.

rich@seaglassfoundry.com