3,400+ MCP servers ready to use
Vinkius

Copernicus Data Space MCP Server for VS Code CopilotGive VS Code Copilot instant access to 14 tools to Check Copernicus Status, Count Products, Get Collection, and more

Built by Vinkius GDPR 14 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Ask AI about this App Connector for VS Code Copilot

The Copernicus Data Space app connector for VS Code Copilot is a standout in the The Unthinkable category — giving your AI agent 14 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Copernicus Data Space and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "copernicus-data-space": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Copernicus Data Space
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Copernicus Data Space MCP Server

Connect to the Copernicus Data Space Ecosystem and unlock the world's largest open Earth observation archive directly from your AI agent.

GitHub Copilot Agent mode brings Copernicus Data Space data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 14 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Product Discovery — Search across Sentinel-1 (radar), Sentinel-2 (optical), Sentinel-3 (ocean/land), Sentinel-5P (atmosphere), and Sentinel-6 (altimetry) collections with temporal, spatial, and attribute filters
  • Geographic Search — Find satellite products covering any location on Earth using bounding box coordinates or WKT polygon geometries
  • Orbit-Based Queries — Retrieve data from specific satellite orbits for interferometry, change detection, and repeat-pass analysis
  • Product Inspection — Access complete metadata, quicklook previews, and internal file structure for any product
  • Download Orchestration — Generate authenticated download URLs with time-limited Bearer tokens for direct product retrieval
  • Data Volume Assessment — Count products matching your criteria before executing full searches

The Copernicus Data Space MCP Server exposes 14 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 14 Copernicus Data Space tools available for VS Code Copilot

When VS Code Copilot connects to Copernicus Data Space through Vinkius, your AI agent gets direct access to every tool listed below — spanning satellite-imagery, geospatial-analysis, earth-observation, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

check_copernicus_status

Returns the connection status. Use this to verify your client_id:client_secret credentials are working correctly. Verify Copernicus Data Space API connectivity and authentication

count_products

Useful for understanding data volume before executing a full search, or for monitoring data availability trends. Count total products available for a collection and date range

get_collection

Use collection names like "SENTINEL-2", "SENTINEL-1", or "SENTINEL-3". Get details about a specific Copernicus collection

get_product

Returns name, sensing time, footprint geometry, file size, checksum, and all associated attributes. Use this after searching to inspect a specific product before downloading. Get detailed metadata for a specific satellite product by UUID

get_product_download_url

Returns the direct download URL along with a Bearer token valid for approximately one hour. Use this to download raw satellite data products (typically in SAFE format for Sentinel data). Generate an authenticated download URL for a product

get_quicklook

Useful for understanding the product structure and accessing thumbnail previews without downloading the full product. Get quicklook preview and file nodes for a product

list_attributes

This helps you understand what filtering parameters are available (e.g., cloud cover percentage, orbit direction, processing level) for refining product searches. List available metadata attributes for a collection

list_collections

Includes Sentinel-1 (radar), Sentinel-2 (optical), Sentinel-3 (ocean/land), Sentinel-5P (atmosphere), Sentinel-6 (altimetry), and complementary missions like Landsat. Each entry includes temporal coverage and description. List all available Copernicus satellite data collections

list_latest_products

Useful for monitoring new data availability or checking processing pipeline status. List the most recently published satellite products

list_product_nodes

Returns the hierarchy of files including measurement data, metadata XML, quicklook images, and auxiliary data. Essential for understanding product structure before selective download. List all files contained within a satellite product

search_by_bbox

Combines spatial filtering with collection and temporal constraints. Ideal for region-specific analysis workflows. Search satellite products within a geographic bounding box

search_by_name

Useful for finding specific orbits, tiles (e.g., "T33UUP" for Sentinel-2 tile), or granule identifiers. Returns product metadata ordered by sensing date. Search satellite products by name pattern

search_by_orbit_number

Especially useful for Sentinel-1 (SAR) and Sentinel-2 (optical) repeat-pass analysis, interferometry, and change detection workflows where you need data from the exact same orbit geometry. Search satellite products by orbit number

search_products

Specify a collection name (e.g., "SENTINEL-2", "SENTINEL-1"), a date range in YYYY-MM-DD format, and optionally an area of interest as a WKT polygon. Returns product metadata including name, footprint, size, and publication date. Maximum 20 results by default. Search Sentinel satellite products by collection, date range, and area

Connect Copernicus Data Space to VS Code Copilot via MCP

Follow these steps to wire Copernicus Data Space into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Copernicus Data Space

Ask Copilot: "Using Copernicus Data Space, help me...". 14 tools available

Why Use VS Code Copilot with the Copernicus Data Space MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Copernicus Data Space through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Copernicus Data Space + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Copernicus Data Space MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Copernicus Data Space in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Copernicus Data Space immediately.

01

"Find Sentinel-2 satellite images over Lisbon from the last week."

02

"How many Sentinel-1 radar products are available for January 2026?"

03

"What data collections are available in the Copernicus Data Space?"

Troubleshooting Copernicus Data Space MCP Server with VS Code Copilot

Common issues when connecting Copernicus Data Space to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Copernicus Data Space + VS Code Copilot FAQ

Common questions about integrating Copernicus Data Space MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.