Home / Token cost / Kai

The Kai MCP server costs 1,519 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 18 tools · 1,519 tokens · 0.8% of 200k · 0.2% 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 0.8%
1M WINDOW 0.2%

Corpus context: Kai ranks #1795 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 1,519 tokens go.

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

ToolCategoryTokens% of server
kai_checkpoint Read 188 12.4%
kai_checkpoint_now Execute 184 12.1%
kai_symbols Read 168 11.1%
kai_context Read 123 8.1%
kai_blame Read 96 6.3%
kai_impact Read 90 5.9%
kai_live_sync Read 89 5.9%
kai_lock Write 82 5.4%
kai_callees Read 66 4.3%
kai_callers Read 64 4.2%
kai_merge_check Write 64 4.2%
kai_dependents Read 51 3.4%
kai_dependencies Read 49 3.2%
kai_sync Read 49 3.2%
kai_tests Read 48 3.2%
kai_unlock Write 44 2.9%
kai_activity Read 34 2.2%
kai_stats Read 30 2.0%

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

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

Grant scopeDefinition costReduction
All 18 tools (no gateway) 1,519 tokens
3 granted tools ~253 tokens −83%
5 granted tools ~422 tokens −72%
10 granted tools ~844 tokens −44%

Kai token-cost questions.

How many tokens does the Kai MCP server use?+

Its 18 tool definitions total 1,519 tokens — 0.8% 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 Kai 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 Kai's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Kai 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 253 tokens, a 83% 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 18 catalogued Kai tools. Counts refresh with every site build.

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

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