Home / Token cost / Markdown

The Markdown MCP server costs 8,635 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 34 tools · 8,635 tokens · 4.3% of 200k · 0.9% 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 4.3%
1M WINDOW 0.9%

Corpus context: Markdown ranks #213 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 8,635 tokens go.

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

ToolCategoryTokens% of server
convert_to_pdf Write 431 5.0%
convert_to_image Write 419 4.9%
convert_to_md Write 390 4.5%
convert_to_docx Write 379 4.4%
convert_to_xlsx Write 376 4.4%
convert_to_xml Write 373 4.3%
batch_convert Write 368 4.3%
convert_to_html Write 368 4.3%
convert_to_json Write 363 4.2%
convert_to_latex Write 356 4.1%
harmonize_markdown Write 345 4.0%
convert_to_txt Destructive 331 3.8%
convert_to_csv Write 330 3.8%
convert_to_rtf Write 314 3.6%
generate_html Write 310 3.6%
convert_to_slack Write 217 2.5%
convert_to_jira Write 216 2.5%
convert_to_bbcode Write 212 2.5%
convert_to_email_html Write 210 2.4%
convert_to_asciidoc Write 208 2.4%
convert_to_orgmode Write 208 2.4%
convert_to_mediawiki Write 200 2.3%
convert_to_rst Write 200 2.3%
convert_to_confluence Write 198 2.3%
convert_to_discord Write 196 2.3%
convert_to_textile Write 188 2.2%
html_to_markdown Read 184 2.1%
repair_markdown Read 175 2.0%
lint_markdown Read 115 1.3%
generate_toc Write 110 1.3%
extract_structure Read 92 1.1%
extract_links Read 88 1.0%
extract_code_blocks Read 84 1.0%
analyze_document Read 81 0.9%

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

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

Grant scopeDefinition costReduction
All 34 tools (no gateway) 8,635 tokens
3 granted tools ~762 tokens −91%
5 granted tools ~1,270 tokens −85%
10 granted tools ~2,540 tokens −71%

Markdown token-cost questions.

How many tokens does the Markdown MCP server use?+

Its 34 tool definitions total 8,635 tokens — 4.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 Markdown 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 Markdown's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Markdown 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 762 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 34 catalogued Markdown tools. Counts refresh with every site build.

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

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