autoboundary

v0.1.0

Builds MIKE 21 SW/HD boundary conditions and wind forcing from public hindcasts: wave dfs1 (USACE WIS, NOAA GFS-Wave, Copernicus WAVERYS, DOE/NREL US Wave), water-level dfs1 (NOAA STOFS-2D, CO-OPS, pyTMD tide), current uv dfs1 (NOAA OFS, STOFS-3D, HYCOM, GLORYS) and wind/pressure dfs2 (HRRR, RRFS, RAP, GFS, ERA5). Windows and Linux only - the dfs writer has no macOS build.

Claude Code6 Skills1 MCP serverstdio

By Siyu MiaoLicense: MIT0 GitHub starsUpdated last week

Directory evidence

Runtimes: Claude Code
Parsed components: 7 skill or MCP entries
Source updated: Sep 15, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install autoboundary for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install autoboundary@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/msy920422/AutoBoundary

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/autoboundary/.

Plugin files

plugins/autoboundary/

├── .claude-plugin/plugin.json
├── skills/conventions/SKILL.md
├── skills/cur/SKILL.md
├── skills/inspect/SKILL.md
├── skills/wave/SKILL.md
├── skills/wind/SKILL.md
├── skills/wl/SKILL.md
└── .mcp.json

Included Skills6

conventionsskills/conventions/SKILL.md

The conventions every AutoBoundary result obeys - coming-from direction, UTC, no silent fills, model_zero datum, dropped points, provenance. Read this before interpreting, explaining or quoting any plan or run result from the autoboundary MCP tools, and before comparing an exported file with an existing MIKE boundary.

curskills/cur/SKILL.md

Build a MIKE 21 HD current boundary (two-item uv dfs1) from NOAA OFS, STOFS-3D-Atlantic, HYCOM or GLORYS, including the de-staggering, rotation, depth average and the dynamic-consistency caveat. Use when the user wants a velocity or current boundary, depth-averaged u/v forcing, or asks whether to prescribe currents at all.

inspectskills/inspect/SKILL.md

Inspect a MIKE file - a .mesh (nodes, projection, boundary codes), a dfs0/dfs1/dfs2 (items, EUM types, axis, ranges), an .mfm (which file each boundary code points at) - or an AutoBoundary output directory and its report. Use when the user asks what is in a mesh or a MIKE file, which boundary code to use, or what a previous run produced.

waveskills/wave/SKILL.md

Build a MIKE 21 SW parameterised wave boundary (dfs1) from a hindcast - choosing between USACE WIS, NOAA GFS-Wave, Copernicus WAVERYS and DOE/NREL US Wave, and cross-checking two of them. Use when the user wants wave forcing, Hs/Tp/MWD/DSD on an open boundary, or asks which wave product covers their site and dates.

windskills/wind/SKILL.md

Build a MIKE 21 wind and pressure forcing dfs2 from NOAA HRRR, RRFS, RAP, GFS or ECMWF ERA5, including the automatic source choice and the grid-relative to earth-relative wind rotation. Use when the user wants wind forcing, a wind/pressure dfs2, or asks which atmospheric product covers their domain and dates.

wlskills/wl/SKILL.md

Build a MIKE 21 HD water-level boundary (dfs1, Surface elevation) from NOAA STOFS-2D, CO-OPS gauges, a pyTMD tide model or the tide+surge composite, and get the vertical datum right. Use when the user wants a water-level or surface-elevation boundary, a tide or storm-surge boundary, or asks about NAVD88 / MSL / MLLW conversion on a MIKE boundary.

MCP servers1

autoboundarystdio

command: uvx
args: --from autoboundary[llm] autoboundary-mcp
env.PYTHONUTF8: 1
env.MPLBACKEND: Agg
env.AUTOBOUNDARY_CACHE: ${CLAUDE_PLUGIN_DATA}/cache

MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.

Plugin manifests1

plugins/autoboundary/.claude-plugin/plugin.json

{
  "name": "autoboundary",
  "displayName": "AutoBoundary",
  "description": "Builds MIKE 21 SW/HD boundary conditions and wind forcing from public hindcasts: wave dfs1 (USACE WIS, NOAA GFS-Wave, Copernicus WAVERYS, DOE/NREL US Wave), water-level dfs1 (NOAA STOFS-2D, CO-OPS, pyTMD tide), current uv dfs1 (NOAA OFS, STOFS-3D, HYCOM, GLORYS) and wind/pressure dfs2 (HRRR, RRFS, RAP, GFS, ERA5). Windows and Linux only - the dfs writer has no macOS build.",
  "version": "0.1.0",
  "author": {
    "name": "Siyu Miao"
  },
  "license": "MIT",
  "homepage": "https://github.com/msy920422/AutoBoundary/tree/main/plugins/autoboundary",
  "repository": "https://github.com/msy920422/AutoBoundary",
  "keywords": [
    "coastal",
    "mike21",
    "wave",
    "hydrodynamics",
    "boundary-conditions",
    "oceanography",
    "hindcast"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[autoboundary on Agent Plugins Marketplace](https://pluginsmp.com/plugins/autoboundary)