Skip to main content

Microsoft Brings MCP to Geospatial Workflows With Planetary Computer Pro Tools for VS Code

Microsoft has added a new set of Model Context Protocol tools to the VS Code Marketplace, and they’re 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 — no context switching, no custom scripts, no specialized API knowledge required.

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.

What It Does

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 — all through natural language prompts.

In practice, that means a developer can type a request like “find Sentinel-2 imagery for this region over the last 90 days,” and the MCP toolset handles the rest — querying the right catalogs, filtering results, and surfacing data without the user needing to know the underlying API structure.

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.

The Problem it Addresses

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.

Working with geospatial data today often requires navigating fragmented tools, managing specialized APIs across systems, and authentication — complexity that slows down workflows and increases the operational burden on teams.

The MCP extension tackles this by consolidating the major workflows — discovery, ingestion, catalog management, and monitoring — into a single interface inside the developer’s existing environment.

Key Capabilities

The toolset covers three primary areas:

STAC Search and Discovery: 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.

GeoCatalog Management: 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 — all through conversational prompts. This eliminates the traditional complexity of API calls and manual configuration.

Data Ingestion: 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 — from a single item to bulk onboarding of entire datasets.

Why it Matters for DevOps Teams

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 — fewer scripts to maintain, fewer manual steps in the pipeline, and faster onboarding for team members who aren’t geospatial specialists.

But it also raises important questions about governance. Mitch Ashley, VP and practice lead for software lifecycle engineering and AI-native software engineering at The Futurum Group, puts it plainly: “MCP 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.”

That’s a critical point. As MCP servers proliferate — each one opening a new connection into production data — access controls and observability can’t be an afterthought. The ease of integration is exactly what makes governance important.

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.

The Microsoft Planetary Computer Pro MCP Tools extension is available now on the VS Code Marketplace. Microsoft’s documentation and a full list of available tools are included on the install page.



from DevOps.com https://ift.tt/B4xOTQs
Labels:

Comments

Post a Comment

Popular posts from this blog

Cursor’s New SDK Turns AI Coding Agents Into Deployable Infrastructure

For most of its life, Cursor has been an IDE. A very good one. But with the public beta of the Cursor SDK, the company is making a different kind of move — one that should get the attention of DevOps teams. The Cursor SDK is a TypeScript library that gives engineers programmatic access to the same runtime, models, and agent harness that power Cursor’s desktop app, CLI, and web interface. In short, the agents that used to live inside an editor can now be invoked from anywhere in your stack. That’s a meaningful shift in how AI coding tools fit into software delivery pipelines. From the Editor to the Pipeline If you’ve used Cursor before, the workflow is familiar — you interact with an agent in real time, asking it to write functions, fix bugs, or review code. The SDK breaks that dependency on interactive use. Now you can call those same agents programmatically, from a CI/CD trigger, a backend service, or embedded inside another tool. Getting started is a single inst...
Post a Comment
Read more

Mistral Moves Coding Agents to the Cloud — and Gets Out of Your Way

For the past year or so, AI coding agents have been tethered to your local machine. You kick off a task, watch the terminal, and babysit every step. It works — but it’s not exactly hands-free. Mistral just changed that. On April 29, the Paris-based AI company announced remote coding agents for its Vibe platform, powered by a new model called Mistral Medium 3.5. The idea is simple: Instead of running coding sessions on your laptop, they now run in the cloud — asynchronously, in parallel, and without you watching over them. What’s Actually New Coding sessions can now work through long tasks while you’re away. Many can run in parallel, and you no longer become the bottleneck at every step the agent takes. That’s the core pitch. You start a task from the Mistral Vibe CLI or directly from Le Chat — Mistral’s AI assistant — and the agent handles the rest. When it’s done, it opens a pull request on GitHub and notifies you, so you review the result inste...
Post a Comment
Read more

GitHub Resets Copilot Pricing as AI Compute Costs Surge

The development community saw this one coming: GitHub will transition its Copilot service to a usage-based billing model on June 1, replacing its existing system of fixed subscriptions supplemented by premium request limits. As reported last week, GitHub suspended new sign-ups for several of its Copilot subscription tiers as it faced a surge in demand from agentic coding workflows. To address that, under GitHub’s new pricing model, customers across individual, business, and enterprise tiers will receive a monthly allocation of AI credits, which are consumed based on token usage. This includes input, output, and cached data processed by underlying models. Once those credits are exhausted, users can purchase additional capacity at published rates. The change leaves base subscription prices intact. Individual plans remain priced at $10 per month for Pro and $39 for Pro+, while business and enterprise tiers continue at $19 and $39 per user per month, respectively. Each plan’s monthly ...
Post a Comment
Read more