goes-mcp
MCP server for NOAA GOES satellite imagery — visible, infrared, water vapor, and composite products from GOES-18 (West) and GOES-19 (East).
Features
- 16 ABI spectral bands — visible, near-IR, and infrared channels
- 6 composite products — GeoColor, AirMass, Sandwich, Fire Temperature, Dust, Derived Motion Winds
- Multiple coverages — CONUS, Full Disk, and 5 regional sectors (SE, NE, Caribbean, Tropical Atlantic, Puerto Rico)
- Image embedding — returns JPEG images directly via MCP
Imagetype - Flexible output — image (default), markdown with URL, or JSON metadata
Data Sources
- NOAA STAR CDN (
cdn.star.nesdis.noaa.gov) — pre-rendered JPEG imagery at multiple resolutions - RAMMB/CIRA SLIDER (
slider.cira.colostate.edu) — timestamp discovery for historical imagery
No API keys required. All data is freely available from NOAA.
Tools
| Tool | Description |
|---|---|
goes_list_products |
List all available bands, composites, coverages, and sectors |
goes_get_available_times |
Get recent image timestamps for a product (via SLIDER API) |
goes_get_latest_image |
Fetch the most recent satellite image |
goes_get_image |
Fetch a satellite image for a specific timestamp |
goes_get_sector_image |
Fetch latest imagery for a regional sector |
goes_get_current_view |
Overview of current imagery availability |
Installation
# With uv (recommended)
uvx goes-mcp
# With pip
pip install goes-mcp
Usage with Claude Desktop
Add to your Claude Desktop config:
{
"mcpServers": {
"goes": {
"command": "uvx",
"args": ["goes-mcp"]
}
}
}
Example Queries
- "Show me the latest GOES-East GeoColor image of the Continental US"
- "Get a satellite view of the Caribbean right now"
- "What satellite imagery is currently available?"
- "Show me infrared band 13 for the full disk view"
- "Get the latest fire temperature composite for the Southeast US"
Development
cd servers/goes-mcp
uv sync --group dev
# Run unit tests
uv run pytest tests/ --ignore=tests/test_live.py --ignore=tests/test_mcp_protocol.py -v
# Run MCP protocol test
uv run pytest tests/test_mcp_protocol.py -v
# Run live integration tests (requires network)
uv run pytest tests/test_live.py -v
# Lint
uv run ruff check src/ tests/ --select E,F,W --ignore E501
uv run ruff format --check src/ tests/
License
MIT
Release files for goes-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| goes_mcp-0.1.2.tar.gz | 16.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| goes_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.2 kB
Release files / goes_mcp-0.1.2.tar.gz
| Download URL | goes_mcp-0.1.2.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4d75acc66f1a651d74fd7b986d20b8cea029db46e8aa35a7b0128959080c4b0
|
|
BLAKE2b-256 checksum How to use checksums |
5c4252340748108135852b185e589301284f5a75eff3e3590ffedd579087a4e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 6, 2026.
Transparency logRelease files / goes_mcp-0.1.2-py3-none-any.whl
| Download URL | goes_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
425721551aa4caf1763fd9573360c4f312b59f150f744560c7f99125863f6faf
|
|
BLAKE2b-256 checksum How to use checksums |
b9cf20e1dc63c744d0ce0377d07535a9eda0f89648251f60ba7d1c0237de8fb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 6, 2026.
Transparency log