Kuksa MCP Server
A Model Context Protocol (MCP) server that connects LLMs to vehicle data via the Eclipse Kuksa Databroker, enabling AI assistants to read and write vehicle signals using the standardized COVESA Vehicle Signal Specification.
README
Kuksa MCP Server
A Model Context Protocol (MCP) server that connects LLMs to vehicle data via the Eclipse Kuksa Databroker. Enables AI assistants to read and write vehicle signals using the standardized COVESA Vehicle Signal Specification (VSS).
Features
- Read signals — Get current or target values of any VSS signal
- Batch reads — Fetch multiple signals in a single call
- Write actuators — Set actuator targets or publish sensor readings
- Browse the VSS tree — List or count signals under any branch, with substring filtering
- Inspect types — Query data types for any signal path
- Server introspection — Name, version, signal count at startup
- Per-request logging — Every tool call logged with params, timing, and result summary
- Dual transport — stdio (default) and SSE (HTTP)
- OpenCode ready — Pre-configured
opencode.jsoncfor local and remote variants
Quick Start
1. Start a Kuksa Databroker
docker run -d --rm -p 55555:55555 --name kuksa-databroker \
ghcr.io/eclipse-kuksa/kuksa-databroker:main --insecure
2. Install & Run
pip install kuksa-mcp-server
kuksa-mcp
Or from source:
git clone https://github.com/mikehaller/kuksa-mcp-server.git
cd kuksa-mcp-server
pip install -e ".[dev]"
kuksa-mcp
3. Configure your MCP client
<details> <summary>Claude Desktop / Cursor (<code>claude_desktop_config.json</code>)</summary>
{
"mcpServers": {
"kuksa": {
"command": "kuksa-mcp"
}
}
}
</details>
<details> <summary>OpenCode — stdio variant (<code>opencode.jsonc</code> in project root)</summary>
{
"mcpServers": {
"kuksa-local": {
"type": "local",
"command": ["kuksa-mcp", "--log-file", "./kuksa-mcp.log"],
"enabled": true,
"timeout": 10000
}
}
}
</details>
<details> <summary>OpenCode — SSE variant (<code>opencode.jsonc</code> in project root)</summary>
{
"mcpServers": {
"kuksa-remote": {
"type": "remote",
"url": "http://127.0.0.1:8765/sse",
"enabled": false,
"timeout": 10000
}
}
}
</details>
OpenCode MCP Server Variants
The project ships with two entries in opencode.jsonc:
| Variant | Transport | Default | Use case |
|---|---|---|---|
kuksa-local |
stdio (subprocess) | enabled | Local dev, single-user, auto-managed |
kuksa-remote |
SSE (HTTP) | disabled | Multi-user, containerized, remote databroker |
Start the remote variant manually:
kuksa-mcp --transport sse --host 0.0.0.0 --port 8765
CLI Reference
kuksa-mcp [options]
Options:
--transport <stdio|sse> Transport protocol (default: stdio)
--host <ip> Bind address for SSE (default: 127.0.0.1)
--port <port> Port for SSE (default: 8765)
--kuksa-host <host> Databroker host (overrides KUKSA_HOST env)
--kuksa-port <port> Databroker port (overrides KUKSA_PORT env)
--log-file <path> File path for request logging (also written to stderr)
Environment Variables
| Variable | Default | Description |
|---|---|---|
KUKSA_HOST |
127.0.0.1 |
Kuksa Databroker host |
KUKSA_PORT |
55555 |
Kuksa Databroker gRPC port |
KUKSA_TOKEN |
(none) | JWT token for authorization |
Tools
| Tool | API | Description |
|---|---|---|
get_signal(path) |
Kuksa V2 | Get current value of one VSS signal |
get_signals(paths) |
Kuksa V2 | Get current values of multiple signals |
set_signal(path, value, datatype) |
Kuksa V2 | Set an actuator target value |
publish_value(path, value, datatype) |
Kuksa V2 | Publish a sensor reading (provider role) |
list_signals(branch, query) |
V1 (deprecated) | List signals and metadata under a branch |
count_signals(branch, query) |
V1 (deprecated) | Count signals matching a filter |
get_target_values(paths) |
V1 (deprecated) | Read actuator target/desired values |
get_value_types(paths) |
V1 (deprecated) | Get data types for one or more signals |
server_info() |
V1 (deprecated) | Get databroker name, version, address |
Resources
| URI | Description |
|---|---|
kuksa://info |
Server and tool reference |
kuksa://signals/{path} |
Signal info (redirects to tool) |
kuksa://branches/{path} |
Branch listing (redirects to tool) |
Startup Output
On startup the server prints a banner with version, databroker info, and catalog stats:
======================================================
Kuksa Databroker MCP Server
Version : 0.1.0
Built : 2026-06-24
======================================================
Backend : databroker
Address : 127.0.0.1:55555
Version : 0.7.0-dev.0
Status : connected
Signals : 1263 total
Types : ACTUATOR=643, ATTRIBUTE=130, SENSOR=490
======================================================
Every tool call is logged:
09:45:12 [INFO] Processing request of type ListToolsRequest
09:45:12 [INFO] Processing request of type CallToolRequest
09:45:12 [INFO] get_signal(args={'path': 'Vehicle.Speed'}) -> ok [0.023s]
09:45:15 [INFO] list_signals(args={'branch': 'Vehicle.Cabin', 'query': ''}) -> 490 results [0.045s]
Development
pip install -e ".[dev]"
pytest
kuksa-mcp --transport sse
python examples/local_test.py
Docker
The server is published as a Docker image on GitHub Container Registry:
docker pull ghcr.io/mikehaller/kuksa-mcp-server:latest
# Run with SSE transport
docker run --rm -p 8765:8765 \
-e KUKSA_HOST=host.docker.internal \
ghcr.io/mikehaller/kuksa-mcp-server:latest \
--transport sse --host 0.0.0.0 --port 8765
The image uses a non-root kuksa user and is built from python:3.12-slim (~200 MB).
License
Apache 2.0 — see LICENSE.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。