@pipeworx/mcp-ioos-erddap 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mojibake Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,161 @@
+# @pipeworx/ioos-erddap
+
+US Integrated Ocean Observing System data — buoys, tide gauges, gliders, HF radar currents, water
+quality and regional ocean model grids — read live from the IOOS regional associations' ERDDAP
+servers.
+
+Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1679+ live data sources.
+
+## Tools
+
+- `ioos_erddap_search_datasets(query, protocol?, node?, limit?)` — full-text search of one node's
+  catalogue. Start here: every other tool takes a `dataset_id` from these results.
+- `ioos_erddap_dataset_info(dataset_id, node?)` — variables, units, axes, time coverage, licence.
+- `ioos_erddap_tabledap(dataset_id, variables?, constraints?, node?, limit?)` — station and glider
+  timeseries rows.
+- `ioos_erddap_griddap_point(dataset_id, variable, latitude, longitude, time?, depth?, node?)` —
+  one gridded value from a regional model or radar grid.
+
+## Auth
+
+Keyless. Every node serves anonymously.
+
+## Data sources
+
+Six nodes, selected with `node`. A dataset lives on exactly one of them, so getting `node` right is
+the first thing a caller has to do; a wrong id raises an error that lists them all.
+
+| `node` | Server | Coverage |
+|---|---|---|
+| `national` | <https://erddap.ioos.us/erddap> | IOOS-wide inventories, asset and metric datasets |
+| `sensors` (default) | <https://erddap.sensors.ioos.us/erddap> | the national in-situ sensor network |
+| `gliders` | <https://gliders.ioos.us/erddap> | every US underwater glider deployment |
+| `pacioos` | <https://pae-paha.pacioos.hawaii.edu/erddap> | Hawaii and the Pacific Islands; ROMS and WRF grids |
+| `secoora` | <https://erddap.secoora.org/erddap> | the US Southeast |
+| `gcoos` | <https://erddap.gcoos.org/erddap> | the Gulf of Mexico |
+
+**NERACOOS and NANOOS are deliberately absent.** `https://www.neracoos.org/erddap` and
+`https://data.nanoos.org/erddap` both answer 301 from our egress (measured 2026-09-17). Adding them
+without resolving where they redirect would ship two node ids that fail for every caller. If you
+add them, verify a live search first, not just a reachable root.
+
+## Traps
+
+Protocol-level traps live in `shared/src/erddap.ts` (shared with `noaa-coastwatch`) and are
+documented in full at the top of that file. Two matter most here:
+
+- **`erddap.ioos.us` has almost no griddap.** The national node is inventories and metrics; the
+  gridded fields are on the regional nodes. A `griddap_point` call against `national` is not a bug.
+- **PacIOOS ROMS grids are 4-D: time, depth, latitude, longitude.** `depth` is required on those,
+  and omitting it is an axis error rather than a defaulted surface reading. `depth: 0.25` is the
+  shallowest level of `roms_hiig`.
+
+And the one this pack found the hard way: **ERDDAP's first `&`-segment is positional** — the server
+reads it as the variable list whatever it contains. Asking for every column (no `variables`) while
+dropping the now-empty first segment slides the row-cap expression into the variable slot and the
+server answers `Unrecognized variable="orderByLimit("5")"`, which reads as a broken dataset rather
+than a malformed URL. The shared client keeps the empty segment.
+
+## Quick Start
+
+Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
+
+```json
+{
+  "mcpServers": {
+    "ioos-erddap": {
+      "url": "https://gateway.pipeworx.io/ioos-erddap/mcp"
+    }
+  }
+}
+```
+
+### What this endpoint actually serves
+
+`tools/list` at `https://gateway.pipeworx.io/ioos-erddap/mcp` returns the tools in the table
+above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
+`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
+gateway-wide set. So the tool count you see is larger than this table: a
+single-pack endpoint currently lists roughly 30 shared tools alongside the
+pack's own. The connection's `initialize` response states its exact scope, and
+is the authoritative answer for a given day.
+
+This is deliberate, not multiplexing by accident. The meta-tools are what let a
+scoped connection answer a question this pack does not cover — via
+`ask_pipeworx`, which routes across the whole catalog — without you adding a
+second MCP server. There is currently no way to mount a pack endpoint without
+them; if the extra schemas cost you more context than the routing is worth,
+connect to the full gateway once rather than to several pack endpoints.
+
+Or connect to the full Pipeworx gateway to get every pack's tools listed
+directly, instead of just this one's:
+
+```json
+{
+  "mcpServers": {
+    "pipeworx": {
+      "url": "https://gateway.pipeworx.io/mcp"
+    }
+  }
+}
+```
+
+Both URLs reach the same gateway and the same 1679+ data sources. The
+only difference is which pack's tools are listed **directly**; `ask_pipeworx`
+reaches all of them from either one.
+
+## No MCP client? Call it over HTTP
+
+```bash
+curl -X POST https://gateway.pipeworx.io/v1/tools/ioos_erddap_search_datasets \
+  -H 'Content-Type: application/json' \
+  -d '{"query":"water temperature","node":"sensors","limit":5}'
+```
+
+No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/ioos_erddap_search_datasets`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
+
+## Standalone (no gateway account)
+
+This package also runs as a local stdio MCP server — no Pipeworx account, no
+gateway round-trip:
+
+```json
+{
+  "mcpServers": {
+    "ioos-erddap": {
+      "command": "npx",
+      "args": ["-y", "@pipeworx/mcp-ioos-erddap"]
+    }
+  }
+}
+```
+
+Or run it directly to confirm it starts:
+
+```bash
+npx -y @pipeworx/mcp-ioos-erddap
+```
+
+It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
+for **only** this pack's tools — none of the shared meta-tools the gateway
+connection above adds. Same source, same tools, no ask_pipeworx routing.
+
+## Using with ask_pipeworx
+
+Instead of calling tools directly, you can ask questions in plain English —
+this works on the pack endpoint above as well as on the full gateway:
+
+```
+ask_pipeworx({ question: "your question about Ioos Erddap data" })
+```
+
+The gateway picks the right tool and fills the arguments automatically.
+
+## More
+
+- [Docs and guides](https://pipeworx.io/docs)
+- [pipeworx.io](https://pipeworx.io)
+
+## License
+
+MIT

package/bin/cli.js

@@ -0,0 +1,17 @@
+#!/usr/bin/env node
+//
+// Entry point for `npx @pipeworx/mcp-<slug>`.
+//
+// Packs ship as raw TypeScript (no build step — see publish-pack.sh for why:
+// tsx sidesteps every extensionless-import / bare-JSON-import edge case a
+// per-pack tsc build would have to solve one pack at a time). This file
+// registers tsx's ESM loader programmatically, then hands off to src/server.ts,
+// which wraps the pack's {tools, callTool} export in a stdio MCP server.
+//
+// Copied verbatim into every published pack repo by scripts/publish-pack.sh —
+// edit this file, not a per-pack copy.
+import { register } from 'tsx/esm/api';
+
+register();
+
+await import('../src/server.ts');

package/package.json

@@ -0,0 +1,32 @@
+{
+  "name": "@pipeworx/mcp-ioos-erddap",
+  "version": "0.1.0",
+  "description": "US IOOS — regional ocean observing data via ERDDAP.",
+  "type": "module",
+  "main": "src/index.ts",
+  "types": "src/index.ts",
+  "bin": {
+    "mcp-ioos-erddap": "bin/cli.js"
+  },
+  "keywords": ["mcp", "mcp-server", "model-context-protocol", "pipeworx", "ioos-erddap"],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/pipeworx-io/mcp-ioos-erddap.git"
+  },
+  "scripts": {
+    "typecheck": "tsc --noEmit"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.30.0",
+    "tsx": "^4.19.0"
+  },
+  "devDependencies": {
+    "typescript": "^5.9.3",
+    "@cloudflare/workers-types": "^4.20260405.1"
+  },
+  "pipeworx": {
+    "sourceHash": "v1-41f644663584e8384b3455ef80ea09c5fb1a152571ad0f4584819d349e9be871",
+    "sourceCommit": "b0fb3c31386cf0256dcf1e2f1b3440435a87ec35"
+  }
+}

package/server.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.pipeworx-io/ioos-erddap",
+  "title": "Ioos Erddap",
+  "description": "US IOOS — regional ocean observing data via ERDDAP.",
+  "version": "0.1.0",
+  "websiteUrl": "https://pipeworx.io/packs/ioos-erddap",
+  "repository": {
+    "url": "https://github.com/pipeworx-io/mcp-ioos-erddap",
+    "source": "github"
+  },
+  "remotes": [
+    {
+      "type": "streamable-http",
+      "url": "https://gateway.pipeworx.io/ioos-erddap/mcp"
+    }
+  ]
+}