-
Notifications
You must be signed in to change notification settings - Fork 8
Closed
Labels
Description
Story Title
Show groups that are part of the registry and allow users to run the group
Description
User Story
As a user
I want to see the groups that are part of the registry
So that I can pick a group that's appropriate for my task
As a user
I want to run a group from the registry
So that I can quickly set up all the MCP servers I need for my task
Acceptance Criteria
Success path
Viewing
- Given a group named
devexists in the registry, when I view the registry, then I see the groupdevin the list with its description and a tag showing that it's a group - Given a group named
devexists in the registry, when I click ondev, then I see the group description, the MCP servers that are part of the group, and I have the option to create the group
Running
- Given a group named
devexists in the registry, when I run the groupdev, then a new group nameddevis created - Given a group named
devexists in the registry and has an MCP server namedfetch, when I run the groupdev, then thefetchMCP server is created - Given a group named
devexists in the registry and has an MCP server namedfetchandfetchhas an environment variable nameTOKEN, when I run the groupdev, then I have the option to set the environment variable nameTOKENforfetch - same as above for secrets, storage volumes, network isolation and all other workload configuration options
Failure path
- Given a group named
devexists in the registry, and I have an existing group in my ToolHive instance with the namedev, when I run the groupdev, then I get an error saying the group already exists AND no group or MCP servers are created - Given a group named
devexists in the registry and has an MCP server namedfetchand I have an existing MCP server namedfetchin my ToolHive instance, when I run the groupdev, then I get an error saying the MCP serverfetchalready exists
Target Release
none
Priority
High
Additional Context
The API will return groups in the following format. Servers and remote servers will follow the usual format that already exists in the registry:
"groups": [
{
"name": "Mobile App Team Toolkit",
"description": "MCP servers for the mobile app development team's workflows",
"servers": [
/* server entries following same format as top-level servers */
],
"remote_servers": [
/* remote server entries following same format as top-level remote_servers */
]
}
]