PlatformManager MCP Server | Pricefx Knowledge Base

PlatformManager provides a Model Context Protocol (MCP) server. MCP clients such as Claude Code or Claude Desktop use the server to read PlatformManager data and to run the Data Validation Tool. Every request runs as the PlatformManager user who owns the MCP token.

The PlatformManager MCP server is separate from the Pricefx MCP Server, which connects to a Pricefx partition.

Connection Details

Setting	Value
Server URL	`https://platform.pricefx.com/mcp`
Transport	Streamable HTTP
Authentication	An MCP token in the header `Authorization: Bearer <token>`
Access	Read-only, except three Data Validation tools that write. See Data Validation Tools.
Rate limit	120 requests per minute per user

The Created Token dialog shows the server URL of the PlatformManager you use.

Create an MCP Token (experimental feature)

An MCP token belongs to the user who creates it.

Navigation: Account menu > Profile Settings > Tokens

In the account menu, select Profile Settings.
Select Tokens.
Click Create MCP Token.
In Token Name, enter a name that identifies the client, for example Claude Code on my laptop.
Click Create.

The Created Token dialog opens. It shows the token, a command to connect Claude Code, and the settings for other MCP clients.

Copy the token and store it in a safe place. PlatformManager shows the token only once.

Connect an MCP Client

Claude Code – In the Created Token dialog, copy the command under Connect Claude Code: and run it in a terminal. The command has this form:
Bash
```
claude mcp add --transport http pfm https://platform.pricefx.com/mcp --header "Authorization: Bearer <token>"
```
Other MCP clients – Configure the server URL https://platform.pricefx.com/mcp. Send the header Authorization: Bearer <token> with every request.

Manage MCP Tokens

The Tokens table in Profile Settings lists your tokens. The Scope column shows MCP for an MCP token and API for an API token. The Expires column shows the expiry date.

Validity – An MCP token expires one year after you create it.
Revoke – To revoke a token, click Delete in its row and confirm. The token stops working immediately.
Lost token – If you lose a token, delete it and create a new one.
Token type – Use an MCP token for the MCP server, and an API token for the PlatformManager API. PlatformManager rejects a token of the other type.

Permissions and Data Access

The MCP server runs every tool call as the owner of the MCP token. Each tool returns only the data that this user can see in PlatformManager.
Each tool checks the same permissions as the PlatformManager endpoint it calls. The tool sections below name the permissions of the newer tools. For the permission list, see Permissions.
MCP requests use only the permissions assigned to the user in PlatformManager. Permissions that come from Active Directory groups do not apply.
PlatformManager audits every tool call and every rejected authentication attempt.

Available Tools

The MCP server exposes the read endpoints of the PlatformManager public API as tools. It also has tools for IntegrationManager instances, data upload runs and the Data Validation Tool. Three Data Validation tools change data: create_validation_upload, submit_validation_run and delete_validation_file. No other tool creates, changes, or deletes data. Tools that take a projectId expect the ID of a PlatformManager account.

Tool	Description
`whoami`	Returns the PlatformManager user that the MCP token belongs to, the expiry date of the token, and your rate limit.
`list_accounts`	Lists PlatformManager accounts.
`list_partitions`	Lists the partitions you can see, across all accounts.
`list_clusters`	Lists Pricefx clusters.
`list_dashboard_instances`	Lists the IntegrationManager instances on the PlatformManager dashboard.
`list_project_partitions`, `list_project_partitions_paged`	Lists the active partitions of an account. The paged tool adds move requests and log and monitoring URLs.
`list_project_users`, `list_project_users_paged`	Lists the active and invited users of an account.
`list_project_instances`, `list_project_instances_paged`	Lists the IntegrationManager instances of an account, with their health status.
`export_partition_schedulers`	Exports the event orchestration schedulers of a partition.
`export_partition_workflows`	Exports the event orchestration workflows of a partition.
`export_partition_event_listeners`	Exports the event orchestration event listeners of a partition.
`search_instance_logs`	Searches the logs of an IntegrationManager instance. Returns at most 100 results.
`list_non_global_permissions`	Lists the non-global PlatformManager permissions, grouped by entity type.
`get_accelerator_versions`	Lists the versions of a Marketplace accelerator package.
`get_latest_config_check_report`	Returns the latest completed Configuration Checker report for a partition or an IntegrationManager instance.

IntegrationManager Tools

search_instance_backup_index needs the Integration Instance - read permission, or higher, on the instance. get_instance_upgrade_rules needs Integration Instance - edit or Integration Instance - admin. The other two tools need no permission.

Tool	Description
`search_instance_backup_index`	Searches the backup archives of an IntegrationManager instance for files by path. Returns which files exist in which backup, without extracting them.
`get_instance_upgrade_rules`	Lists the migration rules that the IntegrationManager upgrade service applies when it upgrades an instance to a target version.
`get_im_upgrade_rules`	Lists the migration rules of the IntegrationManager upgrade service, for all versions or for a range of versions.
`get_im_upgrade_rules_for_ticket`	Lists the migration rules of one breaking change of the IntegrationManager upgrade service.

Data Upload Tools

These tools need the Partition Data Management - use or Partition Data Management - edit permission. A run is identified by its job ID.

Tool	Description
`list_upload_runs`	Lists the data upload runs of a partition.
`get_upload_run`	Returns the status of one data upload run.
`get_upload_errors`	Lists the reasons why a data upload run failed.

Data Validation Tools

These tools run the Data Validation Tool without its UI. Tools that work in an account need the Data Tools - edit permission on it. get_validation_run needs Data Tools - read. get_validation_mapper_templates with a partition needs Marketplace Templates - deploy on that partition.

Tool	Description
`list_validation_projects`	Lists the accounts in which you can run validations.
`list_validation_scenarios`	Lists the validation scenarios.
`get_validation_scenario`	Returns one validation scenario with its checks.
`get_validation_mapper_templates`	Returns the target fields of a scenario, which you map file columns to.
`create_validation_upload`	Writes. Opens an upload and returns an upload URL for the file.
`get_validation_upload`	Returns the status of an upload. When the file is parsed, it returns the file ID and the columns.
`list_validation_files`	Lists the uploaded files of an account.
`get_validation_file`	Returns an uploaded file with its columns.
`delete_validation_file`	Deletes an uploaded file. Runs that already used the file keep their results.
`preflight_validation_run`	Checks a run definition without starting the run.
`submit_validation_run`	Writes. Starts a validation run.
`get_validation_run`	Returns the result of a run: the overall score and status, and the result of each check.

A validation usually follows this order:

Select a scenario with list_validation_scenarios.
Get its target fields with get_validation_mapper_templates.
Upload each file: call create_validation_upload, send the file to the returned URL, and poll get_validation_upload until the file is parsed.
Check the run with preflight_validation_run.
Start the run with submit_validation_run.
Read the result with get_validation_run.

The MCP client sends the file to the upload URL itself. This works only from a client that can read local files, such as Claude Code. Other clients can use the read tools and run a validation on a file uploaded earlier.
submit_validation_run does not check the mapping. Always run preflight_validation_run first.
A run through the MCP server validates one scenario.
The MCP server does not return the row-level report. Download it in the Data Validation Tool.
An overall status n_a means that nothing was scored. The data did not pass. The usual cause is a wrong entity type.

Pricefx can switch off a group of tools in an environment. The tools of that group then do not appear in the tool list.

Your MCP client reads the tool list and the tool parameters from the server. The Swagger UI of PlatformManager documents the public API in the public-api definition.