
NOAA GOES Satellite Imagery MCP Server
Let your coding agent pull live GOES-18/19 satellite layers while you build weather dashboards or research tools.
Overview
goes-mcp is a MCP server for the Build phase that exposes NOAA GOES-18/19 visible, infrared, water vapor, and composite satellite imagery to your agent.
What is this MCP server?
- GOES-18 and GOES-19 imagery via NOAA public data
- Four product families: visible, infrared, water vapor, and composites
- stdio MCP transport with PyPI package and uvx runtime hint
- Version 0.1.2 from the ocean-mcp monorepo on GitHub
- Suited for agent-driven map overlays and environmental monitoring prototypes
- Supports GOES-18 and GOES-19 satellites
- Imagery modes: visible, infrared, water vapor, composites
- Package version 0.1.2 on PyPI with uvx runtime hint
Community signal: 5 GitHub stars.
What problem does it solve?
Agents cannot fetch authoritative GOES satellite layers on their own, so weather and map features stall on manual downloads or brittle NOAA URL guesswork.
Who is it for?
Indie builders adding real-time U.S. satellite imagery to agent-assisted weather or geospatial apps.
Skip if: Teams that only need a static screenshot once and do not want MCP or uvx in their agent stack.
What do I get? / Deliverables
After you register goes-mcp, your agent can pull GOES imagery through MCP tools while you code dashboards, APIs, or research notebooks.
- Agent-callable MCP tools for GOES-18/19 imagery products
- stdio-backed integration suitable for local dev configs
- Foundation for map overlays or weather APIs in your codebase
Recommended MCP Servers
Journey fit
Canonical shelf is Build because the server wires NOAA geostationary imagery into agent workflows as an integration, not a standalone research write-up. Integrations is the right subphase: stdio MCP tools expose visible, infrared, water vapor, and composite products from public NOAA feeds.
How it compares
NOAA imagery MCP integration, not a prebuilt weather SaaS or generic web-scraping skill.
Common Questions / FAQ
Who is goes-mcp for?
Solo and indie developers who use Claude Code, Cursor, or Codex to build apps that need GOES-18/19 satellite imagery from NOAA.
When should I use goes-mcp?
Use it during Build when you are integrating live visible, infrared, water vapor, or composite GOES frames into maps, APIs, or agent workflows.
How do I add goes-mcp to my agent?
Install the PyPI package goes-mcp, run it via uvx with stdio transport, and add the server entry to your agent’s MCP configuration using the published server name.