Home / Token cost / OpenAccountants

The OpenAccountants MCP server costs 2,966 tokens before the first call.

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

QUICK ANSWER The OpenAccountants MCP server's tool definitions consume 2,966 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 13 tools · 2,966 tokens · 1.5% 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.5%
1M WINDOW 0.3%

Corpus context: OpenAccountants ranks #1310 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 2,966 tokens go.

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

ToolCategoryTokens% of server
request_accountant_review Read 708 23.9%
plan_cross_border Write 531 17.9%
compare_jurisdictions Read 324 10.9%
start Execute 226 7.6%
submit_feedback Write 222 7.5%
get_rates Read 190 6.4%
get_skill_sections Read 161 5.4%
search_skills Read 120 4.0%
list_skills Read 110 3.7%
list_verifiers Read 109 3.7%
list_jurisdictions Read 96 3.2%
start_help Execute 89 3.0%
get_skill Read 80 2.7%

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

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

Grant scopeDefinition costReduction
All 13 tools (no gateway) 2,966 tokens
3 granted tools ~684 tokens −77%
5 granted tools ~1,141 tokens −62%
10 granted tools ~2,282 tokens −23%

OpenAccountants token-cost questions.

How many tokens does the OpenAccountants MCP server use?+

Its 13 tool definitions total 2,966 tokens — 1.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 OpenAccountants 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 OpenAccountants's token usage?+

Expose fewer tools. A PolicyLayer grant scopes OpenAccountants 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 684 tokens, a 77% 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 13 catalogued OpenAccountants tools. Counts refresh with every site build.

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

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