Geospatial Agent

Products

Four building blocks. One framework.

From a single MCP server you drop into your existing agent, to a fully branded SaaS deployment we run for you — every layer of the geospatial-AI stack is available standalone or composed.

See the lineup Which is right for me?
MCP
Plug into any agent runtime
A2A
Delegate from your existing agent
Agent
Ship a standalone specialist
SaaS
Branded, customized, hosted
01 · Standalone MCPs

Geospatial superpowers for any agent.

A Model Context Protocol server that exposes a curated toolbelt to any MCP-compatible client — Claude Desktop, Cursor, your own agent runtime, anything that speaks MCP. Drop it in and the host agent gains geospatial execution it couldn't do on its own.

Talk to us about an MCP Read the docs
Featured MCP

geeViz MCP

The full Earth Engine + geeViz toolbelt as one MCP server. Used inside AskTerra. Available standalone.

stdio · streamable_http

12 tools

  • run_codeSandboxed Python REPL pre-loaded with ee, Map, gv, gil, sal, cl. State persists across turns.
  • search_geevizSearch the geeViz library + example catalog by name, module, or query.
  • search_datasetsFind Earth Engine datasets by keyword across the entire catalog.
  • inspect_assetGet real band names, dtypes, and class properties for any EE asset.
  • map_controlAdd layers, set viz params, switch basemaps, center on AOIs.
  • export_imageRender publication-ready thumbnails with legends, scale bars, GIFs, filmstrips.
  • save_session / view_outputPersistent session state. Stable artifact URLs.
  • geeviz_search_places / get_streetviewPlace lookup + Street View when wired to a Maps key.
  • manage_assetList, copy, and delete assets in your EE project.
  • env_infoIntrospect the current REPL's variables, modules, and active credentials.

Works with Claude Desktop, Cursor, Cline, ChatGPT custom GPTs, and any MCP-compliant host. Both local subprocess and remote HTTP transports.

Your own MCP? We build them. Domain-specific tools wrapped in MCP — in-house GIS feeds, proprietary analytics, third-party APIs — deployed standalone or bundled into your tenant.

02 · A2A connectors

Wire your existing agent to a geospatial specialist.

Already have a corporate agent? Don't replace it — extend it. An Agent-to-Agent connector exposes our geospatial agent as a remote skill your existing agent can call: ask_terra(question) goes out, a rich geospatial answer comes back.

Get an A2A endpoint Read the docs
A2A endpoint

AskTerra Geospatial Agent

Your existing agent (any framework) delegates geospatial questions to a hosted endpoint and renders the artifacts back into its own chat.

HTTPS · JSON-RPC

What you get

  • ask_terra(question)One tool the host agent calls. Plain-English geospatial question in. Structured answer + artifact URLs out.
  • Artifact URLsStable links to maps, charts, thumbnails, and reports rendered on our infrastructure — embeddable in your UI.
  • Per-tenant attributionEvery call carries your customer ID. Per-user usage reports. Per-user billing if you want it.
  • StreamingSubscribe to in-flight tool calls and partial results so your UI can show progress.
  • Tenant isolationYour customers' sessions, scripts, and artifacts are scoped to your tenant. No cross-talk.
  • Framework-agnosticWorks with Google ADK, LangGraph, AutoGen, CrewAI, Bedrock Agents — anything that can call a tool.

Two minutes to integrate. Add one tool definition pointing at our endpoint with your API key. Your agent learns to use it from the tool description.

03 · Standalone agents

A specialist your team can talk to today.

A complete, hosted geospatial agent with a chat UI, session memory, saved scripts, and artifact storage. Not a framework you build on — a product your analysts and operators sign in to and use.

Try AskTerra User docs
Reference agent

AskTerra Geospatial Agent

A turnkey conversational geospatial analyst built on the framework, operated by RedCastle Resources.

Hosted

What's in the box

  • Conversational chatPlain-English geospatial questions. Real maps, charts, time-lapses, and reports back.
  • Session memoryYour study area, dates, and intermediate variables persist across turns.
  • Saved scriptsPromote any working analysis to a parameterized script your team re-runs without an LLM.
  • Artifact libraryEvery output is a stable URL. Sharing a map is sharing a link.
  • Reports + exportsMulti-section HTML reports. CSV / GeoJSON / GeoTIFF exports. Email-ready.
  • Access policyWorkspace allowlist. Group-based access via Cloud Identity. Per-user attribution.

Get a team account in days, not months. Pricing is per-seat with included Earth Engine compute attribution.

04 · Customizable SaaS

Your branded geospatial agent. On your domain. With your data.

The full multi-tenant framework powering AskTerra — deployed under your brand, on your URL, with your data sources wired in. We operate it. You sell it.

Talk to us about a deployment Architecture docs
Reference deployment

The AskTerra Framework

AskTerra is one tenant of this framework. Yours would be another — same engine, your brand, your data, your access policy.

One YAML

What you get

  • Your brandLogos, fonts, dark + light palettes, hero copy, footer attribution — all from tenant.yaml.
  • Your domainCustom URL with managed TLS. Cloud Run hosting in your own GCP project, or ours.
  • Your toolsYour in-house MCP servers, Python tools, A2A connectors. All declared in YAML.
  • Your agent topologySingle agent, multi-agent, sub-agents, hierarchies — all configuration.
  • Your access policyAllowlist emails or Workspace groups. Manage in Workspace, no redeploy.
  • Your data isolationOwn BigQuery dataset, Cloud SQL, GCS bucket, Secret Manager. Per-tenant logging.
  • Production-readyModel Armor screening, per-user EE workload tags, signed sessions, audit logs.
  • Setup wizardEnd-to-end scaffold of GCP project, APIs, IAM, BigQuery, OAuth client. Idempotent.

A new tenant deploys in days. Most operators only edit ~30 lines of YAML for a baseline.

Which product is right for you?

Pick by where you are in your build.

If you... Start with Then consider
...already run an agent and want it to do geospatial things Standalone MCP (the geeViz MCP) A2A if you want a hosted specialist instead of a local subprocess
...want a hosted geospatial brain your corporate agent can delegate to A2A connector Custom MCP if you also want some tools locally in your runtime
...want your team to use a chat UI today, not build infrastructure Standalone agent (AskTerra) Customizable SaaS once you outgrow shared branding
...want a branded product on your domain, for your customers or org Customizable SaaS Wire in MCP + A2A connectors as your tool surface grows
...are an ISV, agency, or domain SaaS adding geospatial as a feature A2A connector Customizable SaaS for a co-branded chat UI alongside your product
...are a research lab or university group Standalone agent (free tier on AskTerra) MCP + saved scripts if your students need reproducible analyses

How we work

From scoping call to live deployment.

1

Scoping call

What you want to do, who's using it, what data, what compliance bar. 45 minutes.

2

Tooling spec

We map your use cases to MCPs, sub-agents, A2A connectors, and tenant config.

3

Build & verify

We stand up your tenant on a staging URL. You sign in and run real analyses.

4

Go live

Custom domain, production access policy, monitoring. We operate it ongoing.

Tell us what you're building.

Bring your use case — field, sector, region, data sources. We'll show you which combination of MCP, A2A, agent, and SaaS fits.

Book a scoping call Try the reference agent Read about the framework
Docs Privacy Terms EULA Powered by RedCastle ResourcesRedCastle Resources + geeVizgeeViz + Google Earth EngineGoogle Earth Engine + Google GeminiGoogle Gemini