{"id":4190,"date":"2026-06-01T08:12:45","date_gmt":"2026-06-01T08:12:45","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/06\/01\/microsoft-brings-mcp-to-geospatial-workflows-with-planetary-computer-pro-tools-for-vs-code\/"},"modified":"2026-06-01T08:12:45","modified_gmt":"2026-06-01T08:12:45","slug":"microsoft-brings-mcp-to-geospatial-workflows-with-planetary-computer-pro-tools-for-vs-code","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/06\/01\/microsoft-brings-mcp-to-geospatial-workflows-with-planetary-computer-pro-tools-for-vs-code\/","title":{"rendered":"Microsoft Brings MCP to Geospatial Workflows With Planetary Computer Pro Tools for VS Code"},"content":{"rendered":"<div><img data-opt-id=167803525  fetchpriority=\"high\" decoding=\"async\" width=\"770\" height=\"330\" src=\"https:\/\/devops.com\/wp-content\/uploads\/2026\/05\/Untitled-design-21.jpg\" class=\"attachment-large size-large wp-post-image\" alt=\"\" \/><\/div>\n<p><img data-opt-id=1872890953  fetchpriority=\"high\" decoding=\"async\" width=\"150\" height=\"150\" src=\"https:\/\/devops.com\/wp-content\/uploads\/2026\/05\/Untitled-design-21-150x150.jpg\" class=\"attachment-thumbnail size-thumbnail wp-post-image\" alt=\"\" \/><\/p>\n<p><span>Microsoft has added a new set of Model Context Protocol tools to the VS Code Marketplace, and they\u2019re aimed squarely at developers and data engineers working with geospatial data. The Microsoft Planetary Computer Pro MCP Tools extension provides natural-language-driven access to geospatial workflows directly in Visual Studio Code \u2014 no context switching, no custom scripts, no specialized API knowledge required.<\/span><\/p>\n<p><span>The extension is now available on the VS Code Marketplace, and it marks a meaningful step in how teams interact with large-scale environmental and geospatial datasets.<\/span><\/p>\n<h3><span>What It Does<\/span><\/h3>\n<p><span>The extension integrates directly with GitHub Copilot in VS Code, exposing 35+ tools that connect to both Microsoft Planetary Computer and Planetary Computer Pro. Through those tools, users can perform data ingestion, STAC search, GeoCatalog management, visualization, and ingestion monitoring \u2014 all through natural language prompts.<\/span><\/p>\n<p><span>In practice, that means a developer can type a request like \u201cfind Sentinel-2 imagery for this region over the last 90 days,\u201d and the MCP toolset handles the rest \u2014 querying the right catalogs, filtering results, and surfacing data without the user needing to know the underlying API structure.<\/span><\/p>\n<p><span>Users can describe tasks conversationally, such as querying geospatial imagery, ingesting data, analyzing regions, or preparing datasets, and MCP translates those prompts into executable geospatial operations. This eliminates the need to write code or switch between tools, enabling faster iteration and tighter developer workflows.<\/span><\/p>\n<h3><span>The Problem it Addresses<\/span><\/h3>\n<p><span>Anyone who has worked with geospatial data pipelines knows the friction involved. Data lives across fragmented systems. APIs are specialized and require careful handling. Authentication flows add overhead. And stitching it all together typically requires custom code that has to be maintained over time.<\/span><\/p>\n<p><span>Working with geospatial data today often requires navigating fragmented tools, managing specialized APIs across systems, and authentication \u2014 complexity that slows down workflows and increases the operational burden on teams.<\/span><\/p>\n<p><span>The MCP extension tackles this by consolidating the major workflows \u2014 discovery, ingestion, catalog management, and monitoring \u2014 into a single interface inside the developer\u2019s existing environment.<\/span><\/p>\n<h3><span>Key Capabilities<\/span><\/h3>\n<p><span>The toolset covers three primary areas:<\/span><\/p>\n<p><i><span><strong>STAC Search and Discovery<\/strong>:<\/span><\/i><span> Users can search for data from an area of interest through an interactive map, spanning both Planetary Computer public datasets and Planetary Computer Pro GeoCatalog private datasets, enabling fast discovery of data across space, time, and metadata.<\/span><\/p>\n<p><i><span><strong>GeoCatalog Management<\/strong>:<\/span><\/i><span> Users can create, configure, and manage STAC collections, move datasets from Planetary Computer, define rendering options like natural color or NDVI, and set up mosaics or thumbnails \u2014 all through conversational prompts. This eliminates the traditional complexity of API calls and manual configuration.<\/span><\/p>\n<p><i><span><strong>Data Ingestion<\/strong>:<\/span><\/i><span> Data ingestion, often one of the most complex and time-consuming steps, becomes more manageable with MCP. Users can ingest data from Planetary Computer collections using simple prompts, with MCP handling the orchestration, monitoring, and status tracking of ingestion workflows \u2014 from a single item to bulk onboarding of entire datasets.<\/span><\/p>\n<h3><span>Why it Matters for DevOps Teams<\/span><\/h3>\n<p><span>The Planetary Computer Pro MCP extension is a clear signal that the MCP ecosystem is expanding beyond general developer tooling into domain-specific workflows. For DevOps teams supporting GeoAI and data engineering pipelines, this kind of integration reduces the operational surface area \u2014 fewer scripts to maintain, fewer manual steps in the pipeline, and faster onboarding for team members who aren\u2019t geospatial specialists.<\/span><\/p>\n<p><span>But it also raises important questions about governance. Mitch Ashley, VP and practice lead for software lifecycle engineering and AI-native software engineering at <a href=\"https:\/\/futurumgroup.com\/\" target=\"_blank\" rel=\"noopener\">The Futurum Group<\/a>, puts it plainly: \u201cMCP is consolidating into the connective layer between AI agents and specialized backend systems, and this release elevates the protocol for use in domain-specific workflows. The protocol is becoming infrastructure rather than a convenience for agents. Every MCP server that an agent can reach opens a new path into production systems and data. Teams adopting these integrations must govern what agents query, ingest, and act on, because the integration surface is now a control and access concern.\u201d<\/span><\/p>\n<p><span>That\u2019s a critical point. As MCP servers proliferate \u2014 each one opening a new connection into production data \u2014 access controls and observability can\u2019t be an afterthought. The ease of integration is exactly what makes governance important.<\/span><\/p>\n<p><span>As geospatial workloads continue to grow in scale and importance, simplifying access to these capabilities becomes critical. MCP enables Planetary Computer Pro users to move faster, lower barriers to entry, and unlock the full value of the platform without needing deep expertise in underlying systems or building special connectors to access various tools.<\/span><\/p>\n<p><span>The Microsoft Planetary Computer Pro MCP Tools extension is available now on the<\/span><a href=\"https:\/\/marketplace.visualstudio.com\/items?itemName=ms-planetarycomputer.mpc-pro-mcp-tools\" target=\"_blank\" rel=\"noopener\"> <span>VS Code Marketplace<\/span><\/a><span>. Microsoft\u2019s documentation and a full list of available tools are included on the install page.<\/span><\/p>\n<p><a href=\"https:\/\/devops.com\/microsoft-brings-mcp-to-geospatial-workflows-with-planetary-computer-pro-tools-for-vs-code\/\" target=\"_blank\" class=\"feedzy-rss-link-icon\">Read More<\/a><\/p>\n<p>\u200b<\/p>","protected":false},"excerpt":{"rendered":"<p>Microsoft has added a new set of Model Context Protocol tools to the VS Code Marketplace, and they\u2019re aimed squarely [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4191,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[5],"tags":[],"class_list":["post-4190","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/4190","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/comments?post=4190"}],"version-history":[{"count":0,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/posts\/4190\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/media\/4191"}],"wp:attachment":[{"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/media?parent=4190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/categories?post=4190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/wp-json\/wp\/v2\/tags?post=4190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}