Provider hosted
Tools: 28

Home OpenPlotter Cloud

Home OpenPlotter Cloud

The open-source sailing platform. Save data in the cloud to access charts and graphs. Access anywhere. Your boat software to record, track, manage, report on your vessels

https://openplotter.cloud/

Use in your AI tool

Connect straight to this server’s public endpoint.

Remote MCP URL
https://mcp.openplotter.cloud/mcp

Use on MCPBundles

We add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.

Last probed Sep 14, 2026 · mcp.openplotter.cloud

28tools discovered

Tools discovered (28)

Showing 25 of 28 from the live probe.

  • List user vessels

    Returns the list of vessels visible to the authenticated user, including identifiers, connectivity status, and recent telemetry timestamps. Use this tool first when the user refers to 'my vessel' without specifying which one.

  • Get vessel metadata

    Returns the complete vessel profile: • Identity: name, MMSI, vessel_id, registration country, AIS ship type • Physical dimensions from AIS/SignalK: length (m), beam (m), height (m) • Connectivity: first_contact, last_contact, offline flag (no data >70 min) • Make/model: user-entered string (e.g. 'Bavaria 38 Holiday', 'Sun Fast 37') • Boat spec (spec key): structured sailboatdata.com data when linked — LOA, LWL, beam, max/min draft (m), displacement (kg), ballast (kg), sail area (m²), SA/disp

  • Get vessel Polar metadata

    Returns the vessel's Polar (CSV) data if present in an OCR CSV format. Useful for performance analysis and optimization.

  • List voyage logs

    List voyage logs (trips) with start/end times, distance, duration, and tags. Supports filtering by date range, minimum distance, minimum duration, and tags. Use to browse past voyages or narrow down to specific trips.

  • Get last log details

    Get full details for the vessel's most recent voyage log: GPS track (GeoJSON), distance (NM), duration, average and max speed (knots), max wind speed (TWS knots), departure and arrival moorage names and IDs, and per-point sensor time-series (COG, SOG, depth, wind speed/direction, water temperature, battery, solar, pressure, heading, tank level). Use to answer questions about a specific trip or to obtain moorage IDs for follow-up calls.

  • Get log details

    Get full details for a specific voyage log by ID: GPS track (GeoJSON), distance (NM), duration, average and max speed (knots), max wind speed (TWS knots), departure and arrival moorage names and IDs, and per-point sensor time-series (COG, SOG, depth, wind speed/direction, water temperature, battery, solar, pressure, heading, tank level). Use to answer questions about a specific trip or to obtain moorage IDs for follow-up calls.

  • Get voyage tracks as map data

    Retrieve recent voyage tracks as GeoJSON geographic line features for map rendering. Use when the user wants to visualize, plot, or display their trips on a map. Supports pagination to browse older tracks.

  • Export voyage track file

    Export a specific voyage track as a downloadable file in GPX, GeoJSON, or KML format. GPX works with GPS devices and navigation apps (e.g. Garmin, OpenCPN). KML opens in Google Earth. GeoJSON works with web mapping tools. Use when the user wants to save, share, or re-use a trip track.

  • List visited moorages

    List all moorages (anchorages, marinas, mooring buoys) the vessel has visited, with location, stay type, and usage statistics. Supports filtering by type (anchor, dock, mooring buoy) and pagination.

  • Get moorage details

    Get full details for a specific moorage by ID: location, stay type, and usage statistics.

  • Get all stays at one moorage

    Get the chronological list of every stay recorded at a specific moorage, identified by moorage ID. Returns stay type and duration alongside the inbound log (which voyage arrived here) and the outbound log (which voyage departed from here). Prefer this over get_stays when you already have a moorage ID and want its full visit history. Use for single-location questions: 'how many times have I been to this anchorage?', 'how long did I spend here in total?', 'what trip brought me here last time?'.

  • List stays

    List all stays across every moorage, with arrival/departure times, duration, and stay type (Anchor, Dock, Mooring Buoy). Each stay also includes the preceding log (what voyage brought you there) and the following log (what voyage you left on). Supports filtering by date range (arrived/departed), minimum duration, stay type, and pagination. Use for cross-location questions: 'show me all my anchor stays last month', 'longest stays this year', 'time spent docked vs anchored'.

  • Get stay details

    Get full details for a specific stay by ID: moorage information, arrival/departure times, duration, and stay type (anchor, dock, mooring buoy).

  • Get live vessel position and sensors

    Get the vessel's latest position, speed, heading, and sensor readings: wind, depth, battery, solar, temperature, humidity, pressure, and tank levels. Use to answer questions about where the vessel is now or its current conditions.

  • Get recent sensor history

    Retrieve historical sensor readings for the last 24h, 48h, 72h, or 7 days: battery charge/voltage, solar power, wind speed/direction, water temperature, depth, air temperature, humidity, and barometric pressure trend. Use to answer: 'how was my battery yesterday?', 'what was the wind doing overnight?', 'show me the pressure trend over the last 3 days'.

  • Get user profile and preferences

    Get user profile and preferences including name, unit system (imperial/metric), alert thresholds (low battery, high wind, low depth, pressure drop), and notification settings. Useful for understanding how the user has configured their monitoring and what limits trigger alerts.

  • Get voyage statistics summary

    Get aggregated voyage statistics for a time period: total trips, total distance sailed (NM), total time underway, personal records (max speed, max wind, longest passage), best 24h run, and top moorages by arrivals and duration. Use this to answer: 'how far have I sailed?', 'what was my best passage?', 'sailing summary for this year/season/month', 'how many trips did I do?', 'which countries have I visited?'. Defaults to all-time when no dates given.

  • Get vessel timelapse web player URL

    Returns a URL to the PostgSail timelapse web player showing the vessel's movement animated on a map. The player supports replay controls, speed adjustment, instruments overlay, satellite map, and 3D mode. Use when the user wants to visualize, animate, or replay one or multiple trips. Identify the trip range using get_logs or get_last_log. Provide log IDs (start_log / end_log) for a precise range, or dates (start_date / end_date) to span a period. Use the same value for start_log and end_log to r

  • Get sailing achievement badges

    Get achievements and earned badges based on voyage milestones: distance sailed, number of anchorages visited, night sailing, and other accomplishments.

  • Get moorage arrivals and departures

    Get all voyage logs that departed from or arrived at a specific moorage, identified by its ID. Returns log IDs, names, start/end times, and distance for each matching trip. Use when asked: 'which trips started from my home port?', 'what voyages brought me to this anchorage?', 'show me every trip that passed through [place]', 'trace all routes to/from this marina'. Obtain the moorage ID first from get_moorages, get_moorage, or get_log.

  • Get sailor and vessel context

    Returns personalised sailing context: sailor name, vessel details, lifetime stats (total trips, distance, countries), last 3 trips, favourite moorages, 30-day activity metrics, and alert preferences. PostgSail tracks: logbook (trips with GPS track, distance NM, speed knots), stays (anchor/dock/mooring buoy periods), moorages (named places clustered within 300m), and monitoring (live sensors: wind, depth, battery, solar, temperature, pressure, tanks). Use when asked: 'what data do you have?', 'wh

  • Get engine hours and service status

    Returns engine runtime statistics for the current vessel, computed from SignalK propulsion.%.runTime data stored per logbook entry. Returns four fields: • total_engine_hours: lifetime engine hours across all logbook entries. • last_30d_hours: engine hours in the last 30 days — useful for recent usage trends. • estimated_service_due_hours: the configured service interval in hours (default 200h, overridable via vessel preferences). Compare against total_engine_hours to determine if service is

  • Recommend sail configuration for current conditions

    Given wind conditions and the vessel's polar, recommend sail configuration (headsail, main, reefing) and point of sail. Returns has_polar (bool) — if false, advice is generic Beaufort-scale guidance only, not boat-specific. Returns polar_vmg_kn when a polar match is found and target_bearing_deg is provided. Use when asked: 'what sails should I set?', 'should I reef?', 'best angle to the wind for this passage?', 'will we be close-hauled?'.

  • Find community passages between two places

    Community passages between two geographic areas from sailors who opted into public sharing. Returns real passage stats: distance (NM), duration (hours), avg speed (knots), max wind (knots), vessel type. GEOCODING — resolve place names to coordinates before calling: • Use island or harbour CENTRE coordinates — radius_nm covers all departure points. • A single island spans multiple H3 cells; always use a large enough radius. RADIUS GUIDANCE: • 30nm: island-to-island Med or Baltic (Menorca, Mallo

  • Find community anchorages near a location

    Find anchorages, marinas, moorings, or docks near a position from the PostgSail community (sailors who opted into public data sharing). Returns name, stay type, distance, OSM data (wikidata, wikipedia, note, osm_url). GEOCODING — resolve place names to coordinates before calling: • 'near me' / 'nearby': call get_monitoring_live first for current lat/lon. • Named place: use geographic knowledge (Gothenburg ≈ 57.71°N 11.97°E; Ibiza ≈ 38.91°N 1.43°E). • Coordinates provided: use as-is. Use when a

Get your MCP into directories

A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.

Directory coverage for brands

Frequently Asked Questions

What is the Home OpenPlotter Cloud MCP server?

The open-source sailing platform. Save data in the cloud to access charts and graphs. Access anywhere. Your boat software to record, track, manage, report on your vessels

How do I connect Home OpenPlotter Cloud to my AI agent?

Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.

How many tools does Home OpenPlotter Cloud provide?

MCPBundles probed 28 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.

What authentication does Home OpenPlotter Cloud require?

Home OpenPlotter Cloud may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.

Maintain this listing

Operate Home OpenPlotter Cloud? Verify ownership to take over this directory entry.

Operate Home OpenPlotter Cloud?

This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.

Claim this listing