Public and Private Pricefx MCP Connection

A public connection uses the shared MCP Server URL and does not require authentication. A private connection uses a partition-scoped MCP Server URL and requires OAuth 2.0 authentication. Public connections provide access to public tools, while private connections provide access to private tools.

Public tools – Client-agnostic, not tied to any specific partition, and can be exposed without per-partition endpoints.
Private tools – Partition-scoped, require OAuth authentication, can read or write tenant data, and enforce Role-Based Access Control (RBAC) and partition permissions.

Public Connection Details

Item	Value	Description
Endpoint	https://mcp.pricefx.com/mcp	No authentication
Public MCP Tools	Public Connection Type Tools	The public connection exposes four knowledge tools that let MCP clients find and read Pricefx Knowledge Base content without partition-specific authorization.
Supported Clients	Claude ChatGPT Cline Continue Cursor	All supported clients can connect using the same public server URL.

Private Connection Details

Item	Value	Description
Endpoint	https://mcp.pricefx.com/mcp/<cluster>/<partition>	OAuth 2.0 with PKCE
Private MCP Tools	Private Connection Type Tools
Supported Clients	Claude ChatGPT Copilot Studio Cline Claude Code OpenCode	Clients can automatically discover the authorization server through resource metadata and use it to complete the OAuth flow.

Diagram of the two ways to connect to the Pricefx MCP Server. The public connection needs no authentication and provides Knowledge Base tools. The private connection uses OAuth 2.0 and provides partition-scoped tools subject to tool access control.

See Also