4,000+ servers built on vurb.ts
Vinkius

INPE (STAC API - Satélites) MCP Server for ClineGive Cline instant access to 6 tools to Get Collection, Get Conformance, Get Root Catalog, and more

MCP Inspector GDPR Free for Subscribers

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire INPE (STAC API - Satélites) through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Ask AI about this MCP Server for Cline

The INPE (STAC API - Satélites) MCP Server for Cline is a standout in the Government Public Data category — giving your AI agent 6 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "inpe-stac-api-satelites": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
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

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.

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including INPE (STAC API - Satélites) tool calls without waiting for prompts between steps. Connect 6 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

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.

The INPE (STAC API - Satélites) MCP Server exposes 6 tools through the Vinkius. Connect it to Cline 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 Cline

When Cline 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

Get collection on INPE (STAC API - Satélites)

Get detailed metadata for a specific collection

get

Get conformance on INPE (STAC API - Satélites)

Get STAC conformance classes

get

Get root catalog on INPE (STAC API - Satélites)

Get the root STAC catalog

list

List collection items on INPE (STAC API - Satélites)

List items within a specific collection

list

List collections on INPE (STAC API - Satélites)

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

search

Search items on INPE (STAC API - Satélites)

Search for items across collections

Connect INPE (STAC API - Satélites) to Cline via MCP

Follow these steps to wire INPE (STAC API - Satélites) into Cline. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel
02

Add remote server

Click "Add MCP Server" and paste the configuration above
03

Enable the server

Toggle the server switch to ON
04

Start using INPE (STAC API - Satélites)

Ask Cline: "Using INPE (STAC API - Satélites), help me...". 6 tools available

Why Use Cline with the INPE (STAC API - Satélites) MCP Server

Cline provides unique advantages when paired with INPE (STAC API - Satélites) through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

INPE (STAC API - Satélites) + Cline Use Cases

Practical scenarios where Cline combined with the INPE (STAC API - Satélites) MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from INPE (STAC API - Satélites) and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use INPE (STAC API - Satélites) tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from INPE (STAC API - Satélites) and generates snapshot tests or mocks based on actual payloads

04

Incident response: query INPE (STAC API - Satélites) for real-time status and let Cline generate hotfix patches based on the findings

Example Prompts for INPE (STAC API - Satélites) in Cline

Ready-to-use prompts you can give your Cline agent to start working with INPE (STAC API - Satélites) immediately.

01

"List all available satellite data collections from INPE."

02

"Search for satellite items in the bounding box [-48, -16, -47, -15] for the year 2023."

03

"Get details for the collection 'CBERS4-WFI-16D-2'."

Troubleshooting INPE (STAC API - Satélites) MCP Server with Cline

Common issues when connecting INPE (STAC API - Satélites) to Cline through Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

INPE (STAC API - Satélites) + Cline FAQ

Common questions about integrating INPE (STAC API - Satélites) MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Explore More MCP Servers

View all →