Home / Token cost / Better Bear

The Better Bear MCP server costs 4,063 tokens before the first call.

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

QUICK ANSWER The Better Bear MCP server's tool definitions consume 4,063 tokens — 2.1× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 35 tools · 4,063 tokens · 2.0% of 200k · 0.4% 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 2.0%
1M WINDOW 0.4%

Corpus context: Better Bear ranks #1139 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 4,063 tokens go.

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

ToolCategoryTokens% of server
bear_edit_note Write 264 6.5%
bear_create_note Write 243 6.0%
bear_context_triage Read 232 5.7%
bear_list_notes Read 229 5.6%
bear_attach_file Write 208 5.1%
bear_search Read 194 4.8%
bear_context_import Write 193 4.8%
bear_context_setup Write 157 3.9%
bear_get_note Read 153 3.8%
bear_context_set_prefix Write 148 3.6%
bear_context_push_to_bear Write 140 3.4%
bear_remove_tag Destructive 114 2.8%
bear_add_tag Write 111 2.7%
bear_context_add Write 110 2.7%
bear_context_sync Write 109 2.7%
bear_context_fetch Read 103 2.5%
bear_context_search Read 99 2.4%
bear_toggle_todo Read 99 2.4%
bear_sync Execute 82 2.0%
bear_archive_note Write 82 2.0%
bear_rename_tag Write 82 2.0%
bear_get_todos Read 75 1.8%
bear_list_todos Read 73 1.8%
bear_context_ingest Write 73 1.8%
bear_trash_note Destructive 72 1.8%
bear_context_index Read 72 1.8%
bear_context_remove_external Destructive 71 1.7%
bear_context_status Read 70 1.7%
bear_health_check Read 70 1.7%
bear_context_remove Destructive 64 1.6%
bear_note_stats Read 62 1.5%
bear_delete_tag Destructive 58 1.4%
bear_find_duplicates Read 52 1.3%
bear_find_untagged Read 51 1.3%
bear_get_tags Read 48 1.2%

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

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

Grant scopeDefinition costReduction
All 35 tools (no gateway) 4,063 tokens
3 granted tools ~348 tokens −91%
5 granted tools ~580 tokens −86%
10 granted tools ~1,161 tokens −71%

Better Bear token-cost questions.

How many tokens does the Better Bear MCP server use?+

Its 35 tool definitions total 4,063 tokens — 2.0% 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 Better Bear 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 Better Bear's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Better Bear 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 348 tokens, a 91% 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 35 catalogued Better Bear tools. Counts refresh with every site build.

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

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