mcp-swarm 1.0.6 → 1.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +50 -8
- package/CHANGELOG.ru.md +68 -0
- package/README.md +2 -2
- package/README.ru.md +2 -2
- package/RELEASE_NOTES.md +4 -3
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -9,13 +9,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
9
9
|
|
|
10
10
|
---
|
|
11
11
|
|
|
12
|
-
## [1.0.
|
|
12
|
+
## [1.0.7] - 2026-02-09
|
|
13
13
|
|
|
14
14
|
### 🌉 Full Bridge Coverage — All 26 Smart Tools via Remote
|
|
15
15
|
|
|
16
16
|
#### Fixed
|
|
17
17
|
|
|
18
18
|
- **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 }`.
|
|
19
|
+
- **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.
|
|
19
20
|
|
|
20
21
|
#### Changed
|
|
21
22
|
|
|
@@ -24,15 +25,56 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
24
25
|
- After: all 26 tools × all actions work through bridge (swarm_task, swarm_plan, swarm_quality, swarm_vector, etc.)
|
|
25
26
|
- **Simplified tool routing** — `toolNeedsBridge()` on Cloudflare Worker simplified from 21-line selective logic to `toolName.startsWith("swarm_")` — routes ALL swarm tools through bridge.
|
|
26
27
|
|
|
27
|
-
####
|
|
28
|
+
#### Configuration
|
|
29
|
+
|
|
30
|
+
**Option A: Remote (recommended)**
|
|
31
|
+
|
|
32
|
+
```json
|
|
33
|
+
{
|
|
34
|
+
"mcpServers": {
|
|
35
|
+
"mcp-swarm": {
|
|
36
|
+
"command": "npx",
|
|
37
|
+
"args": [
|
|
38
|
+
"-y", "-p", "mcp-swarm",
|
|
39
|
+
"mcp-swarm-remote",
|
|
40
|
+
"--url", "https://mcp-swarm-server.YOUR-SUBDOMAIN.workers.dev/mcp"
|
|
41
|
+
],
|
|
42
|
+
"env": {
|
|
43
|
+
"SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
|
|
44
|
+
}
|
|
45
|
+
}
|
|
46
|
+
}
|
|
47
|
+
}
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
**Option B: Local with Hub**
|
|
51
|
+
|
|
52
|
+
```json
|
|
53
|
+
{
|
|
54
|
+
"mcpServers": {
|
|
55
|
+
"mcp-swarm": {
|
|
56
|
+
"command": "node",
|
|
57
|
+
"args": ["C:/path/to/Swarm_MCP/dist/serverSmart.js"],
|
|
58
|
+
"env": {
|
|
59
|
+
"SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
}
|
|
63
|
+
}
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
#### What Happens at Startup (Remote)
|
|
28
67
|
|
|
29
68
|
```
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
69
|
+
1. npx downloads mcp-swarm@latest from npm
|
|
70
|
+
2. mcp-swarm-remote starts → checks if companion is running
|
|
71
|
+
3. If not → starts companion with:
|
|
72
|
+
• MCP_SERVER_URL (from --url) → Bridge auto-connects to your Worker
|
|
73
|
+
• SWARM_HUB_URL (from env) → WebSocket to Hub for coordination
|
|
74
|
+
4. Companion starts:
|
|
75
|
+
• Bridge → WebSocket → MCP Server Worker (executes 26 tools locally)
|
|
76
|
+
• Hub → WebSocket → Hub Worker (real-time agent sync)
|
|
77
|
+
5. All 26 smart tools work! ✅
|
|
36
78
|
```
|
|
37
79
|
|
|
38
80
|
---
|
package/CHANGELOG.ru.md
CHANGED
|
@@ -9,6 +9,74 @@
|
|
|
9
9
|
|
|
10
10
|
---
|
|
11
11
|
|
|
12
|
+
## [1.0.7] - 2026-02-09
|
|
13
|
+
|
|
14
|
+
### 🌉 Полное покрытие Bridge — Все 26 Smart Tools через Remote
|
|
15
|
+
|
|
16
|
+
#### Исправлено
|
|
17
|
+
|
|
18
|
+
- **Критично: Авто-запуск Bridge** — `mcp-swarm-remote` теперь передаёт `MCP_SERVER_URL` в companion daemon. Ранее companion не знал URL сервера, и все удалённые tool calls возвращали `{ bridgeConnected: false }`.
|
|
19
|
+
- **Документация: Полный startup flow** — README теперь содержит полные примеры конфигурации для Remote и Local режимов с `SWARM_HUB_URL` и пошаговое описание процесса запуска.
|
|
20
|
+
|
|
21
|
+
#### Изменено
|
|
22
|
+
|
|
23
|
+
- **Универсальная делегация в bridge** — `bridge.ts` импортирует обработчики `allSmartTools` и делегирует ВСЕ tool calls (раньше — только 3 инструмента).
|
|
24
|
+
- **Упрощённая маршрутизация** — `toolNeedsBridge()` упрощена до `toolName.startsWith("swarm_")` (21 строка → 4).
|
|
25
|
+
|
|
26
|
+
#### Конфигурация
|
|
27
|
+
|
|
28
|
+
**Вариант A: Remote (рекомендуемый)**
|
|
29
|
+
|
|
30
|
+
```json
|
|
31
|
+
{
|
|
32
|
+
"mcpServers": {
|
|
33
|
+
"mcp-swarm": {
|
|
34
|
+
"command": "npx",
|
|
35
|
+
"args": [
|
|
36
|
+
"-y", "-p", "mcp-swarm",
|
|
37
|
+
"mcp-swarm-remote",
|
|
38
|
+
"--url", "https://mcp-swarm-server.YOUR-SUBDOMAIN.workers.dev/mcp"
|
|
39
|
+
],
|
|
40
|
+
"env": {
|
|
41
|
+
"SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
|
|
42
|
+
}
|
|
43
|
+
}
|
|
44
|
+
}
|
|
45
|
+
}
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
**Вариант B: Локальный с Hub**
|
|
49
|
+
|
|
50
|
+
```json
|
|
51
|
+
{
|
|
52
|
+
"mcpServers": {
|
|
53
|
+
"mcp-swarm": {
|
|
54
|
+
"command": "node",
|
|
55
|
+
"args": ["C:/path/to/Swarm_MCP/dist/serverSmart.js"],
|
|
56
|
+
"env": {
|
|
57
|
+
"SWARM_HUB_URL": "wss://mcp-swarm-hub.YOUR-SUBDOMAIN.workers.dev/ws"
|
|
58
|
+
}
|
|
59
|
+
}
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
#### Что происходит при запуске (Remote)
|
|
65
|
+
|
|
66
|
+
```
|
|
67
|
+
1. npx скачивает mcp-swarm@latest из npm (сейчас 1.0.6)
|
|
68
|
+
2. mcp-swarm-remote стартует → проверяет, запущен ли companion
|
|
69
|
+
3. Если нет → запускает companion с:
|
|
70
|
+
• MCP_SERVER_URL (из --url) → Bridge подключается к вашему Worker
|
|
71
|
+
• SWARM_HUB_URL (из env) → WebSocket к Hub для координации
|
|
72
|
+
4. Companion начинает работу:
|
|
73
|
+
• Bridge → WebSocket → MCP Server Worker (выполняет 26 инструментов локально)
|
|
74
|
+
• Hub → WebSocket → Hub Worker (синхронизация агентов в реальном времени)
|
|
75
|
+
5. Все 26 Smart Tools работают! ✅
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
12
80
|
## [0.9.19] - 2026-02-08
|
|
13
81
|
|
|
14
82
|
### 🚀 Большой релиз: Smart Routing, Память, Agent Teams, MCP-мосты
|
package/README.md
CHANGED
|
@@ -9,9 +9,9 @@
|
|
|
9
9
|
<img src="./assets/banner.png" alt="MCP Swarm Banner" width="800" />
|
|
10
10
|
</p>
|
|
11
11
|
|
|
12
|
-
# 🐝 MCP Swarm v1.0.
|
|
12
|
+
# 🐝 MCP Swarm v1.0.7 — Universal AI Agent Coordination Platform
|
|
13
13
|
|
|
14
|
-
> 🌉 **v1.0.
|
|
14
|
+
> 🌉 **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`
|
|
15
15
|
|
|
16
16
|
**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.
|
|
17
17
|
|
package/README.ru.md
CHANGED
|
@@ -9,9 +9,9 @@
|
|
|
9
9
|
<img src="./assets/banner.png" alt="MCP Swarm Banner" width="800" />
|
|
10
10
|
</p>
|
|
11
11
|
|
|
12
|
-
# 🐝 MCP Swarm v1.0.
|
|
12
|
+
# 🐝 MCP Swarm v1.0.7 — Универсальная Платформа Координации AI-Агентов
|
|
13
13
|
|
|
14
|
-
>
|
|
14
|
+
> 🌉 **v1.0.7 — Полный Remote Bridge:** Все **26 Smart Tools** теперь работают через Remote Bridge (было 3). Авто-запуск companion с передачей `MCP_SERVER_URL`. Обновитесь: `npm install -g mcp-swarm@latest`
|
|
15
15
|
|
|
16
16
|
**MCP Swarm** — это глобальная «нервная система» для ваших AI-помощников. Она превращает разрозненных агентов (Claude, Cursor, Windsurf, OpenCode) в слаженную команду, способную работать над огромными проектами без конфликтов и потери контекста.
|
|
17
17
|
|
package/RELEASE_NOTES.md
CHANGED
|
@@ -1,7 +1,8 @@
|
|
|
1
|
-
## 🌉 v1.0.
|
|
1
|
+
## 🌉 v1.0.6 — Full Bridge Coverage (All 26 Smart Tools via Remote)
|
|
2
2
|
|
|
3
3
|
### Fixed
|
|
4
4
|
- **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 }`.
|
|
5
|
+
- **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.
|
|
5
6
|
|
|
6
7
|
### Changed
|
|
7
8
|
- **Universal bridge delegation** — `bridge.ts` now imports `allSmartTools` handlers and delegates ALL tool calls (was only 3 tools with limited actions).
|
|
@@ -48,7 +49,7 @@
|
|
|
48
49
|
### What Happens at Startup (Remote)
|
|
49
50
|
|
|
50
51
|
```
|
|
51
|
-
1. npx downloads mcp-swarm@latest from npm (currently 1.0.
|
|
52
|
+
1. npx downloads mcp-swarm@latest from npm (currently 1.0.6)
|
|
52
53
|
2. mcp-swarm-remote starts → checks if companion is running
|
|
53
54
|
3. If not → starts companion with:
|
|
54
55
|
• MCP_SERVER_URL (from --url) → Bridge auto-connects to your Worker
|
|
@@ -61,7 +62,7 @@
|
|
|
61
62
|
|
|
62
63
|
### Stats
|
|
63
64
|
|
|
64
|
-
| Metric | v1.0.4 | v1.0.
|
|
65
|
+
| Metric | v1.0.4 | v1.0.6 |
|
|
65
66
|
|--------|--------|--------|
|
|
66
67
|
| Tools via bridge | 3 | **26** |
|
|
67
68
|
| Bridge auto-start | ❌ | ✅ |
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "mcp-swarm",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.7",
|
|
4
4
|
"private": false,
|
|
5
5
|
"type": "module",
|
|
6
6
|
"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",
|