Permet à un agent IA de gérer des jumeaux numériques, notamment les objets, les attributs, les politiques, les connexions et l'administration de clusters via l'API HTTP de Ditto.
Aussi connu sous nagarjunr/iot-mcp-servers, eclipse-ditto, eclipse-ditto-mcp-server
- Étoiles
- 0
- Outils
- —
- Téléchargements, 30 jours
- 85
- Dernière version
- 0.1.1
- Dernier commit
- 31 oct. 2026
- Licence
- MIT
Qu'est-ce que Eclipse Ditto MCP ?
Permet à un agent IA de gérer des jumeaux numériques, notamment les objets, les attributs, les politiques, les connexions et l'administration de clusters via l'API HTTP de Ditto.
Résumé généré à partir du README du projet
À propos du MCP server Eclipse Ditto
La gestion des jumeaux numériques et de l'état des appareils IoT via un agent IA est possible grâce à ce MCP server Eclipse Ditto. Il sert de passerelle vers l'intégralité de l'API HTTP d'Eclipse Ditto, permettant aux utilisateurs d'interagir avec les objets, les attributs, les fonctionnalités et les politiques. Le serveur est conçu pour fonctionner avec n'importe quel déploiement respectant le protocole ouvert, y compris des plateformes commerciales comme Bosch IoT Things.
Les développeurs peuvent utiliser ce serveur localement ou via des passerelles distantes en configurant des variables d'environnement telles que DITTO_BASE_URL. L'authentification est gérée via des identifiants Basic auth ou un bearer token. Pour les tâches administratives avancées impliquant la connectivité et la configuration de clusters, des identifiants DevOps distincts sont requis. L'ensemble d'outils inclut des commandes spécifiques pour rechercher des objets avec des expressions RQL, envoyer des messages en direct aux appareils et gérer les métriques de connexion.
La sécurité est intégrée à la conception de l'outil grâce à des étapes de confirmation pour toutes les opérations de suppression et une logique de création sans conflit (race-free). Il offre également un moyen d'approximer les flux d'événements en direct en interrogeant les modifications sur une durée spécifiée. Cela en fait une interface polyvalente, tant pour la gestion courante des appareils que pour l'administration DevOps de bas niveau.
Ce que vous pouvez faire avec
- 1Mettre à jour les données des capteurs d'un appareilVous pouvez ordonner à une IA de modifier des propriétés ou des fonctionnalités spécifiques d'un jumeau numérique.
- 2Déclencher des opérations sur un appareil à distanceUn agent peut envoyer des messages en direct à un objet ou une fonctionnalité pour invoquer une opération spécifique.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Eclipse Ditto MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller Eclipse Ditto MCP dans Claude Code
$ claude mcp add --env 'DITTO_BASE_URL=<DITTO_BASE_URL>' --env 'DITTO_BEARER_TOKEN=<YOUR_DITTO_BEARER_TOKEN>' --env 'DITTO_DEVOPS_PASSWORD=<YOUR_DITTO_DEVOPS_PASSWORD>' --env 'DITTO_PASSWORD=<YOUR_DITTO_PASSWORD>' eclipse-ditto -- uvx eclipse-ditto-mcp-serverInstaller Eclipse Ditto MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"eclipse-ditto": {
"command": "uvx",
"args": [
"eclipse-ditto-mcp-server"
],
"env": {
"DITTO_BASE_URL": "<DITTO_BASE_URL>",
"DITTO_BEARER_TOKEN": "<YOUR_DITTO_BEARER_TOKEN>",
"DITTO_DEVOPS_PASSWORD": "<YOUR_DITTO_DEVOPS_PASSWORD>",
"DITTO_PASSWORD": "<YOUR_DITTO_PASSWORD>"
}
}
}
}Installer Eclipse Ditto MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"eclipse-ditto": {
"type": "stdio",
"command": "uvx",
"args": [
"eclipse-ditto-mcp-server"
],
"env": {
"DITTO_BASE_URL": "<DITTO_BASE_URL>",
"DITTO_BEARER_TOKEN": "<YOUR_DITTO_BEARER_TOKEN>",
"DITTO_DEVOPS_PASSWORD": "<YOUR_DITTO_DEVOPS_PASSWORD>",
"DITTO_PASSWORD": "<YOUR_DITTO_PASSWORD>"
}
}
}
}Installer Eclipse Ditto MCP dans VS Code CLI
$ code --add-mcp '{"name":"eclipse-ditto","type":"stdio","command":"uvx","args":["eclipse-ditto-mcp-server"],"env":{"DITTO_BASE_URL":"<DITTO_BASE_URL>","DITTO_BEARER_TOKEN":"<YOUR_DITTO_BEARER_TOKEN>","DITTO_DEVOPS_PASSWORD":"<YOUR_DITTO_DEVOPS_PASSWORD>","DITTO_PASSWORD":"<YOUR_DITTO_PASSWORD>"}}'Installer Eclipse Ditto MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"eclipse-ditto": {
"command": "uvx",
"args": [
"eclipse-ditto-mcp-server"
],
"env": {
"DITTO_BASE_URL": "<DITTO_BASE_URL>",
"DITTO_BEARER_TOKEN": "<YOUR_DITTO_BEARER_TOKEN>",
"DITTO_DEVOPS_PASSWORD": "<YOUR_DITTO_DEVOPS_PASSWORD>",
"DITTO_PASSWORD": "<YOUR_DITTO_PASSWORD>"
}
}
}
}Installer Eclipse Ditto MCP dans Codex
$ codex mcp add eclipse-ditto --env 'DITTO_BASE_URL=<DITTO_BASE_URL>' --env 'DITTO_BEARER_TOKEN=<YOUR_DITTO_BEARER_TOKEN>' --env 'DITTO_DEVOPS_PASSWORD=<YOUR_DITTO_DEVOPS_PASSWORD>' --env 'DITTO_PASSWORD=<YOUR_DITTO_PASSWORD>' -- uvx eclipse-ditto-mcp-serverInstaller Eclipse Ditto MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.eclipse-ditto] command = "uvx" args = ["eclipse-ditto-mcp-server"] [mcp_servers.eclipse-ditto.env] DITTO_BASE_URL = "<DITTO_BASE_URL>" DITTO_BEARER_TOKEN = "<YOUR_DITTO_BEARER_TOKEN>" DITTO_DEVOPS_PASSWORD = "<YOUR_DITTO_DEVOPS_PASSWORD>" DITTO_PASSWORD = "<YOUR_DITTO_PASSWORD>"
Installer Eclipse Ditto MCP dans Gemini CLI
$ gemini mcp add -s user -e 'DITTO_BASE_URL=<DITTO_BASE_URL>' -e 'DITTO_BEARER_TOKEN=<YOUR_DITTO_BEARER_TOKEN>' -e 'DITTO_DEVOPS_PASSWORD=<YOUR_DITTO_DEVOPS_PASSWORD>' -e 'DITTO_PASSWORD=<YOUR_DITTO_PASSWORD>' eclipse-ditto uvx -- eclipse-ditto-mcp-serverInstaller Eclipse Ditto MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"eclipse-ditto": {
"command": "uvx",
"args": [
"eclipse-ditto-mcp-server"
],
"env": {
"DITTO_BASE_URL": "<DITTO_BASE_URL>",
"DITTO_BEARER_TOKEN": "<YOUR_DITTO_BEARER_TOKEN>",
"DITTO_DEVOPS_PASSWORD": "<YOUR_DITTO_DEVOPS_PASSWORD>",
"DITTO_PASSWORD": "<YOUR_DITTO_PASSWORD>"
}
}
}
}Configuration
DITTO_BASE_URLRequisBase URL of the Ditto HTTP API, e.g. http://localhost:8080
DITTO_BEARER_TOKENSecretBearer token, used instead of Basic auth for the same API
DITTO_DEVOPS_PASSWORDSecretBasic auth password for the separate DevOps/Connections realm
DITTO_PASSWORDSecretBasic auth password for the Things/Policies/Messages/Search API
DITTO_DEVOPS_USERNAMEBasic auth username for the separate DevOps/Connections realm
DITTO_USERNAMEBasic auth username for the Things/Policies/Messages/Search API
| Nom | Description | Type |
|---|---|---|
| DITTO_BASE_URL | Base URL of the Ditto HTTP API, e.g. http://localhost:8080 | Requis |
| DITTO_BEARER_TOKEN | Bearer token, used instead of Basic auth for the same API | Secret |
| DITTO_DEVOPS_PASSWORD | Basic auth password for the separate DevOps/Connections realm | Secret |
| DITTO_PASSWORD | Basic auth password for the Things/Policies/Messages/Search API | Secret |
| DITTO_DEVOPS_USERNAME | Basic auth username for the separate DevOps/Connections realm | |
| DITTO_USERNAME | Basic auth username for the Things/Policies/Messages/Search API |
Vérifications automatisées
Exécuté le 13 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessiblenagarjunr/iot-mcp-servers is public and reachablegithub.com/nagarjunr/iot-mcp-servers ↗Réussi
- Le nom du package correspond au dépôt sourceeclipse-ditto-mcp-server names nagarjunr/iot-mcp-servers as sourcepypi.org/project/eclipse-ditto-mcp-server/ ↗Réussi
- Provenance du build (attestation Sigstore)No build attestation published for this releaseNon vérifié
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-10-31github.com/nagarjunr/iot-mcp-servers ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNo popular package one edit away from eclipse-ditto-mcp-serverRéussi
- Aucun avis critique dans le package ou ses dépendances65 resolved dependencies checked; no critical advisoryosv.dev ↗Réussi
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubEclipse Ditto MCP Server
A Model Context Protocol (MCP) server for Eclipse Ditto — the open-source (EPL-2.0) digital twin framework. It exposes Ditto's HTTP API as MCP tools so an AI agent can manage devices ("things"), their attributes/features, policies, connections, and cluster admin — the full Ditto HTTP API surface.
Since Bosch IoT Things and other commercial IoT platforms are built on Ditto's open protocol, this server also works against those deployments — nothing in the code is vendor-specific.
Built with FastMCP.
Tools
Things
| Tool | Description |
|---|---|
list_things(namespaces, filter, fields, limit) |
Search/list things. filter is a Ditto RQL expression, e.g. eq(attributes/location,"lab-1"). |
count_things(namespaces, filter) |
Count things matching a filter without fetching them. |
get_things(thing_ids, fields) |
Bulk-fetch multiple things by ID in one request. |
get_thing(thing_id, fields) |
Fetch the full digital twin for one thing. |
put_thing(thing_id, thing, overwrite=False) |
Create a thing, or replace one with overwrite=True. |
patch_thing(thing_id, patch) |
Partially update a thing via RFC-7396 JSON Merge Patch. |
delete_thing(thing_id, confirm=False) |
Delete a thing. Irreversible. |
get_thing_policy_id / set_thing_policy_id |
Read/repoint the policy controlling a thing. |
get_thing_definition / set_thing_definition / delete_thing_definition |
Manage a thing's WoT/model definition. |
whoami() |
Return the identity Ditto authenticated this connector as — useful to sanity-check credentials. |
Attributes & Features
| Tool | Description |
|---|---|
get_thing_attributes(thing_id, path=None) |
Get all attributes, or one by JSON pointer path. |
set_thing_attributes(thing_id, value, path=None, overwrite=False) |
Set the whole attributes object, or one attribute. |
delete_thing_attributes(thing_id, path=None, confirm=False) |
Delete attributes (whole object or one path). |
get_thing_features(thing_id) |
Get all features (sensor/actuator state). |
get_feature / put_feature / delete_feature |
Read/create-replace/delete one whole feature. |
get_feature_properties / set_feature_properties / delete_feature_properties |
Read/write/delete feature properties or desiredProperties, whole or by path. |
get_feature_definition / set_feature_definition / delete_feature_definition |
Manage a feature's definition. |
Messages
| Tool | Description |
|---|---|
send_message(thing_id, subject, payload, feature_id=None, direction="inbox", timeout=10) |
Send a live message to/from a thing or feature (e.g. invoke a device operation). |
claim_thing(thing_id, payload=None, timeout=10) |
Send a claim message to gain access to a thing. |
Policies
| Tool | Description |
|---|---|
get_policy / put_policy / delete_policy |
Read/create-replace/delete a policy. |
get_policy_entries(policy_id, label=None) |
Read all entries, or one by label. |
set_policy_entry / delete_policy_entry |
Create-replace/delete one policy entry. |
Connectivity & DevOps (require DITTO_DEVOPS_USERNAME/DITTO_DEVOPS_PASSWORD)
Ditto's Connections API and DevOps API (log levels, cluster config, piggyback commands) sit behind a separate "devops" Basic-auth realm on the gateway, independent of the policy-based auth used for things/policies.
| Tool | Description |
|---|---|
list_connections / get_connection |
List/fetch connection configs. |
create_connection(connection, dry_run=False) |
Create a connection (ID generated by Ditto). |
update_connection(connection_id, connection) |
Update an existing connection (404 if it doesn't exist). |
delete_connection(connection_id, confirm=False) |
Delete a connection. |
get_connection_status / get_connection_metrics / get_connection_logs |
Inspect a connection's live state. |
send_connection_command(connection_id, command) |
Open/close/reset-metrics/enable-logs/reset-logs. |
get_logging_config / set_logging_config |
Read/set cluster log levels. |
get_devops_config(path) |
Read cluster-wide runtime config. |
send_devops_piggyback(command, service_name=None, instance_index=None) |
Low-level admin command — Ditto's most powerful, least-guarded API. Use with care. |
Live events
| Tool | Description |
|---|---|
poll_thing_changes(thing_ids, namespaces, filter, fields, duration_seconds=10, max_events=50) |
Open a short-lived SSE connection and collect live thing-change events. A request/response approximation of Ditto's persistent change feed — see caveat below. |
Safety conventions
- Create vs. replace: every
put_*/set_*/create_*tool defaults tooverwrite=False, using Ditto'sIf-None-Match: *header so create-only is race-free (not a check-then-set). Passoverwrite=Trueto replace existing data. - Deletes are confirm-gated: every
delete_*tool requiresconfirm=True. There is no bulk/cascading delete. - Not covered (deliberately): WoT Web-of-Things descriptor endpoints (
/.well-known/wot,/devops/wot/*), and fine-grained policy sub-resources (subjects/{id},resources/{path},imports, token-integration actions) — whole-entryset_policy_entry/get_policy_entriescovers the common case. Add these later if you need them.
Configuration
| Env var | Required | Description |
|---|---|---|
DITTO_BASE_URL |
Yes | Base URL of the Ditto HTTP API, e.g. http://localhost:8080 or your gateway's public URL. |
DITTO_USERNAME / DITTO_PASSWORD |
No | Basic auth for the Things/Policies/Messages/Search API. Typical for self-hosted Ditto (nginx demo setup uses ditto/ditto). |
DITTO_BEARER_TOKEN |
No | Bearer token, used instead of Basic auth for the same API. Typical for OAuth2-fronted deployments (e.g. Bosch IoT Things). |
DITTO_DEVOPS_USERNAME / DITTO_DEVOPS_PASSWORD |
No | Basic auth for the separate DevOps/Connections realm (self-hosted default: devops/foobar). Required only for the Connectivity and DevOps tools. |
If both DITTO_BEARER_TOKEN and Basic auth credentials are set, the bearer token takes precedence. If neither is set, requests are sent unauthenticated (only works if your Ditto instance allows anonymous/pre-authenticated access).
Running locally
uv sync
export DITTO_BASE_URL=http://localhost:8080
export DITTO_USERNAME=ditto
export DITTO_PASSWORD=ditto
export DITTO_DEVOPS_USERNAME=devops # only needed for connectivity/devops tools
export DITTO_DEVOPS_PASSWORD=foobar
uv run dittomcpserver.py
See mcp.json for ready-to-use client configs (stdio and Docker).
Testing against a real Ditto instance
This repo's design principles call for testing against a real instance rather than mocks. docker-compose.yml (adapted from Ditto's official example, trimmed to the services this connector needs) spins up a full local Ditto stack — MongoDB, the Ditto microservices, and an nginx front door with Basic auth.
docker compose up -d # start Ditto on http://localhost:8080 (user: ditto / pass: ditto; devops: devops / foobar)
uv run pytest -v # tests/conftest.py also starts/stops the stack automatically
docker compose down # stop it manually if you started it yourself
The 47 tests cover every tool group (things, attributes/features, messages, policies, connectivity, devops, live events) against this real stack, including delete/confirm gating and create/overwrite gating.
A note on the live-events approximation
poll_thing_changes opens Ditto's SSE change feed for a bounded window instead of holding a persistent subscription (which doesn't map cleanly onto a single MCP tool call). Ditto's SSE stream sends periodic empty data: keepalive lines even when nothing has changed — the tool checks its deadline on every line received, including keepalives, so it reliably returns within duration_seconds regardless of how chatty or quiet the stream is.
License notes
docker-compose.yml and the files under docker/ are adapted from the Eclipse Ditto project (EPL-2.0) and are used here only to spin up a local test instance — they are not part of the MCP server itself.
Questions sur Eclipse Ditto MCP
Comment ajouter Eclipse Ditto MCP à Claude Code ?
Exécutez claude mcp add --env 'DITTO_BASE_URL=<DITTO_BASE_URL>' --env 'DITTO_BEARER_TOKEN=<YOUR_DITTO_BEARER_TOKEN>' --env 'DITTO_DEVOPS_PASSWORD=<YOUR_DITTO_DEVOPS_PASSWORD>' --env 'DITTO_PASSWORD=<YOUR_DITTO_PASSWORD>' eclipse-ditto -- uvx eclipse-ditto-mcp-server dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Eclipse Ditto MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Le serveur prend-il en charge la surveillance d'événements en temps réel ?
Oui, il peut interroger les événements de modification d'objets en direct en utilisant une connexion SSE à courte durée de vie.