mcp-swarm 1.0.5 → 1.0.7

package/CHANGELOG.md

@@ -9,13 +9,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ---
 
-## [1.0.5] - 2026-02-09
+## [1.0.7] - 2026-02-09
 
 ### 🌉 Full Bridge Coverage — All 26 Smart Tools via Remote
 
 #### Fixed
 
 - **Critical: Bridge auto-start** — `mcp-swarm-remote` now passes `MCP_SERVER_URL` to companion daemon. Previously the companion couldn't know where to connect the bridge, so all remote tool calls returned `{ bridgeConnected: false }`.
+- **Documentation: Full startup flow** — README now includes complete configuration examples for both Remote and Local modes with `SWARM_HUB_URL`, and step-by-step explanation of what happens at startup.
 
 #### Changed
 
@@ -24,15 +25,56 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - After: all 26 tools × all actions work through bridge (swarm_task, swarm_plan, swarm_quality, swarm_vector, etc.)
 - **Simplified tool routing** — `toolNeedsBridge()` on Cloudflare Worker simplified from 21-line selective logic to `toolName.startsWith("swarm_")` — routes ALL swarm tools through bridge.
 
-#### How It Works
+#### Configuration
+
+**Option A: Remote (recommended)**
+
+```json
+{
+  "mcpServers": {
+    "mcp-swarm": {
+      "command": "npx",
+      "args": [
+        "-y", "-p", "mcp-swarm",
+        "mcp-swarm-remote",
+        "--url", "https://mcp-swarm-server.YOUR-SUBDOMAIN.workers.dev/mcp"
+      ],
+      "env": {
+        "SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
+      }
+    }
+  }
+}
+```
+
+**Option B: Local with Hub**
+
+```json
+{
+  "mcpServers": {
+    "mcp-swarm": {
+      "command": "node",
+      "args": ["C:/path/to/Swarm_MCP/dist/serverSmart.js"],
+      "env": {
+        "SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
+      }
+    }
+  }
+}
+```
+
+#### What Happens at Startup (Remote)
 
 ```
-IDE → npx mcp-swarm-remote --url https://server.workers.dev/mcp
-       ↓ auto-starts companion with MCP_SERVER_URL
-Companion → BridgeManager → WebSocket → server/bridge
-       ↓ server receives tool call → routes through bridge
-Companion → allSmartTools[toolName](args) → result
-       ↓ returns via WebSocket through server back to IDE
+1. npx downloads mcp-swarm@latest from npm
+2. mcp-swarm-remote starts → checks if companion is running
+3. If not → starts companion with:
+   • MCP_SERVER_URL (from --url) → Bridge auto-connects to your Worker
+   • SWARM_HUB_URL (from env)   → WebSocket to Hub for coordination
+4. Companion starts:
+   • Bridge → WebSocket → MCP Server Worker (executes 26 tools locally)
+   • Hub    → WebSocket → Hub Worker (real-time agent sync)
+5. All 26 smart tools work! ✅
 ```
 
 ---

package/CHANGELOG.ru.md

@@ -9,6 +9,74 @@
 
 ---
 
+## [1.0.7] - 2026-02-09
+
+### 🌉 Полное покрытие Bridge — Все 26 Smart Tools через Remote
+
+#### Исправлено
+
+- **Критично: Авто-запуск Bridge** — `mcp-swarm-remote` теперь передаёт `MCP_SERVER_URL` в companion daemon. Ранее companion не знал URL сервера, и все удалённые tool calls возвращали `{ bridgeConnected: false }`.
+- **Документация: Полный startup flow** — README теперь содержит полные примеры конфигурации для Remote и Local режимов с `SWARM_HUB_URL` и пошаговое описание процесса запуска.
+
+#### Изменено
+
+- **Универсальная делегация в bridge** — `bridge.ts` импортирует обработчики `allSmartTools` и делегирует ВСЕ tool calls (раньше — только 3 инструмента).
+- **Упрощённая маршрутизация** — `toolNeedsBridge()` упрощена до `toolName.startsWith("swarm_")` (21 строка → 4).
+
+#### Конфигурация
+
+**Вариант A: Remote (рекомендуемый)**
+
+```json
+{
+  "mcpServers": {
+    "mcp-swarm": {
+      "command": "npx",
+      "args": [
+        "-y", "-p", "mcp-swarm",
+        "mcp-swarm-remote",
+        "--url", "https://mcp-swarm-server.YOUR-SUBDOMAIN.workers.dev/mcp"
+      ],
+      "env": {
+        "SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
+      }
+    }
+  }
+}
+```
+
+**Вариант B: Локальный с Hub**
+
+```json
+{
+  "mcpServers": {
+    "mcp-swarm": {
+      "command": "node",
+      "args": ["C:/path/to/Swarm_MCP/dist/serverSmart.js"],
+      "env": {
+        "SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
+      }
+    }
+  }
+}
+```
+
+#### Что происходит при запуске (Remote)
+
+```
+1. npx скачивает mcp-swarm@latest из npm (сейчас 1.0.6)
+2. mcp-swarm-remote стартует → проверяет, запущен ли companion
+3. Если нет → запускает companion с:
+   • MCP_SERVER_URL (из --url) → Bridge подключается к вашему Worker
+   • SWARM_HUB_URL (из env)   → WebSocket к Hub для координации
+4. Companion начинает работу:
+   • Bridge → WebSocket → MCP Server Worker (выполняет 26 инструментов локально)
+   • Hub    → WebSocket → Hub Worker (синхронизация агентов в реальном времени)
+5. Все 26 Smart Tools работают! ✅
+```
+
+---
+
 ## [0.9.19] - 2026-02-08
 
 ### 🚀 Большой релиз: Smart Routing, Память, Agent Teams, MCP-мосты

package/README.md

@@ -9,9 +9,9 @@
   <img src="./assets/banner.png" alt="MCP Swarm Banner" width="800" />
 </p>
 
-# 🐝 MCP Swarm v1.0.5 — Universal AI Agent Coordination Platform
+# 🐝 MCP Swarm v1.0.7 — Universal AI Agent Coordination Platform
 
-> 🌉 **v1.0.5 — Full Remote Bridge:** All **26 Smart Tools** now work through Remote Bridge (was 3). Auto-start companion with `MCP_SERVER_URL` passthrough. Zero-config setup — just `npx mcp-swarm-remote --url https://...`. Update: `npm install -g mcp-swarm@latest`
+> 🌉 **v1.0.7 — Full Remote Bridge:** All **26 Smart Tools** now work through Remote Bridge (was 3). Auto-start companion with `MCP_SERVER_URL` passthrough. Zero-config setup — just `npx mcp-swarm-remote --url https://...`. Update: `npm install -g mcp-swarm@latest`
 
 **MCP Swarm** is a global "nervous system" for your AI assistants. It turns separate agents (Claude, Cursor, Windsurf, OpenCode) into a coordinated team that can work on massive projects without conflicts or context loss.
 
@@ -599,11 +599,7 @@ curl "https://api.telegram.org/botYOUR_TOKEN/setWebhook?url=https://mcp-swarm-te
 
 ### Step 4: Configure Your IDE
 
-**Option A: Remote (recommended)**
-
-```bash
-npm install -g mcp-swarm
-```
+**Option A: Remote (recommended) — v1.0.5**
 
 ```json
 {
@@ -611,17 +607,36 @@ npm install -g mcp-swarm
     "mcp-swarm": {
       "command": "npx",
       "args": [
-        "-y",
-        "-p", "mcp-swarm",
+        "-y", "-p", "mcp-swarm",
         "mcp-swarm-remote",
-        "--url", "https://mcp-swarm-server.YOUR-SUBDOMAIN.workers.dev/mcp",
-        "--telegram-user-id", "YOUR_TELEGRAM_ID"
-      ]
+        "--url", "https://mcp-swarm-server.YOUR-SUBDOMAIN.workers.dev/mcp"
+      ],
+      "env": {
+        "SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
+      }
     }
   }
 }
 ```
 
+> 💡 `npx -y -p mcp-swarm` automatically downloads the **latest version** from npm (currently 1.0.5).
+
+**What happens when Remote starts:**
+
+```
+1. npx downloads mcp-swarm@latest from npm
+2. mcp-swarm-remote starts → checks if companion is running
+3. If not → starts companion with:
+   • MCP_SERVER_URL (from --url) → Bridge auto-connects to your Worker
+   • SWARM_HUB_URL (from env)   → WebSocket to Hub for coordination
+4. Companion starts:
+   • Bridge → WebSocket → MCP Server Worker (executes 26 tools locally)
+   • Hub    → WebSocket → Hub Worker (real-time agent sync)
+5. All 26 smart tools work! ✅
+```
+
+---
+
 **Option B: Local with Hub**
 
 ```json
@@ -639,14 +654,26 @@ npm install -g mcp-swarm
 }
 ```
 
+**What happens when Local starts:**
+
+```
+1. Node.js runs serverSmart.js directly (no npm download)
+2. MCP server starts as stdio process → IDE connects via stdin/stdout
+3. All 26 tools execute locally — no bridge needed
+4. Hub connection (optional) → real-time sync between agents
+```
+
+---
+
 ### 🔄 Comparison
 
-| Feature | Remote | Local+Hub |
-|---------|--------|-----------|
-| Setup | `npm i -g mcp-swarm` | `git clone && npm build` |
-| Config | Short | Longer |
-| Data | Your Worker | Local |
-| Offline | ❌ | ✅ (with Hub fallback) |
+| Feature | Remote (A) | Local (B) |
+|---------|------------|-----------|
+| Install | `npx` auto-downloads latest | `git clone && npm build` |
+| Tools | 26 via Bridge | 26 directly |
+| Multi-PC | ✅ Works from any machine | ❌ Only where installed |
+| Updates | ✅ Auto (npx latest) | Manual (`git pull && build`) |
+| Offline | ❌ Needs internet | ✅ Works offline |
 | Latency | ~50–100ms | <10ms |
 
 ### ❓ What is YOUR-SUBDOMAIN?

package/README.ru.md

@@ -9,9 +9,9 @@
   <img src="./assets/banner.png" alt="MCP Swarm Banner" width="800" />
 </p>
 
-# 🐝 MCP Swarm v1.0.4 — Универсальная Платформа Координации AI-Агентов
+# 🐝 MCP Swarm v1.0.7 — Универсальная Платформа Координации AI-Агентов
 
-> 🧠 **v1.0.4 — Консолидация и стабильность:** 54 → **26 Smart Tools** (без потери функций). Исправлена совместимость MCP-протокола (jsonrpc 2.0). 21 AI-модель в MoE Router. Обновитесь: `npm install -g mcp-swarm@latest`
+> 🌉 **v1.0.7 — Полный Remote Bridge:** Все **26 Smart Tools** теперь работают через Remote Bridge (было 3). Авто-запуск companion с передачей `MCP_SERVER_URL`. Обновитесь: `npm install -g mcp-swarm@latest`
 
 **MCP Swarm** — это глобальная «нервная система» для ваших AI-помощников. Она превращает разрозненных агентов (Claude, Cursor, Windsurf, OpenCode) в слаженную команду, способную работать над огромными проектами без конфликтов и потери контекста.
 

package/RELEASE_NOTES.md

@@ -0,0 +1,76 @@
+## 🌉 v1.0.6 — Full Bridge Coverage (All 26 Smart Tools via Remote)
+
+### Fixed
+- **Critical: Bridge auto-start** — `mcp-swarm-remote` now passes `MCP_SERVER_URL` to companion daemon. Previously the companion couldn't know where to connect, so all remote tool calls returned `{ bridgeConnected: false }`.
+- **Documentation: Full startup flow** — README now includes complete configuration examples for both Remote and Local modes with `SWARM_HUB_URL`, and step-by-step explanation of what happens at startup.
+
+### Changed
+- **Universal bridge delegation** — `bridge.ts` now imports `allSmartTools` handlers and delegates ALL tool calls (was only 3 tools with limited actions).
+- **Simplified tool routing** — `toolNeedsBridge()` simplified to `toolName.startsWith("swarm_")` — routes ALL swarm tools through bridge.
+
+### Configuration
+
+**Option A: Remote (recommended)**
+
+```json
+{
+  "mcpServers": {
+    "mcp-swarm": {
+      "command": "npx",
+      "args": [
+        "-y", "-p", "mcp-swarm",
+        "mcp-swarm-remote",
+        "--url", "https://mcp-swarm-server.YOUR-SUBDOMAIN.workers.dev/mcp"
+      ],
+      "env": {
+        "SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
+      }
+    }
+  }
+}
+```
+
+**Option B: Local with Hub**
+
+```json
+{
+  "mcpServers": {
+    "mcp-swarm": {
+      "command": "node",
+      "args": ["C:/path/to/Swarm_MCP/dist/serverSmart.js"],
+      "env": {
+        "SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
+      }
+    }
+  }
+}
+```
+
+### What Happens at Startup (Remote)
+
+```
+1. npx downloads mcp-swarm@latest from npm (currently 1.0.6)
+2. mcp-swarm-remote starts → checks if companion is running
+3. If not → starts companion with:
+   • MCP_SERVER_URL (from --url) → Bridge auto-connects to your Worker
+   • SWARM_HUB_URL (from env)   → WebSocket to Hub for coordination
+4. Companion starts:
+   • Bridge → WebSocket → MCP Server Worker (executes 26 tools locally)
+   • Hub    → WebSocket → Hub Worker (real-time agent sync)
+5. All 26 smart tools work! ✅
+```
+
+### Stats
+
+| Metric | v1.0.4 | v1.0.6 |
+|--------|--------|--------|
+| Tools via bridge | 3 | **26** |
+| Bridge auto-start | ❌ | ✅ |
+| `executeLocalTool()` | 82 lines | **40 lines** |
+| `toolNeedsBridge()` | 21 lines | **4 lines** |
+
+### Upgrade
+
+```bash
+npm install -g mcp-swarm@latest
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-swarm",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "private": false,
   "type": "module",
   "description": "Universal AI agent coordination platform with 26 consolidated smart tools, 21 AI models (Kimi K2.5, GPT-5.3, Opus 4.6), EWC++ self-learning, semantic caching, and Q-Learning routing",