Every tool behind the configuration door /mcpconfig has a right of its own. That right is necessary but never enough.
The chain
tool_config_use— the master switch. Without this right the tool list is empty.tool_config_<tool>— one right per tool. Plan and apply each have their own right, so you can let someone look without letting them change anything.- The functional right behind the tool — the very same right the screen uses.
- When writing: both configuration locks must be open. Tools with level 2 are not run on a production environment.
Who holds these rights?
The rights sit in the MCP-Config group, together with the functional rights the tools need. A fresh install gets that group automatically; on an upgraded environment you set it up with the button on Configuration → AI settings → Tools. Either way the group starts without members: adding someone to the group is the step that turns configuring through AI on for that person.
What the tools do is described on MCP configuration tools.
tool_config_combi_create_plan
Show the intended creation of a package through AI.
tool_config_combi_set_calendar_apply
Set the calendar of a package through AI.
tool_config_combi_set_calendar_plan
Show the intended change of the package calendar through AI.
tool_config_combi_set_extras_apply
Set the options of a package through AI.
tool_config_combi_set_extras_plan
Show the intended change of package options through AI.
tool_config_combi_set_parts_apply
Set the parts of a package through AI.
tool_config_combi_set_parts_plan
Show the intended change of package parts through AI.
tool_config_combi_set_price_schemas_apply
Set the price schemes of a package through AI.
tool_config_combi_set_price_schemas_plan
Show the intended change of package price schemes through AI.
tool_config_combi_update_apply
Change a package through AI.
