Claude CodeCLI

INPE (STAC API - Satélites) MCP Server

Bring Satellite Imagery
to Claude Code

Name: INPE (STAC API - Satélites) MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect INPE (STAC API - Satélites) to Claude Code and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Get CollectionGet ConformanceGet Root CatalogList Collection ItemsList CollectionsSearch Items

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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_catalog and get_conformance.
Collection Browsing — List all available data collections (e.g., CBERS4, Sentinel-2) and fetch detailed metadata for specific ones with list_collections and get_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_collection

Get detailed metadata for a specific collection

get_conformance

Get STAC conformance classes

get_root_catalog

Get the root STAC catalog

list_collection_items

List items within a specific collection

list_collections

g., CBERS4-WFI-16D-2, S2-16D-2). List all available data collections

search_items

Search for items across collections

Why Claude Code?

Claude Code registers INPE (STAC API - Satélites) as an MCP server in a single terminal command. Once connected, Claude Code discovers all 6 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where INPE (STAC API - Satélites) data drives decisions without human intervention.

—
Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart
—
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
—
Claude Code runs headlessly, enabling unattended batch processing using INPE (STAC API - Satélites) tools in cron jobs or deployment scripts
—
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

INPE (STAC API - Satélites) in Claude Code

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

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 Claude Code 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.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	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

Unlock for AI Agents View step-by-step setup guide for Claude Code →

Enterprise Security

Why teams choose Vinkius for INPE (STAC API - Satélites) in Claude Code

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 Claude Code 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.

Unlock for AI Agents View full INPE (STAC API - Satélites) details →

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

The Vinkius Advantage

How Vinkius secures
INPE (STAC API - Satélites) for Claude Code

Every tool call from Claude Code 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.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

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.

How do I add an MCP server to Claude Code?

Run claude mcp add <name> --transport http "<url>" in your terminal. Claude Code registers the server and discovers all tools immediately.

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code

Connection timeout

Check your internet connection and verify the Edge URL is reachable

Explore More MCP Servers

View all →

ChargeDesk

8 tools

Manage billing and payments via ChargeDesk — track charges, refund payments, and manage customers across multiple gateways directly from any AI agent.