4,000+ servers built on vurb.ts
Vinkius
Mastra AISDK
Mastra AI
INPE (STAC API - Satélites) MCP Server

Bring Satellite Imagery
to Mastra AI

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

MCP Inspector GDPR Free for Subscribers
Get CollectionGet ConformanceGet Root CatalogList Collection ItemsList CollectionsSearch Items

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
INPE (STAC API - Satélites)

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

  1. Subscribe to this server
  2. Enter your Brazil Data Cube (BDC) Access Key
  3. 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 Mastra AI?

Mastra's agent abstraction provides a clean separation between LLM logic and INPE (STAC API - Satélites) tool infrastructure. Connect 6 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.

  • Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add INPE (STAC API - Satélites) without touching business code

  • Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation

  • TypeScript-native: full type inference for every INPE (STAC API - Satélites) tool response with IDE autocomplete and compile-time checks

  • One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure

M
See it in action

INPE (STAC API - Satélites) in Mastra AI

AI AgentVinkius
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 Mastra AI 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 catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for INPE (STAC API - Satélites) in Mastra AI

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 Mastra AI 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.

INPE (STAC API - Satélites)
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 Mastra AI

Every tool call from Mastra AI 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

01

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.

02

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.

03

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.

04

How does Mastra AI connect to MCP servers?

Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.

05

Can Mastra agents use tools from multiple servers?

Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.

06

Does Mastra support workflow orchestration?

Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.

07

createMCPClient not exported

Install: npm install @mastra/mcp

Explore More MCP Servers

View all →