🪐 ✨ Earthdata MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Earthdata MCP Server?

Earthdata MCP Server is an implementation of the Model Context Protocol (MCP) that provides tools for interacting with NASA Earth Data, enabling efficient dataset discovery and retrieval for geospatial analysis.

how to use Earthdata MCP Server?

To use the Earthdata MCP Server, configure it with Claude Desktop by adding the necessary command to your claude_desktop_config.json file and run it using Docker. You can also use it in Jupyter for data analysis.

key features of Earthdata MCP Server?

  • Search for datasets and data granules on NASA Earthdata.
  • Supports temporal and spatial queries for dataset retrieval.
  • Integration with Jupyter for further data analysis.

use cases of Earthdata MCP Server?

  1. Searching for datasets related to climate change.
  2. Analyzing geospatial data for environmental research.
  3. Retrieving data granules for specific temporal and spatial conditions.

FAQ from Earthdata MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed to facilitate the discovery and retrieval of datasets in a standardized manner.

  • Can I use this server with Jupyter?

Yes! The server is designed to work seamlessly with Jupyter for data analysis.

  • Is there a demo available?

Yes! A demo is available to showcase how to analyze sea level rise using the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
BSD-3-Clause license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago