Connect Salesforce Agentforce to Performance Hub

Instructions current as of 17 June 2026 (AEST). Vendor MCP support changes frequently - verify against the linked sources if something looks different.

Salesforce has announced MCP support for Agentforce. Public documentation describes it as beta / account-qualified, so confirm availability and the exact auth fields in your own Salesforce org before publishing an agent.

Performance Hub MCP server:

https://app.performancehub.co/mcp

Current status

Public Salesforce sources describe Agentforce MCP support with:

  • A centralized MCP server registry.
  • Tool allowlisting.
  • Security and governance controls.
  • Authentication, granular access controls, policy enforcement, and rate limiting.
  • MCP tools saved as actions in the Agentforce Asset Library.
  • Adding selected MCP actions to topics in Agentforce Builder.

The accessible public sources did not specify the exact external MCP auth fields for arbitrary servers, such as static Authorization: Bearer ..., static x-mcp-api-key, OAuth Dynamic Client Registration, or manual OAuth client configuration. Do not assume any of these auth patterns are supported in Agentforce unless they are confirmed in your Salesforce org, beta documentation, or by Salesforce.

Setup outline

If your Salesforce org has Agentforce MCP beta access:

  1. In Salesforce Setup, register a new MCP server.
  2. Use the server URL:
https://app.performancehub.co/mcp
  1. Configure authentication using the auth methods available in your Salesforce org.
  2. Allowlist only the Performance Hub tools the agent needs.
  3. Save the selected tools as actions in the Agentforce Asset Library.
  4. In Agentforce Builder, open the agent/topic.
  5. Add actions from the Asset Library.
  6. Write clear instructions for each action.
  7. Test in Plan Canvas before publishing.

If MCP auth is not supported in your org

Use a Salesforce-supported integration path instead:

  • A MuleSoft / API action that calls the Performance Hub convenience endpoints.
  • An Apex action that calls a controlled backend service.
  • A Flow action connected to a secure integration layer.

The MCP convenience endpoints are:

GET  https://app.performancehub.co/mcp/tools
POST https://app.performancehub.co/mcp/tools/:name

They still require a valid Performance Hub MCP credential.

Safety prompt recommendation

Use Performance Hub actions only when the user asks about Performance Hub. Do not run device, door, access, order, display, or multi-facility actions without explicit confirmation. Prefer read-only actions before state-changing actions.

Sources