Skip to main content

RTOFS MCP Server

MCP server for accessing NOAA RTOFS (Real-Time Ocean Forecast System) global ocean forecast data. Provides SST, salinity, ocean currents, and sea surface height from the operational HYCOM/ESPC model via the HYCOM THREDDS Data Server.

Features

  • Global 1/12° ocean forecasts (~8 km resolution)
  • 8-day forecast horizon, updated daily
  • Temperature, salinity, currents at all depth levels
  • Sea surface height (SSH) at hourly resolution
  • Point queries, depth profiles, area grids, and vertical transects
  • Pure httpx — no NetCDF/xarray dependencies needed

Installation

# Using uvx (recommended)
uvx rtofs-mcp

# Using pip
pip install rtofs-mcp

Tools

Tool Description
rtofs_get_system_info RTOFS overview — resolution, variables, coverage (no HTTP)
rtofs_list_datasets List HYCOM THREDDS datasets with live availability check
rtofs_get_latest_time Query latest forecast time from THREDDS
rtofs_get_surface_forecast Surface time series at a point (SST, SSS, currents, SSH)
rtofs_get_profile_forecast 3D depth profile at a point (temp, salinity, currents vs depth)
rtofs_get_area_forecast Surface forecast for a bounding box (parallel point queries)
rtofs_get_transect Vertical transect between two points (parallel depth profiles)
rtofs_compare_with_observations Change at a point over the 24 h before a time (default: now)

Example Queries

  • "What is the current SST at The Battery, NYC?"
  • "Show me a temperature depth profile at 35°N, 74°W in the Gulf Stream"
  • "Get the SST forecast for the next 8 days at latitude 25, longitude -80"
  • "Show a vertical transect of temperature from Miami to Bermuda"
  • "What are the ocean currents at 40°N, 74°W?"

Data Source

HYCOM THREDDS Data Server (https://tds.hycom.org/thredds/)

ESPC-D-V02 datasets (operational HYCOM/RTOFS):

  • FMRC_ESPC-D-V02_ssh — Sea Surface Height (2D, hourly)
  • FMRC_ESPC-D-V02_t3z — Water Temperature (3D, 3-hourly)
  • FMRC_ESPC-D-V02_s3z — Salinity (3D, 3-hourly)
  • FMRC_ESPC-D-V02_uv3z — Ocean Currents u/v (3D, 3-hourly)

Data is queried via THREDDS NCSS (NetCDF Subset Service) which returns CSV for point queries — no NetCDF library required.

Configuration

Claude Desktop

{
  "mcpServers": {
    "rtofs": {
      "command": "uvx",
      "args": ["rtofs-mcp"]
    }
  }
}

Development

cd servers/rtofs-mcp
uv sync --group dev
uv run rtofs-mcp                                          # Start server
uv run pytest tests/ --ignore=tests/test_live.py -v       # Unit tests
uv run pytest tests/test_live.py -v                       # Integration tests

License

MIT

Metadata

Release files for rtofs-mcp 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rtofs-mcp 0.1.3
File Size Uploaded
rtofs_mcp-0.1.3.tar.gz 25.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rtofs-mcp 0.1.3
File Interpreter ABI Platform
rtofs_mcp-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 45.7 kB

Release files / rtofs_mcp-0.1.3.tar.gz

Download URL rtofs_mcp-0.1.3.tar.gz
Size 25.0 kB
Tags Source
SHA-256 checksum
How to use checksums
69f776b84a09ba48a8d966632e1a9b5aa125c6522da3722bbba30b08b76b88ae
BLAKE2b-256 checksum
How to use checksums
238a734f1531d5b3d9621c7ab189de30f12482820783d2b6322f6106c919ef05
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 14, 2026.

Transparency log

Release files / rtofs_mcp-0.1.3-py3-none-any.whl

Download URL rtofs_mcp-0.1.3-py3-none-any.whl
Size 20.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e07db65e35291ff5a1a97bb783b8e1a6ca21e955e640c5ef9ae3f76131d7d46a
BLAKE2b-256 checksum
How to use checksums
b47a37093db7116181f80214cc9b7d3c9cb1721beff398cbce4fd7449aecc4e8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 14, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.3 This release

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page