Bring Satellite Imagery
to Cursor
Learn how to connect INPE (STAC API - Satélites) to Cursor 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 SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns INPE (STAC API - Satélites) into an in-editor superpower. Ask Cursor to generate code using live data from INPE (STAC API - Satélites) and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
INPE (STAC API - Satélites) in Cursor
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 Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Aimtell
10 toolsWeb push notification orchestration — manage campaigns, segments, and subscribers via AI.
Deterministic Math Expression Evaluator
1 toolsEquip your AI with flawless algebraic parsing. Safely evaluate complex mathematical string expressions without using vulnerable `eval()` execution.
Grepsr
12 toolsAutomate web scraping via Grepsr — manage reports, trigger crawls, and retrieve data directly via AI.
TripGo
9 toolsAI multimodal transit: plan trips, track vehicles, and check schedules via agents.