VoltSense MCP
Your fleet, in your AI assistant
Connect Claude — or any assistant that speaks the Model Context Protocol — to your VoltSense HUB account, and ask it things you would otherwise go looking for.
“Which boats need attention this morning?”
“Is the freezer on Triton still holding temperature?”
“Did anyone open the boat while I was away?”
“Show me Aurora's battery over the last month.”
https://mcp.voltsense.eu/mcpYou never copy or paste a password, key or token anywhere.
claude mcp add voltsense --transport http https://mcp.voltsense.eu/mcp
A browser window opens for the same sign-in and approval.
You choose these when you connect. Nothing outside the fleet you pick is visible.
Sign in to VoltSense HUB 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 session already in progress. We also e-mail you whenever a new connection is approved, so you would know about one you did not make.
| Tool | Answers |
|---|---|
list_boats | The fleet, worst-first, with the same status your dashboard shows |
get_boat | One boat's details, marina and berth |
get_battery_status | Current readings, each labelled as the boat's, the device's own, or signal |
get_measurement_history | Aggregated history for one measurement |
list_channels | What can be read at all, with units |
list_sensors | EYE sensors with readings and your own alarm limits |
get_sensor_history | History for one sensor |
get_door_events | When a door or hatch was opened |
| Endpoint | |
|---|---|
/mcp | MCP over streamable HTTP |
/.well-known/oauth-protected-resource/mcp | RFC 9728 resource metadata |
/healthz | Liveness |
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-checks which fleet, which permissions and
whether you have disconnected — on every single request. Refresh tokens
rotate; every call is recorded in an audit log.