Skip to main content
As you register more MCP servers in MCPJungle, the total number of tools visible through the gateway grows quickly. Exposing hundreds of tools to a single MCP client degrades LLM calling accuracy and slows down tool discovery. Tool Groups let you define a named subset of tools and give it its own dedicated MCP endpoint. Each client connects to a group endpoint instead of the main /mcp gateway, so it only sees the tools relevant to its task.

​
How tool groups work

When you create a group, MCPJungle registers a new streamable HTTP endpoint at: 
/v0/groups/{group-name}/mcp
Point your MCP client at that URL instead of the main gateway. The client will only discover and call the tools included in that group.
If a tool included in a group is later disabled globally or deregistered, it becomes unavailable through the group endpoint automatically. Re-enabling or re-registering the tool makes it available again without any changes to the group configuration.

​
Configuration file format

You define a group in a JSON file and pass it to the create group command. Three fields control which tools are included:
FieldTypeDescription
namestringUnique name for the group (required).
descriptionstringHuman-readable description (optional).
included_toolsstring[]Canonical tool names to include individually.
included_serversstring[]Include all tools from these MCP servers.
excluded_toolsstring[]Remove specific tools from the resolved set (applied last).
Exclusion is always applied after inclusion. If a tool appears in both included_tools and excluded_tools, it will be excluded from the final group.

​
Configuration approaches

Use included_tools to handpick exactly which tools to expose. Tool names follow the canonical format <server-name>__<tool-name>.
claude-tools-group.json
{
  "name": "claude-tools",
  "description": "This group only contains tools for Claude Desktop to use",
  "included_tools": [
    "filesystem__read_file",
    "deepwiki__read_wiki_contents",
    "time__get_current_time"
  ]
}
This group exposes exactly three tools regardless of how many tools are registered in MCPJungle.
Run mcpjungle list tools to see all available tool names before building your group configuration.

​
Creating a group

Pass the configuration file to the create group command using the -c flag: 
mcpjungle create group -c ./claude-tools-group.json
MCPJungle confirms the group was created and prints its endpoint: 
Tool Group claude-tools created successfully
It is now accessible at the following streamable http endpoint:

    http://127.0.0.1:8080/v0/groups/claude-tools/mcp
Configure your MCP client to connect to that URL instead of http://127.0.0.1:8080/mcp. The client will only see the tools in the group.

​
Managing groups

1

List all groups

mcpjungle list groups
2

Inspect a specific group

mcpjungle get group claude-tools
This shows the group’s description, its MCP endpoint URLs, and the lists of included tools, included servers, and excluded tools.
3

Delete a group

mcpjungle delete group claude-tools
Deleting a group removes its endpoint. Make sure no MCP clients are connected to that endpoint before you delete it. The tools themselves are not deleted — only the group configuration.

​
Working with tools inside a group

Use the --group flag on list tools and invoke to scope operations to a specific group: 
# List tools visible in the group
mcpjungle list tools --group claude-tools

# Invoke a tool through the group context
mcpjungle invoke filesystem__read_file --group claude-tools --input '{"path": "README.md"}'
These commands are useful for verifying that a group is configured correctly before pointing a client at it.

​
Known limitations

MCP Prompts are not currently available through group endpoints. Clients connected to a group endpoint cannot discover or invoke prompts. This is a known issue tracked at mcpjungle#136.
There is no update group command. To change a group’s configuration, delete the group and recreate it with the updated JSON file:
mcpjungle delete group claude-tools
mcpjungle create group -c ./claude-tools-group.json
When MCPJungle runs in enterprise mode, only an admin account can create Tool Groups. Standard users do not have permission to create groups. Support for user-scoped groups is planned for a future release.