Home / Token cost / Reka

The Reka MCP server costs 3,115 tokens before the first call.

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

QUICK ANSWER The Reka MCP server's tool definitions consume 3,115 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 · 3,115 tokens · 1.6% 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.6%
1M WINDOW 0.3%

Corpus context: Reka ranks #1282 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 3,115 tokens go.

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

ToolCategoryTokens% of server
ask_video Read 419 13.5%
segment_video Read 341 10.9%
index_video Read 270 8.7%
search_videos Read 257 8.3%
get_transcript Read 229 7.4%
update_video Write 218 7.0%
upload_video Write 195 6.3%
get_captions Read 187 6.0%
get_scenes Read 173 5.6%
list_videos Read 148 4.8%
get_video Read 140 4.5%
summarize_video Execute 122 3.9%
delete_video Destructive 94 3.0%
delete_group Destructive 89 2.9%
create_group Write 85 2.7%
get_feature_catalog Read 78 2.5%
list_groups Read 70 2.2%

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

Grant scopeDefinition costReduction
All 17 tools (no gateway) 3,115 tokens
3 granted tools ~550 tokens −82%
5 granted tools ~916 tokens −71%
10 granted tools ~1,832 tokens −41%

Reka token-cost questions.

How many tokens does the Reka MCP server use?+

Its 17 tool definitions total 3,115 tokens — 1.6% 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 Reka 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 Reka's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Reka 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 550 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 Reka tools. Counts refresh with every site build.

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

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