INPE (STAC API - Satélites) MCP Server for CursorGive Cursor instant access to 6 tools to Get Collection, Get Conformance, Get Root Catalog, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this MCP Server for Cursor
The INPE (STAC API - Satélites) MCP Server for Cursor is a standout in the Government Public Data category — giving your AI agent 6 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
{
"mcpServers": {
"inpe-stac-api-satelites": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install INPE (STAC API - Satélites) and 4,000+ MCP Servers from a single visual interface.





* 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
About 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.
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.
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.
The INPE (STAC API - Satélites) MCP Server exposes 6 tools through the Vinkius. Connect it to Cursor in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 6 INPE (STAC API - Satélites) tools available for Cursor
When Cursor connects to INPE (STAC API - Satélites) through Vinkius, your AI agent gets direct access to every tool listed below — spanning satellite-imagery, stac-api, earth-observation, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.
Get collection on INPE (STAC API - Satélites)
Get detailed metadata for a specific collection
Get conformance on INPE (STAC API - Satélites)
Get STAC conformance classes
Get root catalog on INPE (STAC API - Satélites)
Get the root STAC catalog
List collection items on INPE (STAC API - Satélites)
List items within a specific collection
List collections on INPE (STAC API - Satélites)
g., CBERS4-WFI-16D-2, S2-16D-2). List all available data collections
Search items on INPE (STAC API - Satélites)
Search for items across collections
Connect INPE (STAC API - Satélites) to Cursor via MCP
Follow these steps to wire INPE (STAC API - Satélites) into Cursor. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using INPE (STAC API - Satélites)
Why Use Cursor with the INPE (STAC API - Satélites) MCP Server
Cursor AI Code Editor provides unique advantages when paired with INPE (STAC API - Satélites) through the Model Context Protocol.
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) + Cursor Use Cases
Practical scenarios where Cursor combined with the INPE (STAC API - Satélites) MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for INPE (STAC API - Satélites) in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with INPE (STAC API - Satélites) immediately.
"List all available satellite data collections from INPE."
"Search for satellite items in the bounding box [-48, -16, -47, -15] for the year 2023."
"Get details for the collection 'CBERS4-WFI-16D-2'."
Troubleshooting INPE (STAC API - Satélites) MCP Server with Cursor
Common issues when connecting INPE (STAC API - Satélites) to Cursor through Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
INPE (STAC API - Satélites) + Cursor FAQ
Common questions about integrating INPE (STAC API - Satélites) MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
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?
How do I verify MCP tools are loaded?
Explore More MCP Servers
View all →
Stemmer & Lemmatizer Engine
1 toolsPorter and Lancaster local text stemming. Reduce vocabulary size exactly and deterministically before feeding text to a vector database.

Figma Alternative
16 toolsAccess Figma design files, comments, components and images via API — inspect nodes, render exports and track version history from any AI agent.

WeChat Mini-Programs / 微信小程序
10 toolsChina's dominant mini-app ecosystem — manage users, phone numbers, and messaging via AI.

Wazuh (SIEM)
21 toolsManage your Wazuh SIEM infrastructure—monitor agents, inspect security events, and manage manager configurations directly from your AI agent.
