How to Use the Copernicus Data Space MCP in LlamaIndex

Q: How do I avoid duplicate API calls to Copernicus Data Space with LlamaIndex?

By indexing the results of searchbybbox into your LlamaIndex vector store, your agent checks local cache first. It only queries the live Copernicus catalog when the local index lacks coverage for the requested dates.

Q: Does LlamaIndex support the full Copernicus Data Space toolset?

Yes, all 14 tools including getquicklook and searchbyorbitnumber are exposed to the LlamaIndex agent. You can filter which tools are active using the allowedtools configuration.

Q: How does the agent handle Sentinel orbit numbers?

The agent uses searchbyorbitnumber to find matching passes, then indexes the sensing times. This makes it easy to run temporal change detection queries across identical orbit paths.

Index live Sentinel satellite metadata into your LlamaIndex vector store for grounded geospatial RAG.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Copernicus Data Space MCP to LlamaIndex

Create your Vinkius account to connect Copernicus Data Space to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Copernicus Data Space with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Grounded Geospatial RAG

LlamaIndex doesn't just execute spatial queries; it indexes the output of `search_products` straight into your local vector database. This means your agent can query past search runs to find Sentinel-2 footprints without hitting the live Copernicus API twice. By feeding the structured metadata from `get_product` into your index, you prevent hallucinations about satellite coverage. Your agent answers questions about cloud cover or sensing dates using verified, indexed facts instead of guessing.

Automated MCP Server Collection Indexing

Build a self-updating knowledge base of available Earth observation data using this MCP Server. Your LlamaIndex pipeline can run `list_latest_products` on a schedule, automatically indexing new Sentinel-1 and Sentinel-5P files as they get published. The tool `list_collections` provides the high-level schema of what's available, which the agent uses to route user queries to the right index. If a user asks about ocean temperature, LlamaIndex knows to search the Sentinel-3 collection index.

Granular File Hierarchy Mapping

Before downloading massive SAFE files, use LlamaIndex to map and query the internal structure of a product. The agent calls `list_product_nodes` to retrieve the file tree, indexing the paths so you can search for specific XML metadata files. Once the correct node is identified, the agent calls `get_product_download_url` to fetch only what you need. This keeps your vector store clean, indexing only the relevant file paths rather than raw binary data.

Setup guide

Set up Copernicus Data Space MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Copernicus Data Space MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Copernicus Data Space tools.",
)
response = await agent.run("List recent Copernicus Data Space data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Copernicus Data Space. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Copernicus Data Space now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Copernicus Data Space MCP in LlamaIndex

Yes, you convert the MCP Server tools into a LlamaIndex tool spec and pass them to your agent. The tool outputs are automatically formatted as document nodes, ready to be indexed or queried.

By indexing the results of `search_by_bbox` into your LlamaIndex vector store, your agent checks local cache first. It only queries the live Copernicus catalog when the local index lacks coverage for the requested dates.

Yes, all 14 tools including `get_quicklook` and `search_by_orbit_number` are exposed to the LlamaIndex agent. You can filter which tools are active using the allowed_tools configuration.

The agent uses `search_by_orbit_number` to find matching passes, then indexes the sensing times. This makes it easy to run temporal change detection queries across identical orbit paths.

Your Copernicus client keys and spatial query parameters are handled within a secure, ephemeral V8 sandbox via the MCP Server. We never write your satellite metadata queries or download tokens to persistent storage, keeping your geographical research private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript