Home / Token cost / Salesforce Cloud

The Salesforce Cloud MCP server costs 2,551 tokens before the first call.

Connect Salesforce Cloud and its 17 tool definitions are loaded into the model's context on every request — 1.3% of a 200k window spent before your agent does anything.

QUICK ANSWER The Salesforce Cloud MCP server's tool definitions consume 2,551 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 17 tools · 2,551 tokens · 1.3% of 200k · 0.3% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 1.3%
1M WINDOW 0.3%

Corpus context: Salesforce Cloud ranks #1406 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 2,551 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 150 tokens per tool.

ToolCategoryTokens% of server
find_similar_opportunities Read 255 10.0%
opportunity_insights Read 251 9.8%
batch Execute 235 9.2%
search_opportunities Read 224 8.8%
describe_object Read 215 8.4%
analyze Read 202 7.9%
get_opportunity_details Read 165 6.5%
execute_soql Execute 158 6.2%
download_file Read 148 5.8%
update_record Write 124 4.9%
enrich_opportunity Read 119 4.7%
create_record Write 110 4.3%
generate_business_case Write 102 4.0%
analyze_conversation Read 76 3.0%
list_objects Read 73 2.9%
delete_record Destructive 66 2.6%
get_user_info Read 28 1.1%

Most agents use a handful of these tools. They pay for all 17.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (150 tokens each).

Grant scopeDefinition costReduction
All 17 tools (no gateway) 2,551 tokens
3 granted tools ~450 tokens −82%
5 granted tools ~750 tokens −71%
10 granted tools ~1,501 tokens −41%

Salesforce Cloud token-cost questions.

How many tokens does the Salesforce Cloud MCP server use?+

Its 17 tool definitions total 2,551 tokens — 1.3% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does Salesforce Cloud consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce Salesforce Cloud's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Salesforce Cloud to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 450 tokens, a 82% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 17 catalogued Salesforce Cloud tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes Salesforce Cloud to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.