2,500+ MCP servers ready to use
Vinkius

Planet Labs MCP Server for Claude Desktop 12 tools β€” connect in under 2 minutes

Built by Vinkius GDPR 12 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach β€” Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers β€” no config files, no terminal commands. Install Planet Labs and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic SetupΒ·json
{
  "mcpServers": {
    "planet-labs": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Planet Labs
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 Planet Labs MCP Server

Connect your Planet Labs API to any AI agent and take full control of daily satellite imagery search, discovery, automated delivery, and imagery analysis through natural conversation.

Claude Desktop is the definitive way to connect Planet Labs to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Quick Search β€” Search for satellite imagery with geometry, date range, cloud cover, and sun elevation filters
  • Saved Searches β€” Create and manage saved searches for recurring imagery monitoring workflows
  • Search Results β€” Execute saved searches with pagination and sorting to retrieve imagery results
  • Search Statistics β€” Get histograms of imagery availability by time interval for planning analysis
  • Item Details β€” View detailed metadata for specific imagery items including acquisition conditions
  • Asset Discovery β€” List all available asset types (visual, analytic, UDM2) for each imagery item
  • Item Types β€” Browse all available satellite imagery types (PSScene, SkySat, RapidEye, Landsat, Sentinel-2)
  • Asset Types β€” Understand available data products (true-color, surface reflectance, uncertainty masks)
  • Cloud Coverage β€” Estimate clear area percentage before downloading imagery for quality assessment
  • Subscriptions β€” List and create automated subscriptions for continuous cloud delivery of imagery
  • Multi-Satellite Access β€” Search across PlanetScope (3-5m), SkySat (sub-meter), RapidEye (5m), Landsat (30m), and Sentinel-2 (10m)
  • Global Daily Coverage β€” Access daily imagery of Earth landmass with 200+ PlanetScope satellites

The Planet Labs MCP Server exposes 12 tools through the Vinkius. Connect it to Claude Desktop in under two minutes β€” no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Planet Labs to Claude Desktop via MCP

Follow these steps to integrate the Planet Labs MCP Server with Claude Desktop.

01

Open Claude Desktop Settings

Go to Settings β†’ Developer β†’ Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using Planet Labs

Look for the πŸ”Œ icon in the chat. your 12 tools are now available

Why Use Claude Desktop with the Planet Labs MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Planet Labs through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Planet Labs + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Planet Labs MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Planet Labs MCP Tools for Claude Desktop (12)

These 12 tools become available when you connect Planet Labs to Claude Desktop via MCP:

01

create_saved_search

Accepts the same filter parameters as quick_search including geometry, date range, cloud cover, and item types. Returns a search ID that can be used with get_search_results to execute the search on demand. Essential for automated monitoring, change detection workflows, and recurring imagery retrieval. AI agents should use this when users ask "set up a search for new imagery over my field every week", "create a saved search for cloud-free images", or need to establish recurring imagery monitoring for a specific area. Create a saved search for continuous imagery monitoring

02

create_subscription

Accepts geometry, date range, cloud cover filters, item types, and delivery destination (cloud storage or webhook). Returns the created subscription with ID and status. Essential for setting up automated monitoring, establishing continuous data feeds for change detection, and ensuring regular imagery delivery for operational workflows. AI agents should use this when users ask "set up daily imagery delivery for my farm", "create a subscription for cloud-free images over this area", or need to establish automated imagery delivery for monitoring applications. Create a new subscription for continuous automated imagery delivery

03

get_cloud_coverage

Returns clear percentage, cloud percentage, and status information. Essential for quality assessment before downloading imagery, filtering cloudy images from analysis workflows, and ensuring usable imagery for visual interpretation. AI agents should use this when users ask "how cloudy is this image", "what percentage of this scene is clear", or need to assess imagery quality before committing to download. Estimate cloud coverage and clear area percentage for a specific imagery item

04

get_item_assets

Each asset includes download URLs, file sizes, and permissions. Essential for selecting the appropriate data product for analysis, downloading imagery for GIS processing, and understanding available data products. AI agents should use this when users ask "what assets are available for this image", "get download URLs for analytic imagery", or need to select specific asset types (visual for display, analytic for analysis) for download. List all available asset types (visual, analytic, UDM) for a specific imagery item

05

get_item_details

Essential for evaluating image quality before download, understanding acquisition conditions, and preparing orders for specific imagery. AI agents should reference this when users ask "show me details for this image", "what is the cloud cover and acquisition time for item X", or need to evaluate imagery quality before downloading. Get detailed metadata for a specific satellite imagery item

06

get_search_results

Supports pagination (page, page_size) and sorting (acquired asc/desc, published asc/desc). Returns imagery items with acquisition dates, cloud cover, geometry, and available asset types. Essential for retrieving results from pre-configured monitoring searches and executing recurring imagery queries. AI agents should use this when users ask "run my Weekly Farm Monitoring search", "get results from saved search X", or need to execute a saved search and retrieve the latest imagery results. Execute a saved search and retrieve imagery results

07

get_search_statistics

Essential for understanding imagery availability patterns, planning data collection schedules, and assessing temporal coverage for change detection analysis. AI agents should use this when users ask "how many images are available per month for my area", "show me imagery availability statistics", or need to understand temporal patterns of satellite coverage before setting up monitoring. Get statistical histograms of available imagery for an area and time period

08

list_asset_types

Returns asset type IDs, display names, and descriptions. Essential for selecting the appropriate data product for specific use cases (visual for visualization, analytic for NDVI calculation, UDM for quality filtering). AI agents should reference this when users ask "what asset types can I download", "difference between analytic and visual assets", or need to understand available data products for analysis. List all available asset types (visual, analytic, UDM, etc.) and their properties

09

list_item_types

Returns item type IDs, display names, and supported asset types for each. Essential for understanding available imagery sources, selecting appropriate resolution and coverage for analysis, and planning data acquisition strategies. AI agents should use this when users ask "what satellite imagery types are available", "compare PSScene vs SkySat resolution", or need to understand the full catalog of Planet imagery options. List all available satellite imagery item types and their supported assets

10

list_saved_searches

Returns search names, IDs, filter criteria, item types, and creation dates. Essential for managing monitoring workflows, reviewing existing search configurations, and selecting searches for execution. AI agents should reference this when users ask "show me all my saved searches", "list my monitoring configurations", or need to review existing saved searches before executing them. List all saved searches in your Planet account

11

list_subscriptions

Returns subscription names, IDs, filter criteria, delivery destinations, and status. Essential for monitoring automated imagery delivery, reviewing subscription configurations, and managing continuous data feeds. AI agents should reference this when users ask "show me all my subscriptions", "list automated imagery deliveries", or need to review existing subscription configurations. List all active imagery subscriptions for continuous cloud delivery

12

quick_search

Supports item types including PSScene (PlanetScope, 3-5m resolution, daily global coverage), SkySat (sub-meter resolution, high-detail), RapidEye (5m resolution, historical archive), Landsat 8/9 (30m resolution, USGS), and Sentinel-2 (10m resolution, ESA). Returns imagery items with acquisition dates, cloud cover percentages, sun elevation, instrument mode, geometry, and available asset types. Essential for satellite imagery discovery, change detection analysis, disaster monitoring, and agricultural assessment. AI agents should use this when users ask "find cloud-free imagery over this area from last month", "search for PSScene images of my farm", or need to discover available satellite imagery for a specific location and time period. Geometry must be provided as GeoJSON (Point, Polygon, or MultiPolygon). Date filtering uses the acquired property in ISO 8601 format. Cloud cover and sun elevation are filtered using the filter object with range operators. Search for satellite imagery from Planet Labs with geometry, date, and cloud cover filters

Example Prompts for Planet Labs in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Planet Labs immediately.

01

"Find cloud-free PSScene imagery over my farm boundary from the last 30 days."

02

"Show me what satellite imagery types are available and their resolutions."

03

"Create a daily subscription for cloud-free imagery over my monitoring area."

Troubleshooting Planet Labs MCP Server with Claude Desktop

Common issues when connecting Planet Labs to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the πŸ”Œ icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Planet Labs + Claude Desktop FAQ

Common questions about integrating Planet Labs MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the πŸ”Œ icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect Planet Labs to Claude Desktop

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.