VoltSense HUB Model Context Protocol Connect

Ask about the boats
in your care.

Connect Claude to your VoltSense HUB account and ask in plain words — batteries, sensors, alarms, maintenance. It can look at everything you approve, and change nothing at all.

Battery bank 1 — daily minimum

5 Jul – 9 Aug · one boat
15.0 14.0 11.9 11.0 11.07 V · 16 Jul 5 Jul 19 Jul · power back 9 Aug
What the assistant says about it “Bank 1 fell below the 11.9 V limit on 16, 17 and 18 July, reaching 11.07 V. Shore power was restored on the 19th and it has been at 14.03 V since — 23 days ago, not this week.”
Getting started

Connect in three steps

You never copy or paste a password, key or token anywhere.

STEP 1

Add the connector

In Claude, open Settings → Connectors and choose Add custom connector. Paste this URL.

https://mcp.voltsense.eu/mcp
STEP 2

Sign in at VoltSense

Claude sends you to the HUB to sign in with the account you already use. Your password never reaches Claude.

STEP 3

Choose a fleet, approve

Pick which fleet may be read and review the list of permissions. Nothing outside that fleet is visible.

Using Claude Code instead?

One command, then the same browser sign-in.

claude mcp add voltsense --transport http https://mcp.voltsense.eu/mcp

Changed your mind?

Sign in at hoiustaja.voltsense.eu and open Account → Connected apps. Every connection is listed with the fleet it covers and when it was last used. Removing one takes effect immediately, including for a conversation already in progress. We also e-mail you whenever a new connection is approved, so you would hear about one you did not make.

In practice

Things worth asking

Which boats need attention this morning? worst-first, with the status your dashboard shows
When did Aurora last lose shore power? answered on every boat — see below
What maintenance is still open across the yard? every boat, most urgent first
Is the freezer on Triton still holding temperature? judged against your own alarm limits
Did anyone open the boat while I was away? open-and-close episodes, with durations
Has anything knocked into Nordkapp since launch? the strongest jolt in each measurement cycle
Two answers we work out for you

Where the honest answer takes more than a reading

Shore power, without a shore-power sensor

Most boats have no wired shore-power sensor, and on those the raw channel reports something meaningless rather than nothing — which is worse. So the assistant is given a worked-out answer instead: from the sensor where one is fitted, and otherwise from whether the house bank is being held at charging voltage. It is told which of the two it got, and that the second cannot tell shore power apart from solar or a running engine. Expect it to say so too.

Leaning, and what it cannot tell you

The monitoring unit is fitted in whatever orientation suits the boat, so nothing in the data says which way is up relative to the hull. An assistant can tell you how far a boat has moved from her own resting attitude — useful if a cradle has shifted or a load has moved — but never which side she is leaning towards. If one claims to know, it is guessing.

Permissions

What it can read

You approve this list when you connect, one fleet at a time.

Your boatsNames, berth and marina, registration and owner details, and the alert status from your dashboard.
Battery & sensorsCurrent and historical battery voltage, shore power, bilge, temperature, cellular signal, and how hard the boat has been knocked or how far she is leaning.
Wireless sensorsEYE sensor readings: temperature, humidity, door contacts, sensor battery.
Alarm historyAlarms raised for your boats, with time, severity and cause.
Maintenance recordsTasks, their status and work hours, comments and history.
ManualsThe manuals attached to your boats, and links to them.
AI Guard findingsStatus, findings, written assessments and past analyses.
Account overviewYour licence, boat allowance, team members and marinas.
Limits, in plain words

What it cannot do

No writes

Read-only. It cannot create or change maintenance tasks, edit boats, alter settings or make payments. There is no write path to switch off — none exists.

No other fleets

Only the fleet you picked. A boat outside it does not read as forbidden; it reads as not there, because even its existence is not ours to confirm.

No positions

VoltSense does not track vessels. The position on your map is the berth you typed in. The monitoring device does report coordinates — we simply never ask for them, and no level of access changes that.

No credentials

Not your password, not your payment details, not the device's own access key. This server holds none of them itself, so a compromise of it leaks nothing you had not already approved.

Under the hood

The tools an assistant gets

Fifteen, one group per permission. An assistant picks the right one; you never name them yourself.

ToolAnswers
list_boatsThe fleet, worst-first, with the same status your dashboard shows
get_boatOne boat's details, marina and berth
get_battery_statusCurrent readings, each labelled as the boat's, the device's own, or signal
get_measurement_historyHistory for one measurement — voltages, temperature, signal, and the strongest knock in each cycle
get_shore_power_historyWhen a boat was and was not charging, on every boat
list_channelsWhat can be read at all, with units
get_alarm_historyAlarms already raised, each with how long ago it was
list_maintenanceEverything open across the fleet, most urgent first
get_boat_maintenanceOne boat's tasks, or one task with its comments and logged hours
get_manualsThe manuals attached to a boat
get_ai_guardThe overnight analysis: findings and the written assessment
get_accountYour licence, boat allowance, marinas and team
list_sensorsEYE sensors with readings and your own alarm limits
get_sensor_historyHistory for one sensor
get_door_eventsWhen a door or hatch was opened
For the technically minded

How the connection is secured

Authorisation is OAuth 2.1 with PKCE (S256) against hoiustaja.voltsense.eu, which issues short-lived RS256 access tokens bound to this resource. This server holds no credentials of its own: it verifies your token against the HUB's published signing key and forwards that same token, so the HUB re-decides which fleet, which permissions and whether you have disconnected — on every single request. Refresh tokens rotate; every call is recorded in an audit log.

Endpoints
/mcpMCP over streamable HTTP
/.well-known/oauth-protected-resource/mcpRFC 9728 resource metadata
/healthzLiveness

Not using VoltSense yet?
Start monitoring your fleet

Battery monitoring, maintenance records and alarms for marinas, storage yards and service companies. The assistant comes with it — see what VoltSense does.