Skip to content

Commit 6d1fee9

Browse files
committed
Incorporate feedback
1 parent 957418b commit 6d1fee9

File tree

1 file changed

+11
-2
lines changed

1 file changed

+11
-2
lines changed

docs/toolhive/guides-cli/group-management.md

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ When running an MCP server, specify the group using the `--group` flag:
4646

4747
```bash
4848
thv run --group development fetch
49-
thv run --group production filesystem --volume /prod/repo:/workspace:ro
49+
thv run --group production filesystem --volume /prod/repo:/projects:ro
5050
```
5151

5252
:::info What's happening?
@@ -58,6 +58,15 @@ When you specify a group:
5858

5959
:::
6060

61+
A single workload can only belong to one group at a time. To run multiple
62+
instances of the same MCP server in different groups, use a unique name for each
63+
instance:
64+
65+
```bash
66+
thv run --group development --name fetch-dev fetch
67+
thv run --group production --name fetch-prod fetch
68+
```
69+
6170
## Configure client access to groups
6271

6372
You can configure MCP clients to access specific groups, giving you control over
@@ -68,7 +77,7 @@ which tools are available in different contexts.
6877
When registering a client, you can specify which group it should access:
6978

7079
```bash
71-
thv client register --group development
80+
thv client register <CLIENT_NAME> --group development
7281
```
7382

7483
This configures the client to only access servers in the `development` group.

0 commit comments

Comments
 (0)