PlatformManager provides a read-only Model Context Protocol (MCP) server. MCP clients such as Claude Code or Claude Desktop use the server to read PlatformManager data. 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 |
|
|
Transport |
Streamable HTTP |
|
Authentication |
An MCP token in the header |
|
Access |
Read-only |
|
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
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:
Bashclaude 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 headerAuthorization: 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 matching public API endpoint. 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 has no tools that create, change, or delete data. Tools that take a projectId expect the ID of a PlatformManager account.
|
Tool |
Description |
|---|---|
|
|
Returns the PlatformManager user that the MCP token belongs to. |
|
|
Lists PlatformManager accounts. |
|
|
Lists the partitions you can see, across all accounts. |
|
|
Lists Pricefx clusters. |
|
|
Lists the IntegrationManager instances on the PlatformManager dashboard. |
|
|
Lists the active partitions of an account. The paged tool adds move requests and log and monitoring URLs. |
|
|
Lists the active and invited users of an account. |
|
|
Lists the IntegrationManager instances of an account, with their health status. |
|
|
Exports the event orchestration schedulers of a partition. |
|
|
Exports the event orchestration workflows of a partition. |
|
|
Exports the event orchestration event listeners of a partition. |
|
|
Searches the logs of an IntegrationManager instance. Returns at most 100 results. |
|
|
Lists the non-global PlatformManager permissions, grouped by entity type. |
|
|
Lists the versions of a Marketplace accelerator package. |
|
|
Returns the latest completed Configuration Checker report for a partition or an IntegrationManager instance. |
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.
Limitations
-
Authentication – The server accepts only MCP tokens. It does not support OAuth.
-
Server-initiated requests – The server does not support MCP sampling or elicitation.
-
Response size – The three
export_partition_tools andget_latest_config_check_reportreturn the full result in one response. A large export or report produces a large response. -
Rate limit – After 120 requests in one minute, the server rejects further requests from the same user until the minute ends. The error message is
MCP rate limit exceeded.