About Nausika
Nausika’s public repository is an issue tracker for its connector between AI assistants and the sea. It is intended for reporting bugs, requesting features and identifying gaps in regional coverage; the repository contains no product code.
Key features
- 01File bug reports
- 02Request features
- 03Flag coverage gaps
- 04Use issue templates
- 05Weekly issue triage
Use cases
- 01Report an incorrect sea forecast, route or place
- 02Request a connector behavior change
- 03Identify regions with missing or inaccurate atlas coverage
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.nausika.appclaude mcp add --transport http app-nausika https://mcp.nausika.app{"mcpServers":{"app-nausika":{"type":"http","url":"https://mcp.nausika.app"}}}Open in Cursor{"servers":{"app-nausika":{"type":"http","url":"https://mcp.nausika.app"}}}Open in VS Code{"mcpServers":{"app-nausika":{"type":"http","url":"https://mcp.nausika.app"}}}{"mcpServers":{"app-nausika":{"serverUrl":"https://mcp.nausika.app"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
19| Parameter | Type | Required | Description |
|---|---|---|---|
| preset | enum | No | High-level mode. now=current snapshot, today=24h hourly+daily, tactical=3d hourly_3+daily (default), planning=8d daily, extended=14d daily, none=3d hourly_3+daily but with NO core variables (caller supplies full variables list).now | today | tactical | planning | extended | none |
| end_date | string | No | Window end date YYYY-MM-DD. Used with start_date. Defaults to preset. Same ~16-day (forecast) / ~8-day (marine) window limit as start_date — use nausika_seasonal_forecast beyond that. |
| end_hour | string | No | Window end ISO YYYY-MM-DDThh:mm. Used with start_hour. Defaults to preset. |
| latitude | number | Yes | Latitude in decimal degrees (WGS84, -90 to 90) |
| longitude | number | Yes | Longitude in decimal degrees (WGS84, -180 to 180) |
| variables | array | No | Extra variables added to the preset core (additive). Each is routed to its endpoint automatically. Required (non-empty) when preset='none'. Examples: swell_wave_height/swell_wave_direction/swell_wave_period for swell breakdown, ocean_current_velocity/ocean_current_direction (FROM-corrected) for currents, cape for thunderstorm risk, uv_index_max for UV. |
| start_date | string | No | Window start date YYYY-MM-DD. Used with end_date. Wins over forecast_hours/forecast_days. Defaults to preset. Must fall within the rolling forecast window (~16 days ahead for atmospheric data, ~8 days for marine/wave data) — for dates further out, use nausika_seasonal_forecast instead. |
| start_hour | string | No | Window start ISO YYYY-MM-DDThh:mm. Used with end_hour. Most specific override (wins over date and hour-count windows). Defaults to preset. |
| forecast_days | integer | No | Override preset days (1-16). Forecast endpoint caps at 16, Marine at 8. Defaults to preset. |
| forecast_hours | integer | No | Override with an hourly window. Wins over forecast_days. Defaults to preset. |
| include_percentiles | boolean | No | When true, ALSO fetch the Open-Meteo ECMWF IFS-ENS ensemble (50 perturbed members) and expose `<var>_p10/_p50/_p90` percentile series alongside the deterministic forecast for atmospheric variables (precipitation, wind, gusts, pressure, temperature, etc.). Reveals forecast uncertainty — useful at planning/extended horizons or for convective setups where the deterministic run can disagree wildly with the ensemble median. Waves/swell/currents/SST stay deterministic (no public ensemble). Adds one extra HTTP call (~200ms latency) and grows the hourly payload ~4×. Default false. |
| temporal_resolution | enum | No | Override hourly granularity. hourly_1=every hour, hourly_3=every 3h, hourly_6=every 6h. Defaults to the preset's resolution.hourly_1 | hourly_3 | hourly_6 |
Details
From the project READMENausika — Feedback & Issue Tracker
This repository is the public issue tracker for Nausika, a connector between AI assistants and the sea.
There is no code here. File a bug, request a feature, flag a coverage gap — the maintainer triages weekly.
Before filing
- A question, not a bug? Email [email protected] — faster for Q&A.
- A privacy concern? Use [email protected].
- Already filed? Check open issues — a thumbs-up counts more than a duplicate.
Filing
Use the issue templates:
- Bug — something's wrong with a forecast, a route, a place, or the connector
- Feature — something missing or that should work differently
- Coverage — a region where Nausika's atlas is blank, thin, or wrong
What we ship
Nausika is in public beta. Maintainer: Andrea di Cagno. Triage cadence: weekly. No SLA — this is a beta.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.