GIS Cloud

Read, create, edit and delete maps, layers, features and field forms in GIS Cloud.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the GIS Cloud connector does

The GIS Cloud MCP server connects a GIS Cloud account — a cloud GIS platform for maps, spatial data and field data collection — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 55 tools that read, create, edit and delete maps, layers, features, tables and Mobile Data Collection forms. Sign-in is OAuth, with a read-only option at consent.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

GIS Cloud tools (55)

  • add_table_columns
  • bind_form_to_layer
  • bulk_update_features
  • create_bookmark
  • create_feature
  • create_form
  • create_layer
  • create_map
  • create_table
  • create_table_row
  • delete_bookmark
  • delete_feature
  • delete_file
  • delete_form
  • delete_layer
  • delete_map
  • delete_table
  • delete_table_row
  • get_attribute_stats
  • get_bookmark
  • get_current_user
  • get_datasource
  • get_feature
  • get_form
  • get_layer
  • get_layer_columns
  • get_map
  • get_table
  • import_file
  • list_basemaps
  • list_bookmarks
  • list_datasources
  • list_dbconnections
  • list_features
  • list_files
  • list_forms
  • list_layers
  • list_maps
  • list_table_rows
  • list_tables
  • make_directory
  • query_read
  • query_write
  • read_file
  • refresh_access_token
  • render_map
  • unzip_file
  • update_bookmark
  • update_feature
  • update_form
  • update_layer
  • update_map
  • update_table_row
  • upload_binary_file
  • upload_file

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The one OAuth scope is a wildcard. Both the server's RFC 9728 resource descriptor and its authorization server metadata advertise scopes_supported: ["mcp"] and nothing else. A scope naming no object and no verb cannot exclude anything: granting it grants whatever the server implements, now and later. The read-only choice GIS Cloud offers at consent is a real control, but it is enforced by GIS Cloud's own permission model, not by the OAuth grant.
  • query_write makes the verb census incomplete. SQL forwarded to PostGIS reaches operations no tool name describes. Do not read "8 delete tools" as a bound on destructive reach.
  • The vendor enumerates families, not tool names. Every name matched semantically, none literally, so a rename between the directory and the server would be invisible to this diff.
  • Truncate, reports and select appear in the vendor's own description with no tool name behind them. Truncate is destructive, which is exactly where an omission matters most.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here — including whether update_map can reach a sharing property.
  • The two-step confirmation is documented, not observed. Verifying it would mean invoking a destructive tool. We did not.
  • This connector ships an MCP app widget. Anthropic's directory sets has_mcp_app: true for GIS Cloud. A widget runs in the user's browser and acts on the user's click, so no tool audit reaches it. We did not fetch or test it, and its behaviour is unknown.
  • The RFC 9728 path is a catch-all. Every suffix under /.well-known/oauth-protected-resource/ returned a byte-identical document, including a deliberately bogus control path. The document names the correct resource, so the scope finding stands, but the path is not path-specific.
  • refresh_access_token is classified as a write here because it mutates session state. It does not touch geospatial data, so treat the 23-write figure as including one session-management tool.
  • Personal data is inseparable from the map data. Collector identity and GNSS attributes sit in ordinary layer columns, so a read-only connection still exposes them to any feature query.

Frequently asked questions

Can the GIS Cloud connector delete a map or a layer?

Yes. Eight of the 55 tools carry a delete verb, including delete_map, delete_layer, delete_feature and delete_table. GIS Cloud documents a two-step confirmation for destructive actions, where the first call returns a plain-language summary such as the layer name and its feature count, and nothing changes until you approve it. We could not verify that gate on the wire.

Can the GIS Cloud MCP server publish a map publicly?

No tool in the listing does. GIS Cloud makes a map public by granting read permission to the anonymous user, which is the permissions endpoint on the REST API. No tool among the 55 names a permission, share, public or anonymous operation, so the publish boundary falls outside the connector's tool surface. That is a real boundary, not an inferred one.

Can the GIS Cloud connector read location data about the people who collected it?

Yes, wherever a form was built with them. GIS Cloud documents hidden form items, invisible to the collector, that automatically record the collector's Username, Latitude, Longitude, Altitude, Speed, GPS Heading, Accuracy, Device ID and time on every submission. These land in ordinary layer columns, which list_features and query_read return like any other attribute.

How many tools does the GIS Cloud MCP server have?

Anthropic's directory lists 55 on 2026-08-23. Our split of those names is 24 read, 23 write and 8 delete. The count understates the reachable surface, because query_write forwards SQL to the underlying PostGIS database, and the operations SQL reaches are not bounded by any tool name in the list.

What OAuth scopes does the GIS Cloud MCP server request?

Exactly one, named mcp. The server's RFC 9728 descriptor and its authorization server metadata both advertise that single scope. It names no object and no verb, so it is a wildcard that cannot exclude anything. GIS Cloud's own documentation describes a read-only or read-and-write choice on the consent screen, which is a separate control from the OAuth scope.

Can the GIS Cloud connector overwrite field-collected data?

Yes. bulk_update_features updates many features in one call, update_feature changes one, and query_write forwards SQL that can rewrite rows directly. Field-collected records are often irreplaceable, since re-collection means sending a crew back. GIS Cloud flags bulk updates as destructive and gates them behind its confirmation step.

Does GIS Cloud publish its own list of MCP tools?

It publishes capability families, not tool names. GIS Cloud's AI Connectors article groups the surface into maps, layers, features, tables, forms, queries, files, bookmarks and account. Every family maps onto directory tool names, but the article also names truncate, select and reports, and no tool in the listing carries those verbs.

What happens if I connect GIS Cloud with read-only permission?

GIS Cloud states the assistant inherits exactly your permissions and that read is the baseline, with writing and deleting gated at authorisation. Choosing read-only at the consent screen is the strongest control available here, because the single mcp OAuth scope does not separate reading from writing on its own.

Sources

More Analytics connectors

  • Aleph

    Query live FP&A data, build reports and update dashboards from your AI assistant.

  • august

    Interview simulated customer twins, run focus groups and surveys from an AI agent.

  • ChartMogul

    Query MRR, ARR, churn, retention, cohorts, customers and sales pipeline from your AI assistant.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put GIS Cloud to work.

Connect GIS Cloud once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.