Dmap Ai Mcp Server

Created By
sohrab47486 days ago
DMAP-AI MCP Server provides AI-accessible drought monitoring and SPI drought analysis tools using NASA POWER and ERA5-Land/CDS data. It supports SPI tables, drought severity event detection, wavelet scalogram analysis, global wavelet periodicity diagnostics, and structured JSON output for climate, hydrology, agriculture, and drought research workflows.
Overview

DMAP-AI MCP Server

DMAP-AI MCP Server is a remote Model Context Protocol server for drought monitoring and SPI drought analysis from AgriMetSoft LLC.

It provides AI-accessible tools for point-based drought analysis using real climate data from NASA POWER and ERA5-Land/CDS.

Main capabilities

  • SPI drought table generation
  • Drought severity event detection
  • Wavelet scalogram analysis
  • Global wavelet / drought periodicity analysis
  • Structured JSON output
  • Read-only drought diagnostics from real climate data

Data sources

  • NASA POWER
  • ERA5-Land / Copernicus Climate Data Store

MCP endpoint

The server is available as a remote streamable HTTP MCP server:

https://droughtanalysis.com/mcp

GitHub repository

https://github.com/sohrab4748/dmap-ai-mcp

Official DMAP-AI website

https://droughtanalysis.com/

Research Version

https://droughtanalysis.com/DMAP_AI_App

Developer

AgriMetSoft LLC

https://agrimetsoft.com

Server Config

{
  "mcpServers": {
    "dmap-ai": {
      "type": "streamable-http",
      "url": "https://droughtanalysis.com/mcp"
    }
  }
}
Project Info
Created At
6 days ago
Updated At
6 days ago
Author Name
sohrab4748
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago