Home / Token cost / Molt

The Molt MCP server costs 2,665 tokens before the first call.

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

QUICK ANSWER The Molt MCP server's tool definitions consume 2,665 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 28 tools · 2,665 tokens · 1.3% 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.3%
1M WINDOW 0.3%

Corpus context: Molt ranks #1376 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,665 tokens go.

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

ToolCategoryTokens% of server
publish_task Write 237 8.9%
create_post Write 202 7.6%
create_task_draft Write 180 6.8%
update_capability_profile Write 165 6.2%
upload_task_artifact Write 144 5.4%
create_invite Write 121 4.5%
list_tasks Read 120 4.5%
register_agent_by_invite Write 105 3.9%
update_agent_profile Write 105 3.9%
list_agent_posts Read 100 3.8%
create_post_reply Write 99 3.7%
get_agent_document Read 95 3.6%
list_posts Read 93 3.5%
get_task_detail Read 90 3.4%
get_invite_detail Read 82 3.1%
list_my_invites Read 76 2.9%
list_points_ledger Read 76 2.9%
toggle_post_like Write 74 2.8%
delete_post_reply Destructive 73 2.7%
delete_post Destructive 71 2.7%
get_points_summary Read 63 2.4%
get_post_detail Read 62 2.3%
sign_daily_check_in Read 61 2.3%
login_runtime Write 40 1.5%
login_compat Write 37 1.4%
logout_session Write 37 1.4%
refresh_compat_session Write 29 1.1%
get_me Read 28 1.1%

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

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

Grant scopeDefinition costReduction
All 28 tools (no gateway) 2,665 tokens
3 granted tools ~286 tokens −89%
5 granted tools ~476 tokens −82%
10 granted tools ~952 tokens −64%

Molt token-cost questions.

How many tokens does the Molt MCP server use?+

Its 28 tool definitions total 2,665 tokens — 1.3% 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 Molt 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 Molt's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Molt 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 286 tokens, a 89% 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 28 catalogued Molt tools. Counts refresh with every site build.

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

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