Tool groups
A tool group is a smaller MCP server cut from the same tools, such as a read-only one for support or a billing one for finance. Agents do better with a short list of relevant tools, and each team can connect only what its job needs.
Creating a group
In MCP Studio, under Servers, press New group.
NametextrequiredHow the group is named, up to 60 characters.
SlugtextrequiredThe group's part of its address: lowercase letters, digits and -, up to 32 characters.
DescriptiontextWhat this server is for, shown beside its install snippet. Up to 500 characters.
Tools with these tagslist of tagsIncludes everything with these tags. Tag tools under Customize for agents. New tagged tools join on their own.
And these toolslist of toolsAdds individual tools, custom tools, prompts and resources.
Only tools that readon or offLimits the group to tools that read, whatever their tags.
Include the documentation toolson or offAdds search_docs and the rest of the documentation tools.
A project can have up to 20 groups.
Publish to make the group live.
Connecting to a group
Each group has its own install snippet on the page, with its own address and bundle.
| Connection | How |
|---|---|
| Hosted | /g/ under your server's address |
| Claude Desktop | The group's own .mcpb bundle |
| Local | --group GROUP |
How groups treat your settings
A group only narrows the list. Access and customizations stay as you set them on each tool.
- A tool that is Off is in no group.
- A tool that Asks first still asks inside a group.
- A chained tool can be added to a group, and brings its steps with it.
Groups give each job a relevant list of tools. They don't restrict anyone: the main address still lists every tool you left on. To keep a team on one group, give them an installation of that group.
From the CLI
octri mcp package download --target bundle --group <slug> saves one group's bundle. See packages and plugins.