Bring Satellite Imagery
to VS Code Copilot
Learn how to connect INPE (STAC API - Satélites) to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
Compatible with every major AI agent and IDE
What is the INPE (STAC API - Satélites) MCP Server?
Connect to the INPE Brazil Data Cube and explore high-resolution satellite imagery catalogs through natural language. This server implements the STAC (SpatioTemporal Asset Catalog) specification to provide seamless access to Earth observation data from missions like CBERS, Sentinel, and Landsat.
What you can do
- Catalog Discovery — Explore the root catalog and check conformance classes of the INPE STAC server using
get_root_catalogandget_conformance. - Collection Browsing — List all available data collections (e.g., CBERS4, Sentinel-2) and fetch detailed metadata for specific ones with
list_collectionsandget_collection. - Item Listing — Retrieve specific scenes and assets within a collection using spatial (bounding box) and temporal filters via
list_collection_items. - Advanced Search — Perform cross-collection searches to find the exact satellite imagery needed for environmental monitoring or research using
search_items.
How it works
- Subscribe to this server
- Enter your Brazil Data Cube (BDC) Access Key
- Start querying satellite metadata from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Data Scientists & Researchers — Quickly find satellite scenes for specific dates and regions without manual API calls or complex scripts.
- Environmental Analysts — Monitor land use, deforestation, or agricultural changes using INPE's curated data cubes directly from your AI assistant.
- GIS Developers — Integrate satellite metadata discovery and asset retrieval directly into your development workflow.
Built-in capabilities (6)
Get detailed metadata for a specific collection
Get STAC conformance classes
Get the root STAC catalog
List items within a specific collection
g., CBERS4-WFI-16D-2, S2-16D-2). List all available data collections
Search for items across collections
Why VS Code Copilot?
GitHub Copilot Agent mode brings INPE (STAC API - Satélites) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
INPE (STAC API - Satélites) in VS Code Copilot
INPE (STAC API - Satélites) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect INPE (STAC API - Satélites) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for INPE (STAC API - Satélites) in VS Code Copilot
The INPE (STAC API - Satélites) 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. All 6 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
INPE (STAC API - Satélites) for VS Code Copilot
Every tool call from VS Code Copilot to the INPE (STAC API - Satélites) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I see what types of satellite data are available?
Use the list_collections tool. It will return a list of all available datasets in the INPE Brazil Data Cube, such as CBERS-4, Sentinel-2, and various synthesized data cubes.
Can I search for specific images using geographic coordinates?
Yes! Use the search_items tool and provide a bbox (bounding box) string in the format '[minx, miny, maxx, maxy]'. This allows you to find all satellite scenes covering your area of interest.
How do I get the technical metadata for a specific collection?
Use the get_collection tool with the specific collection_id (e.g., 'CBERS4-WFI-16D-2'). It will provide detailed information about the spatial extent, temporal interval, and available assets for that collection.
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.
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.
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.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
AirMatch Pro
10 toolsMatch candidates to job openings with AI-powered recruitment scoring and talent pipeline management for faster hiring.

Fireflies.ai
12 toolsRecord, transcribe, and search across all your meetings with AI that captures every conversation and makes it instantly findable.

Infracost
13 toolsCloud cost estimates for Terraform — manage cost guardrails, tagging policies, and custom enterprise price books directly through your AI agent.

Hugging Face
15 toolsAccess thousands of pre-trained AI models for NLP, vision, and audio tasks with the largest open-source machine learning hub.
