GeoD Global
English

GEOD × YOUR AGENT

Connect your Agent
to real local data.

The desktop, CLI, and local MCP adapter share one execution core. Connect a compatible Agent client to inspect your data, review a plan, and track the actual result.

Request early accessRead the MCP reference

Development integration · Local MCP client required. Write tools are enabled explicitly.

Your Agent client

Compatible local MCP host

GeoD MCP adapter

Local stdio connection

GeoD execution core

Persisted jobs, projects, and files

A workflow you can inspect.

Give the Agent a specific task, then review the source, the plan, and the saved result. The example below uses a supported local Sentinel-2 scene classification layer (SCL).

  1. Inspect the source and its pixels

    Inspect the raster's CRS, dimensions, checksum, and original pixel values. Pin the recipe to the exact source job and checksum.

    geod_raster_inspect · geod_raster_pixel

  2. Review the pixel-aligned crop plan

    Review output dimensions, crop bounds, and warnings before a task is created.

    geod_recipe_plan

  3. Run with writes enabled and wait for completion

    Write tools require explicit startup configuration. After running the recipe, wait until the task succeeds and its worker has settled.

    geod_recipe_run → geod_job_status
    status = succeeded · settled = true

  4. Inspect the saved GeoTIFF result

    Inspect the completed file and sample its pixels. Keep the output linked to its source and recipe.

    geod_raster_inspect · geod_raster_pixel

Tools with useful, visible outcomes.

  • Jobs and projects

    Read persisted task states and project records; follow the same job through completion.

    geod_jobs_list · geod_job_status · geod_projects_list
  • Raster inspection and recipes

    Read real pixels and preview a supported recipe's output grid before running it.

    geod_raster_inspect · geod_raster_pixel · geod_recipe_plan
  • Saved WCS coverage

    Inspect saved coverage descriptions, plans, and original samples from completed local files.

    geod_wcs_plan · geod_wcs_inspect · geod_wcs_pixel
  • Explicitly enabled tasks

    Run supported recipes, download supported files, or cancel and retry jobs when write tools are enabled.

    geod_recipe_run · geod_download · geod_job_cancel

Two ways to connect.

Use the development runtime built from source. Configure its executable path in a compatible MCP client, then choose one connection mode.

Use an existing local service

Start the local GeoD service first, then connect its loopback address. The service owns the jobs, so they can continue after the Agent session closes.

geod-runtime serve-mcp --server http://127.0.0.1:4318

Use a separate local workspace

A standalone MCP process owns its data directory. Use a directory that is not already open in the desktop or another process, and keep the session open until jobs settle.

geod-runtime serve-mcp --data-dir ./geod-agent-data

Add the following startup flag only when you want to enable write tools.

--allow-write

Through a local MCP adapter in a compatible client. The integration uses GeoD's runtime; it does not automatically control an open desktop window.

Current scope

The current MCP recipe runner clips supported single-band Sentinel-2 SCL rasters. Other operations and provider access depend on their own verified scope.

SCL contains scene classification codes. It is not a land-cover classification product. General GIS analysis and reprojection require other tools.

Files stay in the local GeoD workspace. Tool results can include file paths, metadata, and coordinates; any onward handling depends on the Agent client's configuration.

Read the MCP referenceReview all data and access requirements