Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
MCP server for the Eclipse Ditto digital twin HTTP API (things, policies, connections, more).
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
DITTO_BASE_URL, DITTO_USERNAME, DITTO_PASSWORD, DITTO_BEARER_TOKEN, DITTO_DEVOPS_USERNAME, DITTO_DEVOPS_PASSWORDLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"eclipse-ditto": {
"command": "uvx",
"args": [
"eclipse-ditto-mcp-server"
],
"env": {
"DITTO_BASE_URL": "your-value",
"DITTO_USERNAME": "your-value",
"DITTO_PASSWORD": "your-value",
"DITTO_BEARER_TOKEN": "your-value",
"DITTO_DEVOPS_USERNAME": "your-value",
"DITTO_DEVOPS_PASSWORD": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add eclipse-ditto --env DITTO_BASE_URL=your-value --env DITTO_USERNAME=your-value --env DITTO_PASSWORD=your-value --env DITTO_BEARER_TOKEN=your-value --env DITTO_DEVOPS_USERNAME=your-value --env DITTO_DEVOPS_PASSWORD=your-value -- uvx eclipse-ditto-mcp-serverCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"eclipse-ditto": {
"command": "uvx",
"args": [
"eclipse-ditto-mcp-server"
],
"env": {
"DITTO_BASE_URL": "your-value",
"DITTO_USERNAME": "your-value",
"DITTO_PASSWORD": "your-value",
"DITTO_BEARER_TOKEN": "your-value",
"DITTO_DEVOPS_USERNAME": "your-value",
"DITTO_DEVOPS_PASSWORD": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"eclipse-ditto": {
"type": "stdio",
"command": "uvx",
"args": [
"eclipse-ditto-mcp-server"
],
"env": {
"DITTO_BASE_URL": "your-value",
"DITTO_USERNAME": "your-value",
"DITTO_PASSWORD": "your-value",
"DITTO_BEARER_TOKEN": "your-value",
"DITTO_DEVOPS_USERNAME": "your-value",
"DITTO_DEVOPS_PASSWORD": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
DITTO_USERNAME envDITTO_DEVOPS_USERNAME envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub nagarjunr, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: DITTO_BASE_URL, DITTO_PASSWORD, DITTO_BEARER_TOKEN, DITTO_DEVOPS_PASSWORD
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.1) llegó al registro hace 3 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, AI Deprecations
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
| 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. |
| 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. |
| 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. |
| 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. |
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. |
| 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. |
put_*/set_*/create_* tool defaults to overwrite=False, using Ditto's If-None-Match: * header so create-only is race-free (not a check-then-set). Pass overwrite=True to replace existing data.delete_* tool requires confirm=True. There is no bulk/cascading delete./.well-known/wot, /devops/wot/*), and fine-grained policy sub-resources (subjects/{id}, resources/{path}, imports, token-integration actions) — whole-entry set_policy_entry/get_policy_entries covers the common case. Add these later if you need them.| 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).
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).
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.
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.
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.