Home / Token cost / Kibana

The Kibana MCP server costs 4,383 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 16 tools · 4,383 tokens · 2.2% 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.2%
1M WINDOW 0.4%

Corpus context: Kibana ranks #1095 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,383 tokens go.

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

ToolCategoryTokens% of server
vl_search_saved_objects Read 957 21.8%
vl_create_saved_object Write 574 13.1%
vl_update_saved_object Write 522 11.9%
vl_bulk_update_saved_objects Write 497 11.3%
vl_bulk_delete_saved_objects Destructive 405 9.2%
vl_get_saved_object Read 389 8.9%
execute_kb_api Execute 164 3.7%
analyze_object_dependencies Read 144 3.3%
get_kibana_api_detail Read 126 2.9%
analyze_deletion_impact Read 121 2.8%
check_dashboard_health Read 119 2.7%
scan_all_dashboards_health Read 101 2.3%
get_available_spaces Read 74 1.7%
search_kibana_api_paths Read 70 1.6%
get_status Read 69 1.6%
list_all_kibana_api_paths Read 51 1.2%

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

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

Grant scopeDefinition costReduction
All 16 tools (no gateway) 4,383 tokens
3 granted tools ~822 tokens −81%
5 granted tools ~1,370 tokens −69%
10 granted tools ~2,739 tokens −38%

Kibana token-cost questions.

How many tokens does the Kibana MCP server use?+

Its 16 tool definitions total 4,383 tokens — 2.2% 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 Kibana 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 Kibana's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Kibana 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 822 tokens, a 81% 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 16 catalogued Kibana tools. Counts refresh with every site build.

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

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