Home / Token cost / Kernelcad

The Kernelcad MCP server costs 11,038 tokens before the first call.

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

QUICK ANSWER The Kernelcad MCP server's tool definitions consume 11,038 tokens — 5.8× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 48 tools · 11,038 tokens · 5.5% of 200k · 1.1% 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 5.5%
1M WINDOW 1.1%

Corpus context: Kernelcad ranks #155 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 11,038 tokens go.

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

ToolCategoryTokens% of server
design_loop Execute 758 6.9%
add_hermite_g2 Write 553 5.0%
emboss_text Read 523 4.7%
trace_from_image Execute 513 4.6%
add_path_hermite_g2 Write 480 4.3%
add_surface_from_boundary Write 467 4.2%
add_nurbs_surface Write 465 4.2%
add_pattern_feature Write 448 4.1%
review_cad Execute 441 4.0%
add_path_nurbs_segment Write 421 3.8%
add_path_spline Write 387 3.5%
add_variable_sweep Write 387 3.5%
add_nurbs_curve Write 354 3.2%
project_curve Read 332 3.0%
add_sketch_text Write 327 3.0%
add_mate Write 278 2.5%
add_connector Write 259 2.3%
evaluate_sdf Read 240 2.2%
export_stl Write 196 1.8%
add_feature Write 183 1.7%
get_face_lineage Read 177 1.6%
list_edges Read 174 1.6%
lookup_cookbook Read 171 1.5%
list_faces Read 160 1.4%
list_face_labels Read 146 1.3%
set_param_value Write 137 1.2%
solve_sketch Write 129 1.2%
inspect_assembly Read 126 1.1%
params_update Write 124 1.1%
lookup_authoring_skill Read 121 1.1%
remove_feature Destructive 115 1.0%
get_edges_of Read 113 1.0%
list_api Read 109 1.0%
get_shape_info Read 108 1.0%
why_did_this_fail Read 108 1.0%
flatten_pattern Read 98 0.9%
evaluate_script Execute 95 0.9%
solve_mates Execute 93 0.8%
list_topology Read 92 0.8%
list_assemblies Read 91 0.8%
list_features Read 85 0.8%
get_bend_table Read 75 0.7%
list_diagnostic_codes Read 74 0.7%
list_mates Read 73 0.7%
add_constraint Write 69 0.6%
validate_assembly Read 66 0.6%
list_constraints Read 56 0.5%
params_list Read 41 0.4%

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

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 (230 tokens each).

Grant scopeDefinition costReduction
All 48 tools (no gateway) 11,038 tokens
3 granted tools ~690 tokens −94%
5 granted tools ~1,150 tokens −90%
10 granted tools ~2,300 tokens −79%

Kernelcad token-cost questions.

How many tokens does the Kernelcad MCP server use?+

Its 48 tool definitions total 11,038 tokens — 5.5% 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 Kernelcad 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 Kernelcad's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Kernelcad 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 690 tokens, a 94% 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 48 catalogued Kernelcad tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Kernelcad 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.