SignalK MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SignalK MCP ServerShow me the 3 closest AIS targets to my vessel"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SignalK MCP Server
A Model Context Protocol (MCP) server that provides AI agents with efficient access to SignalK marine data using code execution in V8 isolates. This approach reduces token usage by 90-96% compared to traditional MCP tools.
🚀 Version 1.0.6: Now using code execution engine for massive token savings! See CHANGELOG.md for details.
Why Code Execution?
Traditional MCP tools return ALL data to the AI, consuming massive amounts of tokens. This server uses V8 isolates (like Cloudflare Workers) to let AI agents run JavaScript code that filters data before returning it.
Token Savings:
Vessel state queries: 94% reduction (2,000 → 120 tokens)
AIS target filtering: 95% reduction (10,000 → 500 tokens)
Multi-call workflows: 97% reduction (13,000 → 300 tokens)
Quick Start
Installation
# Via npx (recommended)
npx signalk-mcp-server
# Or install globally
npm install -g signalk-mcp-serverClaude Desktop Configuration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"signalk": {
"command": "npx",
"args": ["signalk-mcp-server"],
"env": {
"SIGNALK_HOST": "localhost",
"SIGNALK_PORT": "3000",
"SIGNALK_TLS": "false"
}
}
}
}Basic Usage
AI Agent Query: "What's my vessel's position and the 3 closest AIS targets?"
Code Execution (Automatic):
(async () => {
// Get vessel position
const vessel = await getVesselState();
const position = vessel.data["navigation.position"]?.value;
// Get AIS targets and filter in isolate
const ais = await getAisTargets({ pageSize: 50 });
const closest = ais.targets.slice(0, 3);
return JSON.stringify({ position, closest });
})()
// Returns: ~300 tokens (97% savings vs legacy tools!)Features
Code Execution Engine
V8 Isolate Sandbox: Secure JavaScript execution
Client-side Filtering: Process data before returning to AI
Multiple API Calls: Combine operations in one execution
90-96% Token Savings: Massive reduction in context window usage
Sub-100ms Overhead: Fast execution with memory/timeout limits
Available SDK Functions
When using execute_code, these functions are available. IMPORTANT: ALL functions are async and MUST be awaited:
// Vessel data
const vessel = await getVesselState();
// AIS targets (with pagination and optional distance filter)
const ais = await getAisTargets({ page: 1, pageSize: 50, maxDistance: 5000 });
// System alarms
const alarms = await getActiveAlarms();
// Discover available data paths
const paths = await listAvailablePaths();
// Get specific path value (both string and object syntax work)
const speed = await getPathValue("navigation.speedOverGround");
const heading = await getPathValue({ path: "navigation.headingTrue" });
// Connection status - ALSO requires await!
const status = await getConnectionStatus();Real-time Marine Data
Vessel position, heading, speed, wind
AIS target tracking with distance calculations
System notifications and alarms
Dynamic SignalK path discovery
Connection health monitoring
Configuration
Environment Variables
# SignalK Connection (Required)
SIGNALK_HOST=localhost # SignalK server hostname/IP
SIGNALK_PORT=3000 # SignalK server port
SIGNALK_TLS=false # Use WSS/HTTPS (true/false)
# Execution Mode (Optional)
EXECUTION_MODE=code # code (default) | tools (legacy) | hybrid
# Optional Settings
SERVER_NAME=signalk-mcp-server
SERVER_VERSION=1.0.6Execution Modes
Mode | Description | Use Case |
code (default) | V8 isolate execution only | Production use, maximum efficiency |
tools | Legacy MCP tools | Backward compatibility |
hybrid | Both approaches available | Migration period |
Examples
Example 1: Filtered Vessel Data
Query: "Get my vessel name and position"
Code:
(async () => {
const vessel = await getVesselState();
return JSON.stringify({
name: vessel.data.name?.value,
position: vessel.data["navigation.position"]?.value
});
})()Result: ~200 tokens (vs 2,000 with legacy tools)
Example 2: Nearby Vessels
Query: "Show vessels within 1 nautical mile"
Code:
(async () => {
const ais = await getAisTargets({ pageSize: 50 });
// Filter in isolate - huge savings!
const nearby = ais.targets.filter(t =>
t.distanceMeters && t.distanceMeters < 1852
);
return JSON.stringify({
total: ais.count,
nearby: nearby.length,
vessels: nearby.slice(0, 5)
});
})()Result: ~300 tokens (vs 10,000 with legacy tools)
Example 3: Critical Alarms Only
Query: "Any critical alarms?"
Code:
(async () => {
const alarms = await getActiveAlarms();
const critical = alarms.alarms.filter(a =>
a.state === "alarm" || a.state === "emergency"
);
return JSON.stringify({
hasCritical: critical.length > 0,
count: critical.length,
details: critical
});
})()Result: ~100 tokens (vs 1,000 with legacy tools)
Example 4: Multi-Call Workflow
Query: "Give me a situation report"
Code:
(async () => {
// All calls in ONE execution!
const vessel = await getVesselState();
const ais = await getAisTargets({ pageSize: 50 });
const alarms = await getActiveAlarms();
// Process everything in isolate
const closeVessels = ais.targets.filter(t =>
t.distanceMeters && t.distanceMeters < 1852
).length;
const criticalAlarms = alarms.alarms.filter(a =>
a.state === "alarm" || a.state === "emergency"
).length;
return JSON.stringify({
position: vessel.data["navigation.position"]?.value,
speed: vessel.data["navigation.speedOverGround"]?.value,
vesselsNearby: closeVessels,
criticalAlarms: criticalAlarms
});
})()Result: ~300 tokens (vs 13,000 with 3 separate tool calls!)
Development
Prerequisites
Node.js 18.0.0 or higher
Access to a SignalK server
Setup
# Clone repository
git clone <repository-url>
cd signalk-mcp-server
# Install dependencies
npm install
# Build
npm run build
# Run tests
npm run test:unit
# Run in development mode
npm run devTesting
# Unit tests (fast)
npm run test:unit
# Integration tests (requires live SignalK server)
npm run test:e2e
# Full CI pipeline
npm run ciArchitecture
Code Execution Flow
AI Agent
↓
execute_code tool
↓
V8 Isolate Sandbox (isolated-vm)
↓
SignalK SDK Functions (all async, must await)
↓
SignalK Binding Layer (RPC-style)
↓
SignalK Client (HTTP REST API)
↓
SignalK ServerNote: HTTP-only mode ensures fresh data on every request. WebSocket code is preserved for future streaming support.
Key Components
Isolate Sandbox (
src/execution-engine/isolate-sandbox.ts): Secure V8 isolate executionSignalK Binding (
src/bindings/signalk-binding.ts): RPC-style method invocationSDK Generator (
src/sdk/generator.ts): Auto-generates SDK from tool definitionsSignalK Client (
src/signalk-client.ts): HTTP/WebSocket client for SignalK
Security
Complete Isolation: No access to Node.js globals
Memory Limits: 128MB per execution
Timeout Protection: 30s maximum execution time
No Credential Exposure: SignalK auth handled by binding layer
Read-Only: No write operations to SignalK server
Migration from 1.x
Breaking Changes
Version 1.0.6 changes the default mode from hybrid to code. Legacy tools are no longer available by default.
Backward Compatibility
To use legacy tools, set the execution mode:
{
"mcpServers": {
"signalk": {
"env": {
"EXECUTION_MODE": "tools"
}
}
}
}Migration Guide
See TOOL-MIGRATION-GUIDE.md for complete migration examples.
Before (Legacy):
Tool: get_vessel_state
Returns: All vessel data (~2000 tokens)After (Code):
(async () => {
const vessel = await getVesselState();
return JSON.stringify({
name: vessel.data.name?.value,
position: vessel.data["navigation.position"]?.value
});
})()
// Returns: ~200 tokensTroubleshooting
Connection Issues
Check connection status (note: await is required):
(async () => {
const status = await getConnectionStatus(); // await is required!
return JSON.stringify(status);
})()Legacy Mode
If you need legacy tools temporarily:
EXECUTION_MODE=tools npx signalk-mcp-serverDebug Mode
Enable verbose logging:
DEBUG=true
LOG_LEVEL=debugContributing
Contributions welcome! Please see CONTRIBUTING.md for guidelines.
License
MIT License - see LICENSE for details.
Resources
CHANGELOG.md - Version history and migration guide
TOOL-MIGRATION-GUIDE.md - Detailed migration examples
Credits
Built with:
isolated-vm - V8 isolate execution
@modelcontextprotocol/sdk - MCP TypeScript SDK
SignalK community for the excellent marine data protocol
🚢 Happy sailing with AI-powered marine data!
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/VesselSense/signalk-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server