The quick answer: a Salesforce MCP budget can contain four different bills—the AI work surface, the connector or agent platform, the Salesforce services the workflow invokes, and the implementation and governance work around it. A low connector price does not make a custom workflow free. An enterprise platform price does not mean every MCP request is metered the same way.
Price the complete operating loop: user, identity, Salesforce context, allowed action, review path, failure handling, and ongoing owner.
GAT Solutions built ApexGenius, a packaged Salesforce MCP product, and also implements Salesforce Hosted MCP, Agentforce, and custom MCP systems. That gives us a useful distinction: sometimes the connector is the answer; sometimes it is only one component of the project.
The four cost layers behind Salesforce MCP
| Cost layer | What it pays for | Question to answer |
|---|---|---|
| AI work surface | Claude, ChatGPT, Cursor, VS Code, or another compatible client | Which users need which AI capabilities and enterprise controls? |
| Connection or platform | Salesforce Hosted MCP, ApexGenius, Agentforce, or a custom MCP server | Is this a packaged connection, an agent platform, or software we must build and operate? |
| Salesforce services | Existing edition, API capacity, and any separately metered capability the workflow invokes | What entitlement or usage sits underneath each tool call? |
| Implementation & operation | Architecture, identity, permissions, workflow design, testing, enablement, monitoring, and change control | What has to be designed and maintained beyond connecting the endpoint? |
Connector pricing and implementation cost are different
A packaged connector is software. Its price covers access to a defined capability. ApexGenius, for example, publishes a flat product subscription rather than a GAT consulting fee or a custom engineering estimate. Because pricing and promotions can change, the authoritative number lives on the ApexGenius pricing page.
Implementation pays for the decisions around that software: which Salesforce identities connect, what each user can read or change, which actions appear to the model, how writes are reviewed, what happens in a sandbox versus production, how failures surface, and how people learn to use the workflow safely. If those decisions are already simple and the packaged product fits, the project may be little more than setup and enablement. If the workflow crosses five systems and performs consequential actions, the connector is only the beginning.
How the main Salesforce AI paths affect cost
| Path | Commercial model | Implementation work that can remain | Best fit |
|---|---|---|---|
| Salesforce Hosted MCP | Access and underlying usage follow current Salesforce edition, API, and product terms | Entitlement validation, client application, OAuth, permissions, tool scope, testing, and rollout | Salesforce-managed endpoints safely cover the required data and actions |
| ApexGenius | Flat product subscription; see the product site for current pricing | User and org setup, permission design, workflow patterns, enablement, and optional operating support | Packaged Salesforce access from Claude, ChatGPT, and compatible MCP clients |
| Agentforce | Salesforce licensing and usage models; confirm the current order form and rate card | Use-case design, topics, actions, data grounding, testing, channels, guardrails, and operation | Agents that live in Salesforce and its customer or employee channels |
| Custom MCP server | Engineering, infrastructure, security, observability, and maintenance | The product itself plus every workflow, tool, identity, evaluation, and operating control | Specialized tools, multiple systems, custom policies, or a purpose-built experience |
Salesforce packaging changes frequently. Verify current Hosted MCP and Agentforce entitlements with your account team and the official Agentforce pricing pagebefore approving a business case.
What a Salesforce MCP implementation actually includes
A credible implementation estimate should name the work. If a proposal has one line called “MCP setup,” ask which of these are inside it:
- Use-case architecture: users, jobs, source systems, actions, outcomes, and non-goals.
- Identity and OAuth: per-user versus service identity, token lifecycle, revocation, and environment separation.
- Salesforce authorization: profiles, permission sets, sharing, field-level security, API access, and metadata permissions.
- Tool scope: which reads, writes, metadata actions, deployments, or custom tools are exposed.
- Human control: previews, approvals, validation-only paths, production gates, and escalation.
- Failure design: denied access, malformed input, partial updates, limits, timeouts, retries, and recovery.
- Evaluation: test cases for accuracy, action selection, permission boundaries, and unsafe requests.
- Enablement: role-based patterns, documentation, acceptable-use guidance, and support ownership.
- Operation: monitoring, audit review, access changes, tool versioning, and continuous improvement.
The six factors that move implementation cost
- Number of systems. A packaged Salesforce connection is different from a workflow spanning Salesforce, HubSpot, support, documents, billing, and internal APIs.
- Action risk. Read-only analysis needs fewer controls than record updates, case decisions, financial actions, or metadata deployment.
- Identity complexity. One authorized user is simpler than enterprise SSO, multiple roles, service identities, tenant boundaries, and regulated access.
- Custom tool depth. Standard connector tools are already productized. Custom tools require design, code, tests, observability, documentation, and maintenance.
- Production evidence. Security review, evaluation suites, audit requirements, business continuity, and formal rollout add work because they reduce operating risk.
- Adoption scope. A developer pilot and a company-wide Claude or ChatGPT rollout are different change programs even when they call the same MCP server.
Three common budget shapes
1. Product only
The use case is Salesforce-centered, the packaged tool scope fits, and the internal administrator can manage identities, permissions, and enablement. Start with ApexGenius MCPand keep consulting out of the bill unless a real implementation need appears.
2. Packaged connector plus governed rollout
The product fits, but the organization needs architecture, least- privilege configuration, sandbox validation, workflow templates, training, and an operating model. The software subscription and the GAT engagement remain separate and visible.
3. Custom, cross-system AI workflow
The job extends beyond Salesforce or needs purpose-built actions, retrieval, a chatbot, specialized approvals, or its own user experience. Budget this as a system implementation with MCP inside it, not as connector setup.
Product, project, or both?
- Use ApexGenius when the need is a packaged Salesforce connection inside Claude, ChatGPT, or another compatible client.
- Hire GAT when the need is workflow architecture, custom tools, multi-system integration, governance, rollout, or ongoing operation.
- Use both when ApexGenius is the connector and GAT owns the business workflow and operating model around it.
See the full Salesforce MCP consulting and implementation service, or compare the architecture paths in our Salesforce MCP options guide.
Does Salesforce Hosted MCP mean the implementation is free?
No. Included product access and zero implementation work are not the same thing. Your organization may still need entitlement validation, client setup, identity and permission design, workflow configuration, testing, documentation, enablement, and ongoing ownership.
Should we start with Agentforce or MCP?
Start with the operating job. If people need their existing AI work surface to inspect or act on Salesforce, MCP is the natural category. If the business needs an agent that operates inside Salesforce channels for customers or employees, Agentforce may be the platform job. Many organizations eventually use both for different users and workflows.
Can GAT give us an exact implementation price?
Yes, after the users, systems, actions, environments, controls, and launch scope are clear. We do not publish invented price bands that pretend a one-user connector setup and a regulated multi-system agent are the same service. Book a consultationand GAT will recommend the smallest viable implementation path.