Manage app groups through the MCP server (create groups, add/remove apps, show group in list_apps)
The problem
Problem
App groups (the folders in the Apps sidebar) can only be managed in the desktop UI. The MCP server has no tool for them, and list_apps / get_app do not return which group an app belongs to.
When an AI agent deploys apps through MCP (create_app, deploy_template), it cannot file the new app into the right group. A user who keeps, say, 15 static-site apps in one group has to drag each new app in by hand after every deploy, and the agent cannot check that it was done.
Proposed tools
- list_app_groups(serverId?): id, name, icon, color, parent, server, member stack ids
- create_app_group(serverId, name, icon?, color?, parentId?)
- update_app_group(groupId, name?, icon?, color?, parentId?)
- delete_app_group(groupId): danger tier, apps are kept
- set_app_groups(serverId, stackId, groupIds[]), or add_app_to_group / remove_app_from_group
- groupIds (or group names) in the list_apps and get_app results
- Optional: a groupId argument on create_app / deploy_template, so the app lands in its group in one step
Why not write the local database directly
It works (app_groups / app_group_memberships), but it bypasses the app: no validation, the open UI may not refresh, and it breaks if the schema changes. A supported tool is safer for everyone.
Use case
"Clone this site" → the agent mirrors it, deploys it with create_app, adds it to the "Site mirrors" group and verifies it, with no manual UI step.
Roadmap progress
PENDING
REVIEWING
—
PLANNED
—
IN PROGRESS
COMPLETED
—
- — thanhlinh9191 submitted this request
- — Khoa - StoicSoft Team moved it to In progress
Discussion1
- thanhlinh9191Sign in to reply
Readable version of the description (the board shows Markdown as plain text, so the headings and list above ran together):
PROBLEM
App groups (the folders in the Apps sidebar) can only be managed in the desktop UI. The MCP server has no tool for them, and list_apps / get_app do not return which group an app belongs to.
When an AI agent deploys apps through MCP (create_app, deploy_template), it cannot file the new app into the right group. A user who keeps, say, 15 static-site apps in one group has to drag each new app in by hand after every deploy, and the agent cannot check that it was done.
PROPOSED TOOLS
- list_app_groups(serverId?): id, name, icon, color, parent, server, member stack ids.
- create_app_group(serverId, name, icon?, color?, parentId?).
- update_app_group(groupId, name?, icon?, color?, parentId?).
- delete_app_group(groupId): danger tier; the apps are kept.
- set_app_groups(serverId, stackId, groupIds[]), or add_app_to_group / remove_app_from_group.
- groupIds (or group names) in the list_apps and get_app results.
- Optional: a groupId argument on create_app / deploy_template, so the app lands in its group in one step.
WHY NOT WRITE THE LOCAL DATABASE DIRECTLY
It works (tables app_groups / app_group_memberships), but it bypasses the app: no validation, the open UI may not refresh, and it breaks if the schema changes. A supported tool is safer for everyone.
USE CASE
"Clone this site": the agent mirrors it, deploys it with create_app, adds it to the "Site mirrors" group and verifies it, with no manual UI step.
Sign in to comment, vote and follow this request.
Sign in to reply