APIs from API Catalog

The Salesforce API Catalog is a curated registry of REST API endpoints that admins can map to custom MCP tools through the Setup UI. Rather than writing integration code, you select an endpoint from the catalog, configure its parameters, and publish it as a named tool on a custom server.

You configure API Catalog-backed tools through the custom server Setup UI — browse or search the catalog for an endpoint, set any fixed parameters, name the tool, and publish. See Custom MCP Servers for the full configuration walkthrough.

When an agent invokes the tool, the MCP server makes the corresponding REST API call using the authenticated user's credentials. All calls respect the user's object permissions and field-level security.

Use API Catalog tools when:

  • The operation exists as a Salesforce REST endpoint that isn't covered by the standard pre-configured servers (SObject tools, Invocable Actions, Data 360, or Tableau).
  • You're working with product-specific Connect APIs (Billing, CPQ, Field Service, Health Cloud, etc.) that have structured endpoints beyond basic SObject CRUD.

Use Invocable Actions instead when:

  • The operation requires server-side logic that isn't expressed as a single REST API call — for example, multi-step business logic, conditional branching, or operations that need to span multiple calls.
  • You want admin-maintainable automation using Flow Builder rather than a fixed API endpoint.

  • Billing operations: An agent helping sales reps answer customer billing questions invokes a Salesforce Billing API endpoint to retrieve invoice status, payment history, or outstanding balance — without giving the agent broad SObject access to billing records.

  • Field Service scheduling: An agent coordinating field service appointments invokes a Field Service Connect API to check technician availability and schedule a visit, using the structured scheduling endpoints rather than direct SObject manipulation.

  • Only endpoints registered in the API Catalog are available for selection. Not every Salesforce API endpoint is cataloged at GA — coverage expands over time.
  • Fixed parameters are set at configuration time and cannot be overridden by the agent at runtime. Parameters left open can be passed by the agent at call time.
  • Each tool maps to a single REST endpoint. Operations that require multiple API calls should use Flows or Invocable Actions, which can orchestrate multiple calls server-side.
  • API Catalog tools run as the authenticated user — the same permissions and rate limits apply as they would to any REST API call made by that user.