Agentic GIS in Microsoft Copilot with CARTO

CARTO’s guide explains how to connect its Model Context Protocol (MCP) Server to Microsoft Copilot Studio, enabling Copilot agents in Microsoft 365 or Teams to create and edit maps, build and run CARTO Workflows, query spatial data, perform geocoding and routing, locate existing assets, and support platform administration through conversational prompts. Actions run under the authenticated CARTO user’s existing permissions, including row-level security, execute in the organization’s connected data warehouse, and are logged in CARTO Activity Data. Setup involves creating a CARTO SPA OAuth client, manually configuring the MCP tool with OAuth 2.0 in Copilot Studio, adding the generated callback URL, signing in, and publishing the agent; a read-focused API-token option is also available without map or workflow authoring. The guide recommends enabling generative orchestration, disabling dynamic discovery, and optionally providing CARTO Agent Skills to improve geospatial decision-making. Examples show Copilot producing a Chicago transit-access map with cartographic styling and creating an auditable, reusable workflow pipeline, while the integration is presented as a way to broaden access to governed geospatial analysis and reduce reliance on specialist GIS teams.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.