@@ -268,23 +268,38 @@ purposes:
268268 },
269269 "groups": [
270270 {
271- "name": "frontend-dev ",
272- "description": "Tools for frontend development team ",
271+ "name": "devops-toolkit ",
272+ "description": "Complete DevOps toolkit for development teams ",
273273 "servers": {
274- "dev-fetch": {
275- "description": "Development web content fetching with broader access",
276- "image": "ghcr.io/stackloklabs/gofetch/server:latest",
274+ "github": {
275+ "description": "GitHub integration for repository and issue management",
276+ "image": "ghcr.io/github/github-mcp-server:v0.15.0",
277+ "status": "Active",
278+ "tier": "Official",
279+ "transport": "stdio",
280+ "env_vars": [
281+ {
282+ "name": "GITHUB_PERSONAL_ACCESS_TOKEN",
283+ "description": "GitHub personal access token",
284+ "required": true,
285+ "secret": true
286+ }
287+ ]
288+ },
289+ "heroku": {
290+ "description": "Heroku platform deployment and management",
291+ "image": "ghcr.io/stacklok/dockyard/npx/heroku-mcp-server:1.0.7",
277292 "status": "Active",
278293 "tier": "Community",
279- "transport": "streamable-http ",
280- "permissions ": {
281- "network": {
282- "outbound ": {
283- "allow_host ": ["*"] ,
284- "allow_port ": [80, 443]
285- }
294+ "transport": "stdio ",
295+ "env_vars ": [
296+ {
297+ "name ": "HEROKU_API_KEY",
298+ "description ": "Heroku API key" ,
299+ "required ": true,
300+ "secret": true
286301 }
287- }
302+ ]
288303 }
289304 }
290305 },
@@ -317,25 +332,27 @@ purposes:
317332This registry provides :
318333
319334- A production-ready `production-fetch` server at the top level
320- - A `frontend-dev` group with a more permissive `dev-fetch` server
335+ - A `devops-toolkit` group with GitHub and Heroku servers for complete DevOps
336+ workflows
321337- A `testing-suite` group with a restricted `test-fetch` server
322338
323- Each server has the same base image but different configurations appropriate for
324- its use case.
339+ Notice how the `devops-toolkit` group contains multiple servers that work
340+ together—GitHub for repository management and Heroku for
341+ deployment—demonstrating how groups can bundle related functionality.
325342
326343# ## Run registry groups
327344
328345You can run entire groups using the group command :
329346
330347` ` ` bash
331- # Run all servers in the frontend-dev group
332- thv group run frontend-dev
348+ # Run all servers in the devops-toolkit group (GitHub + Heroku)
349+ thv group run devops-toolkit
333350
334351# Run all servers in the testing-suite group
335352thv group run testing-suite
336353
337- # You can also pass environment variables and secrets to group runs
338- thv group run frontend-dev --env DEV_MODE=true --secret API_KEY=my-secret
354+ # You can also pass environment variables and secrets to specific servers in the group
355+ thv group run devops-toolkit --secret github-token,target=github.GITHUB_PERSONAL_ACCESS_TOKEN --secret heroku-key,target=heroku.HEROKU_API_KEY
339356` ` `
340357
341358Groups provide a convenient way to start multiple related servers with a single
0 commit comments