dosync 0.6.2__tar.gz → 0.6.3__tar.gz

{dosync-0.6.2 → dosync-0.6.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dosync
-Version: 0.6.2
+Version: 0.6.3
 Summary: The semantic layer between AI agents and physical devices
 Author-email: Rodrigo Giuliani <rgiuliani@dosync.dev>
 License-Expression: Apache-2.0
@@ -45,7 +45,7 @@ Requires-Dist: twilio>=8.0.0; extra == "sms"
 Provides-Extra: mavlink
 Requires-Dist: pymavlink>=2.4.0; extra == "mavlink"
 Provides-Extra: mcp
-Requires-Dist: mcp>=1.0.0; extra == "mcp"
+Requires-Dist: mcp<2.0,>=1.0.0; extra == "mcp"
 Provides-Extra: all
 Requires-Dist: pywizlight>=0.5.0; extra == "all"
 Requires-Dist: paho-mqtt>=2.0.0; extra == "all"
@@ -53,7 +53,7 @@ Requires-Dist: aiohttp>=3.9.0; extra == "all"
 Requires-Dist: bleak>=0.21; extra == "all"
 Requires-Dist: twilio>=8.0.0; extra == "all"
 Requires-Dist: pymavlink>=2.4.0; extra == "all"
-Requires-Dist: mcp>=1.0.0; extra == "all"
+Requires-Dist: mcp<2.0,>=1.0.0; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest>=7.4; extra == "dev"
 Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
@@ -788,6 +788,130 @@ test, so it is named rather than recommended.
 
 ---
 
+## Connecting an agent
+
+This page has said "MCP" a dozen times — a badge at the top, a section on why
+MCP is the channel rather than the rival, a drone that flew a mission through
+it — and never once explained how to connect an agent. This is that.
+
+DoSync ships an MCP server. It is not a separate product: it exposes the hub's
+intents and devices as tools, and every call it makes lands in the same policy
+engine and the same audit chain as a call from `curl`. An agent that reaches a
+device through it is governed exactly like anything else.
+
+### What DoSync provides
+
+The server is a module rather than a command, and it needs the MCP SDK, which
+the hub does not install:
+
+```bash
+pip install "mcp>=1.0.0,<2.0"       # or: pipx inject dosync "mcp>=1.0.0,<2.0"
+python -m dosync.mcp_server
+```
+
+The upper bound is not caution. The 2.x SDK changed how tools are registered
+and this server is written against 1.x; without the cap, a fresh install gets
+2.x and the server exits at import. It says so plainly if that happens.
+
+It speaks over stdin/stdout, so a successful start prints nothing and waits.
+Typing into that terminal will produce JSON parse errors — that is the protocol
+rejecting your keystrokes, not a fault.
+
+It reads three environment variables:
+
+| Variable | Meaning |
+|---|---|
+| `DOSYNC_HUB_URL` | Where the hub is. Default `http://localhost:47200` |
+| `DOSYNC_TOKEN` | The hub's bearer token |
+| `DOSYNC_CA_CERT` | CA certificate, when the hub runs over TLS |
+
+That is the whole of DoSync's side. Everything below is about getting a client
+to launch that command — which is the client's business, not the protocol's.
+
+### What the client provides
+
+MCP clients are configured with a JSON file naming a command to run and the
+environment to run it in. The shape is standard:
+
+```json
+{
+  "mcpServers": {
+    "dosync": {
+      "command": "/absolute/path/to/python",
+      "args": ["-m", "dosync.mcp_server"],
+      "env": {
+        "DOSYNC_HUB_URL": "http://localhost:47200",
+        "DOSYNC_TOKEN": "your-token-here"
+      }
+    }
+  }
+}
+```
+
+**That file holds a credential.** It grants whatever the token grants. This
+project shipped a live token in a public repository for three months, so the
+warning is not rhetorical: keep it out of version control and off shared
+drives.
+
+Use an absolute path to the interpreter that has DoSync installed. A client
+launches the command with its own environment, not yours, so `python` may not
+resolve to what you expect. With `pipx`, the interpreter is inside its venv —
+on Linux and macOS `~/.local/share/pipx/venvs/dosync/bin/python`, on Windows
+`%LOCALAPPDATA%\pipx\pipx\venvs\dosync\Scripts\python.exe`.
+
+Where the file goes and how it reloads is documented by your client, not here.
+
+### Two things Windows does to this file
+
+Neither belongs to any particular client, and both fail without a useful error,
+so they are worth knowing before you spend an afternoon on them.
+
+**A packaged application does not see the path you wrote to.** Applications
+installed from the Microsoft Store run with a virtualised filesystem: when they
+read `%APPDATA%\Something`, Windows redirects them to
+`%LOCALAPPDATA%\Packages\<package-id>\LocalCache\Roaming\Something`. A file
+written to the literal path is invisible to the application, and nothing
+reports this — the client simply behaves as though no configuration exists. If
+your client offers a button that opens its configuration folder, use it and
+write there.
+
+**PowerShell 5.1 writes a byte-order mark.** `Set-Content -Encoding UTF8` puts
+three bytes at the start of the file that JSON parsers reject, and the error
+names an invisible character: `Unexpected token ''`. Write it without one:
+
+```powershell
+[System.IO.File]::WriteAllText($path, $json, [System.Text.UTF8Encoding]::new($false))
+```
+
+Check the first byte is `123` (`{`) and not `239`:
+
+```powershell
+[System.IO.File]::ReadAllBytes($path)[0]
+```
+
+### What it looks like when it works
+
+*Verified 29 August 2026: Windows 11 ARM64, Python 3.14, DoSync 0.6.2 installed
+with `pipx`, MCP SDK 1.29.1, Claude Desktop from the Microsoft Store. Named
+because a result you cannot reproduce is not evidence — not as a
+recommendation. Any client that speaks MCP works; the details above are what
+that combination required, and clients change theirs without notice.*
+
+Asked in plain language which devices were registered, the agent listed six —
+three WiZ bulbs with their actions, and three adopted devices with none. What
+it said about the second group is the part worth reading:
+
+> Estos tres últimos están registrados pero sin tags ni acciones definidas — el
+> hub sabe que existen pero no puede actuar sobre ellos todavía.
+
+It did not invent capabilities for devices that have none. That is not the
+model being careful: the hub reports an undeclared device as undeclared, so
+there was nothing to invent from. Then it offered to describe one — the drafting
+flow in [`/v1/devices/{id}/describe`](#keeping-the-hub-running), reached from
+the other end.
+
+---
+
 ## What's built today
 
 | Component | Status |

{dosync-0.6.2 → dosync-0.6.3}/README.md

@@ -726,6 +726,130 @@ test, so it is named rather than recommended.
 
 ---
 
+## Connecting an agent
+
+This page has said "MCP" a dozen times — a badge at the top, a section on why
+MCP is the channel rather than the rival, a drone that flew a mission through
+it — and never once explained how to connect an agent. This is that.
+
+DoSync ships an MCP server. It is not a separate product: it exposes the hub's
+intents and devices as tools, and every call it makes lands in the same policy
+engine and the same audit chain as a call from `curl`. An agent that reaches a
+device through it is governed exactly like anything else.
+
+### What DoSync provides
+
+The server is a module rather than a command, and it needs the MCP SDK, which
+the hub does not install:
+
+```bash
+pip install "mcp>=1.0.0,<2.0"       # or: pipx inject dosync "mcp>=1.0.0,<2.0"
+python -m dosync.mcp_server
+```
+
+The upper bound is not caution. The 2.x SDK changed how tools are registered
+and this server is written against 1.x; without the cap, a fresh install gets
+2.x and the server exits at import. It says so plainly if that happens.
+
+It speaks over stdin/stdout, so a successful start prints nothing and waits.
+Typing into that terminal will produce JSON parse errors — that is the protocol
+rejecting your keystrokes, not a fault.
+
+It reads three environment variables:
+
+| Variable | Meaning |
+|---|---|
+| `DOSYNC_HUB_URL` | Where the hub is. Default `http://localhost:47200` |
+| `DOSYNC_TOKEN` | The hub's bearer token |
+| `DOSYNC_CA_CERT` | CA certificate, when the hub runs over TLS |
+
+That is the whole of DoSync's side. Everything below is about getting a client
+to launch that command — which is the client's business, not the protocol's.
+
+### What the client provides
+
+MCP clients are configured with a JSON file naming a command to run and the
+environment to run it in. The shape is standard:
+
+```json
+{
+  "mcpServers": {
+    "dosync": {
+      "command": "/absolute/path/to/python",
+      "args": ["-m", "dosync.mcp_server"],
+      "env": {
+        "DOSYNC_HUB_URL": "http://localhost:47200",
+        "DOSYNC_TOKEN": "your-token-here"
+      }
+    }
+  }
+}
+```
+
+**That file holds a credential.** It grants whatever the token grants. This
+project shipped a live token in a public repository for three months, so the
+warning is not rhetorical: keep it out of version control and off shared
+drives.
+
+Use an absolute path to the interpreter that has DoSync installed. A client
+launches the command with its own environment, not yours, so `python` may not
+resolve to what you expect. With `pipx`, the interpreter is inside its venv —
+on Linux and macOS `~/.local/share/pipx/venvs/dosync/bin/python`, on Windows
+`%LOCALAPPDATA%\pipx\pipx\venvs\dosync\Scripts\python.exe`.
+
+Where the file goes and how it reloads is documented by your client, not here.
+
+### Two things Windows does to this file
+
+Neither belongs to any particular client, and both fail without a useful error,
+so they are worth knowing before you spend an afternoon on them.
+
+**A packaged application does not see the path you wrote to.** Applications
+installed from the Microsoft Store run with a virtualised filesystem: when they
+read `%APPDATA%\Something`, Windows redirects them to
+`%LOCALAPPDATA%\Packages\<package-id>\LocalCache\Roaming\Something`. A file
+written to the literal path is invisible to the application, and nothing
+reports this — the client simply behaves as though no configuration exists. If
+your client offers a button that opens its configuration folder, use it and
+write there.
+
+**PowerShell 5.1 writes a byte-order mark.** `Set-Content -Encoding UTF8` puts
+three bytes at the start of the file that JSON parsers reject, and the error
+names an invisible character: `Unexpected token ''`. Write it without one:
+
+```powershell
+[System.IO.File]::WriteAllText($path, $json, [System.Text.UTF8Encoding]::new($false))
+```
+
+Check the first byte is `123` (`{`) and not `239`:
+
+```powershell
+[System.IO.File]::ReadAllBytes($path)[0]
+```
+
+### What it looks like when it works
+
+*Verified 29 August 2026: Windows 11 ARM64, Python 3.14, DoSync 0.6.2 installed
+with `pipx`, MCP SDK 1.29.1, Claude Desktop from the Microsoft Store. Named
+because a result you cannot reproduce is not evidence — not as a
+recommendation. Any client that speaks MCP works; the details above are what
+that combination required, and clients change theirs without notice.*
+
+Asked in plain language which devices were registered, the agent listed six —
+three WiZ bulbs with their actions, and three adopted devices with none. What
+it said about the second group is the part worth reading:
+
+> Estos tres últimos están registrados pero sin tags ni acciones definidas — el
+> hub sabe que existen pero no puede actuar sobre ellos todavía.
+
+It did not invent capabilities for devices that have none. That is not the
+model being careful: the hub reports an undeclared device as undeclared, so
+there was nothing to invent from. Then it offered to describe one — the drafting
+flow in [`/v1/devices/{id}/describe`](#keeping-the-hub-running), reached from
+the other end.
+
+---
+
 ## What's built today
 
 | Component | Status |

{dosync-0.6.2 → dosync-0.6.3}/dosync/__init__.py

@@ -13,5 +13,5 @@ The two numbers move independently on purpose:
   __version__           this implementation of the hub  (semver)
   __protocol_version__  the wire contract other implementations must match
 """
-__version__ = "0.6.2"
+__version__ = "0.6.3"
 __protocol_version__ = "0.4"

{dosync-0.6.2 → dosync-0.6.3}/dosync/adapters/__init__.py

@@ -6,7 +6,7 @@ Translation layer between the DoSync protocol and real physical devices.
 Modelo:
     DoSync Hub → AdapterExecutor → [WiZAdapter | GPIOAdapter | ShellyAdapter | ...]
 
-Para agregar un nuevo dispositivo:
+To add a new device type:
     1. Crear adapters/mi_marca.py implementando DoSyncAdapter
     2. Register the device with adapter="my_brand" in its CapabilityManifest
     3. The hub treats it like any other device — no core changes needed
@@ -55,7 +55,7 @@ class DoSyncAdapter(ABC):
     Cada adapter traduce acciones DoSync al protocolo nativo
     del dispositivo (UDP, HTTP, GPIO, BLE, etc.).
 
-    Para implementar un adapter nuevo:
+    To implement a new adapter:
 
         class MyBrandAdapter(DoSyncAdapter):
             async def execute(self, action, urgency):

{dosync-0.6.2 → dosync-0.6.3}/dosync/adapters/matter.py

@@ -1,7 +1,7 @@
 """
 DoSync — Matter Adapter
 =======================
-Adapter para dispositivos Matter via python-matter-server o Home Assistant bridge.
+Adapter for Matter devices, via python-matter-server or Home Assistant bridge.
 
 Matter is the Connectivity Standards Alliance IoT interoperability standard.
 Este adapter soporta dos modos:
@@ -164,7 +164,7 @@ class _MatterViaHA:
 
 class MatterAdapter(DoSyncAdapter):
     """
-    Adapter DoSync para dispositivos Matter.
+    DoSync adapter for Matter devices.
 
     Modo actual: via Home Assistant bridge (v0.2).
     Modo futuro: via python-matter-server standalone (v0.3).

{dosync-0.6.2 → dosync-0.6.3}/dosync/adapters/shelly.py

@@ -1,7 +1,7 @@
 """
 DoSync — Shelly Adapter
 =======================
-Adapter para dispositivos Shelly via HTTP local (Gen1 y Gen2).
+Adapter for Shelly devices over local HTTP (Gen1 and Gen2).
 
 Features:
 - Fully local communication — no cloud, no internet required
@@ -199,7 +199,7 @@ class ShellyAdapter(DoSyncAdapter):
     adapter_kind = "reference"
 
     """
-    Adapter DoSync para dispositivos Shelly.
+    DoSync adapter for Shelly devices.
 
     Soporta Gen1 (API REST) y Gen2 (API RPC).
     Sin dependencias externas — usa requests.

{dosync-0.6.2 → dosync-0.6.3}/dosync/db.py

@@ -232,7 +232,7 @@ class DoSyncDB:
         log.debug("Deleted device: %s", device_id)
 
     def load_devices(self) -> list[dict]:
-        """Carga todos los dispositivos registrados."""
+        """Load every registered device."""
         with self._cursor() as cur:
             cur.execute("SELECT manifest_json FROM devices ORDER BY registered_at")
             rows = cur.fetchall()
@@ -552,7 +552,7 @@ class DoSyncDB:
         return {}
 
     def load_all_device_states(self) -> dict:
-        """Carga todos los estados persistidos. Retorna {device_id: state_dict}."""
+        """Load every persisted state. Returns {device_id: state_dict}."""
         with self._cursor() as cur:
             cur.execute("SELECT device_id, state_json FROM device_state")
             rows = cur.fetchall()

{dosync-0.6.2 → dosync-0.6.3}/dosync/hub.py

@@ -685,7 +685,7 @@ class CapabilityMatchingResolver(BaseResolver):
                          actuator_type: str, intent: Intent) -> dict | None:
         """
         When the intent carries explicit profile actions in its context,
-        busca los params correspondientes a este dispositivo y actuator.
+        finds the params belonging to this device and actuator.
         Returns None when there is no match — the caller uses the defaults.
         """
         profile_actions = intent.context.get("actions", [])
@@ -3553,7 +3553,7 @@ class DoSyncHub:
         """
         Ejecuta un PhasedActionPlan: cada fase en paralelo,
         the phases in sequence, with a delay between them.
-        Ideal para emergencias donde el orden importa.
+        Suited to emergencies where ordering matters.
         """
         all_results = []
 

{dosync-0.6.2 → dosync-0.6.3}/dosync/mcp_server.py

@@ -128,6 +128,22 @@ def fmt(data: dict) -> str:
 
 server = Server("dosync-hub")
 
+# Checked here rather than left to fail at the first decorator. The 2.x SDK
+# removed `Server.list_tools()`, so an operator with that version installed got
+# `AttributeError: 'Server' object has no attribute 'list_tools'` from inside a
+# module they never opened — a true statement about the wrong thing. The
+# dependency is capped at `<2.0` now, but a cap does not help anyone who
+# already has 2.x in their environment, which is exactly who this message is
+# for.
+if not hasattr(server, "list_tools"):
+    import mcp as _mcp
+    raise RuntimeError(
+        "This MCP server is written against the 1.x SDK and the installed "
+        f"version is {getattr(_mcp, '__version__', 'unknown')}. The 2.x SDK "
+        "changed how tools are registered, so nothing here can start.\n\n"
+        "  pipx inject --force dosync 'mcp>=1.0.0,<2.0'\n\n"
+        "Porting to 2.x is tracked work, not a configuration problem.")
+
 
 async def _intent_property_schema() -> dict:
     """Build the JSON-schema fragment for the `intent` argument by reading the
@@ -179,7 +195,7 @@ async def list_tools() -> list[types.Tool]:
                 "Execute a semantic intent on the DoSync hub. "
                 "The hub resolves which devices act and how, "
                 "from their declared capabilities. "
-                "Usar para: emergencias, rutinas, control del ambiente, notificaciones."
+                "Use for: emergencies, routines, environment control, notifications."
             ),
             inputSchema={
                 "type": "object",
@@ -847,8 +863,8 @@ async def main():
         log.warning(
             "DOSYNC_TOKEN is not set — requests to the hub may fail "
             "if authentication is enabled. "
-            "Usar: DOSYNC_AUTH=false para deshabilitar, o "
-            "DOSYNC_TOKEN=<token> para autenticar."
+            "Set DOSYNC_TOKEN=<token> to authenticate, or run the hub with "
+            "DOSYNC_AUTH=false to turn authentication off (development only)."
         )
 
     async with mcp.server.stdio.stdio_server() as (read_stream, write_stream):

{dosync-0.6.2 → dosync-0.6.3}/dosync/security.py

@@ -25,7 +25,7 @@ Quick start:
     # Generar PKI completa (primera vez)
     python3 -m dosync.security setup
 
-    # Emitir certificado para un adapter nuevo
+    # Issue a certificate for a new adapter
     python3 -m dosync.security issue --name gpio --ip 127.0.0.1
 
     # Verify the certificates are valid and have not expired

{dosync-0.6.2 → dosync-0.6.3}/dosync/server.py

@@ -1294,7 +1294,7 @@ async def explain_intent(
     """
     Explainability endpoint — the resolver's reasoning for one intent.
 
-    Para cada dispositivo registrado, detalla:
+    For each registered device, it details:
     - Score total y desglose (tag overlap, location bonus, emergency bonus, actuator match)
     - Why it was included in or excluded from the ActionPlan
     - Which tags matched the intent's resolution tags

{dosync-0.6.2 → dosync-0.6.3}/dosync.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dosync
-Version: 0.6.2
+Version: 0.6.3
 Summary: The semantic layer between AI agents and physical devices
 Author-email: Rodrigo Giuliani <rgiuliani@dosync.dev>
 License-Expression: Apache-2.0
@@ -45,7 +45,7 @@ Requires-Dist: twilio>=8.0.0; extra == "sms"
 Provides-Extra: mavlink
 Requires-Dist: pymavlink>=2.4.0; extra == "mavlink"
 Provides-Extra: mcp
-Requires-Dist: mcp>=1.0.0; extra == "mcp"
+Requires-Dist: mcp<2.0,>=1.0.0; extra == "mcp"
 Provides-Extra: all
 Requires-Dist: pywizlight>=0.5.0; extra == "all"
 Requires-Dist: paho-mqtt>=2.0.0; extra == "all"
@@ -53,7 +53,7 @@ Requires-Dist: aiohttp>=3.9.0; extra == "all"
 Requires-Dist: bleak>=0.21; extra == "all"
 Requires-Dist: twilio>=8.0.0; extra == "all"
 Requires-Dist: pymavlink>=2.4.0; extra == "all"
-Requires-Dist: mcp>=1.0.0; extra == "all"
+Requires-Dist: mcp<2.0,>=1.0.0; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest>=7.4; extra == "dev"
 Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
@@ -788,6 +788,130 @@ test, so it is named rather than recommended.
 
 ---
 
+## Connecting an agent
+
+This page has said "MCP" a dozen times — a badge at the top, a section on why
+MCP is the channel rather than the rival, a drone that flew a mission through
+it — and never once explained how to connect an agent. This is that.
+
+DoSync ships an MCP server. It is not a separate product: it exposes the hub's
+intents and devices as tools, and every call it makes lands in the same policy
+engine and the same audit chain as a call from `curl`. An agent that reaches a
+device through it is governed exactly like anything else.
+
+### What DoSync provides
+
+The server is a module rather than a command, and it needs the MCP SDK, which
+the hub does not install:
+
+```bash
+pip install "mcp>=1.0.0,<2.0"       # or: pipx inject dosync "mcp>=1.0.0,<2.0"
+python -m dosync.mcp_server
+```
+
+The upper bound is not caution. The 2.x SDK changed how tools are registered
+and this server is written against 1.x; without the cap, a fresh install gets
+2.x and the server exits at import. It says so plainly if that happens.
+
+It speaks over stdin/stdout, so a successful start prints nothing and waits.
+Typing into that terminal will produce JSON parse errors — that is the protocol
+rejecting your keystrokes, not a fault.
+
+It reads three environment variables:
+
+| Variable | Meaning |
+|---|---|
+| `DOSYNC_HUB_URL` | Where the hub is. Default `http://localhost:47200` |
+| `DOSYNC_TOKEN` | The hub's bearer token |
+| `DOSYNC_CA_CERT` | CA certificate, when the hub runs over TLS |
+
+That is the whole of DoSync's side. Everything below is about getting a client
+to launch that command — which is the client's business, not the protocol's.
+
+### What the client provides
+
+MCP clients are configured with a JSON file naming a command to run and the
+environment to run it in. The shape is standard:
+
+```json
+{
+  "mcpServers": {
+    "dosync": {
+      "command": "/absolute/path/to/python",
+      "args": ["-m", "dosync.mcp_server"],
+      "env": {
+        "DOSYNC_HUB_URL": "http://localhost:47200",
+        "DOSYNC_TOKEN": "your-token-here"
+      }
+    }
+  }
+}
+```
+
+**That file holds a credential.** It grants whatever the token grants. This
+project shipped a live token in a public repository for three months, so the
+warning is not rhetorical: keep it out of version control and off shared
+drives.
+
+Use an absolute path to the interpreter that has DoSync installed. A client
+launches the command with its own environment, not yours, so `python` may not
+resolve to what you expect. With `pipx`, the interpreter is inside its venv —
+on Linux and macOS `~/.local/share/pipx/venvs/dosync/bin/python`, on Windows
+`%LOCALAPPDATA%\pipx\pipx\venvs\dosync\Scripts\python.exe`.
+
+Where the file goes and how it reloads is documented by your client, not here.
+
+### Two things Windows does to this file
+
+Neither belongs to any particular client, and both fail without a useful error,
+so they are worth knowing before you spend an afternoon on them.
+
+**A packaged application does not see the path you wrote to.** Applications
+installed from the Microsoft Store run with a virtualised filesystem: when they
+read `%APPDATA%\Something`, Windows redirects them to
+`%LOCALAPPDATA%\Packages\<package-id>\LocalCache\Roaming\Something`. A file
+written to the literal path is invisible to the application, and nothing
+reports this — the client simply behaves as though no configuration exists. If
+your client offers a button that opens its configuration folder, use it and
+write there.
+
+**PowerShell 5.1 writes a byte-order mark.** `Set-Content -Encoding UTF8` puts
+three bytes at the start of the file that JSON parsers reject, and the error
+names an invisible character: `Unexpected token ''`. Write it without one:
+
+```powershell
+[System.IO.File]::WriteAllText($path, $json, [System.Text.UTF8Encoding]::new($false))
+```
+
+Check the first byte is `123` (`{`) and not `239`:
+
+```powershell
+[System.IO.File]::ReadAllBytes($path)[0]
+```
+
+### What it looks like when it works
+
+*Verified 29 August 2026: Windows 11 ARM64, Python 3.14, DoSync 0.6.2 installed
+with `pipx`, MCP SDK 1.29.1, Claude Desktop from the Microsoft Store. Named
+because a result you cannot reproduce is not evidence — not as a
+recommendation. Any client that speaks MCP works; the details above are what
+that combination required, and clients change theirs without notice.*
+
+Asked in plain language which devices were registered, the agent listed six —
+three WiZ bulbs with their actions, and three adopted devices with none. What
+it said about the second group is the part worth reading:
+
+> Estos tres últimos están registrados pero sin tags ni acciones definidas — el
+> hub sabe que existen pero no puede actuar sobre ellos todavía.
+
+It did not invent capabilities for devices that have none. That is not the
+model being careful: the hub reports an undeclared device as undeclared, so
+there was nothing to invent from. Then it offered to describe one — the drafting
+flow in [`/v1/devices/{id}/describe`](#keeping-the-hub-running), reached from
+the other end.
+
+---
+
 ## What's built today
 
 | Component | Status |

{dosync-0.6.2 → dosync-0.6.3}/dosync.egg-info/requires.txt

@@ -15,7 +15,7 @@ aiohttp>=3.9.0
 bleak>=0.21
 twilio>=8.0.0
 pymavlink>=2.4.0
-mcp>=1.0.0
+mcp<2.0,>=1.0.0
 
 [ble]
 bleak>=0.21
@@ -32,7 +32,7 @@ aiohttp>=3.9.0
 pymavlink>=2.4.0
 
 [mcp]
-mcp>=1.0.0
+mcp<2.0,>=1.0.0
 
 [mqtt]
 paho-mqtt>=2.0.0

{dosync-0.6.2 → dosync-0.6.3}/pyproject.toml

@@ -89,11 +89,17 @@ ha      = ["aiohttp>=3.9.0"]
 ble     = ["bleak>=0.21"]
 sms     = ["twilio>=8.0.0"]
 mavlink = ["pymavlink>=2.4.0"]
-mcp     = ["mcp>=1.0.0"]
+# `<2.0` is not caution, it is a measured incompatibility: the 2.x SDK removed
+# `Server.list_tools()`, which `dosync/mcp_server.py` decorates at import time,
+# so `python -m dosync.mcp_server` dies with an AttributeError before it can
+# serve anything. An open-ended `>=1.0.0` was correct the day it was written
+# and stopped being correct when 2.0 shipped — the same shape of mistake as the
+# plain `uvicorn` pin that left the hub without a WebSocket library.
+mcp     = ["mcp>=1.0.0,<2.0"]
 # Everything a fully-loaded deployment needs.
 all = [
     "pywizlight>=0.5.0", "paho-mqtt>=2.0.0", "aiohttp>=3.9.0",
-    "bleak>=0.21", "twilio>=8.0.0", "pymavlink>=2.4.0", "mcp>=1.0.0",
+    "bleak>=0.21", "twilio>=8.0.0", "pymavlink>=2.4.0", "mcp>=1.0.0,<2.0",
 ]
 dev = [
     "pytest>=7.4", "pytest-asyncio>=0.23", "httpx>=0.27",