MCP-based Roles for Pricefx Copilot | Pricefx Knowledge Base

The Pricefx Copilot can detect MCP‑based roles defined in a partition and use them to provide more accurate and context‑aware assistance.

Configuring MCP Roles for Pricefx Copilot

The Pricefx Copilot reads role definitions from the Advanced Configuration Options on the partition.

For a role to be detected and used by the Pricefx Copilot, it must be described by a JSON object that meets the following requirements:

The option name must be prefixed with MCP_role_, for example MCP_role_LPGManager. As a best practice, use the same value in the JSON name field.

The JSON must have the following structure:

JSON

{
  "name": "LPG Manager", //A brief, descriptive name for the role. Avoid at all cost names without meaning like "Role1" or "MyRole".
  "summary": "The LPG Manager is in charge of live price grids (LPGs)", //A brief, thoughtful summary of what the role is about and what it can do. This will be used by the LLM to understand *when to use this role*. No need to list the available tools in this summary, this is done automatically.
  "prompt": "", //This string will be used to help the LLM pick a tool *when the role is called*. This is where you can set instructions and examples about which tool to pick in which conditions. By default it is not mandatory (can be empty).
  "available_tools": [
    "lookup_lpg",
    "submit_lpg",
    "update_lpg"
  ] //The list of tool *names* that the role can use. Must be a subset of the *available* tools on the MCP servers.
}

To discover and use MCP Roles, a user must have permission to read from the Application Configuration Options table(APPLICATIONPROPERTIES_FETCH), which is currently granted only to the following user roles:

General Admin
Data Integration
Support
Develop Interceptors

For more information about user roles see User Roles.

Once the role is stored in the partition, the Pricefx Copilot automatically detects it and uses it when appropriate.