|
1 | 1 | # Sub-Agent MCP |
2 | 2 |
|
3 | | -[](https://github.com/stormaref/Sub-Agent-MCP/actions/workflows/ci.yml) |
| 3 | +[](https://github.com/systemgroupnet/Sub-Agent-MCP/actions/workflows/ci.yml) |
4 | 4 | [](LICENSE) |
5 | 5 | [](https://www.python.org/downloads/) |
6 | | -[](https://github.com/stormaref/Sub-Agent-MCP/pkgs/container/sub-agent-mcp) |
| 6 | +[](https://github.com/systemgroupnet/Sub-Agent-MCP/pkgs/container/sub-agent-mcp) |
7 | 7 |
|
8 | 8 | Production-ready Python MCP server for **LLM delegation and sub-agent orchestration**. A parent LLM (for example, Cursor’s agent) connects to this server and delegates work by calling a **tool named after each agent** defined in YAML (for example, `researcher`). |
9 | 9 |
|
@@ -164,7 +164,7 @@ Images are published on **git tags** matching `v*` (for example `v0.1.2`), not o |
164 | 164 | docker run -p 8000:8000 \ |
165 | 165 | -e OPENAI_API_KEY=sk-... \ |
166 | 166 | -v "$(pwd)/config/agents.yaml:/app/config/agents.yaml:ro" \ |
167 | | - ghcr.io/stormaref/sub-agent-mcp:latest |
| 167 | + ghcr.io/systemgroupnet/sub-agent-mcp:latest |
168 | 168 | ``` |
169 | 169 |
|
170 | 170 | Mount your own `agents.yaml` and ensure MCP `url` values are reachable from inside the container (use host networking, service names, or `host.docker.internal` as appropriate). |
@@ -427,7 +427,7 @@ Pull requests and pushes to `main` run lint and tests in [`.github/workflows/ci. |
427 | 427 |
|
428 | 428 | ## Docker image and releases |
429 | 429 |
|
430 | | -**Registry:** `ghcr.io/stormaref/sub-agent-mcp` |
| 430 | +**Registry:** `ghcr.io/systemgroupnet/sub-agent-mcp` |
431 | 431 |
|
432 | 432 | **When images publish:** Pushing a git tag `v0.*` (for example `v0.1.2`) runs the Docker job after tests pass. Pushes to `main` alone do not publish images. |
433 | 433 |
|
|
0 commit comments