Home / Token cost / Discource Mcp Tools

The Discource Mcp Tools MCP server costs 2,151 tokens before the first call.

Connect Discource Mcp Tools and its 15 tool definitions are loaded into the model's context on every request — 1.1% of a 200k window spent before your agent does anything.

QUICK ANSWER The Discource Mcp Tools MCP server's tool definitions consume 2,151 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 15 tools · 2,151 tokens · 1.1% of 200k · 0.2% 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.1%
1M WINDOW 0.2%

Corpus context: Discource Mcp Tools ranks #1525 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,151 tokens go.

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

ToolCategoryTokens% of server
discourse_get_chat_messages Read 321 14.9%
search_discourse_communities Read 310 14.4%
discourse_filter_topics Read 289 13.4%
discourse_read_topic Read 168 7.8%
discourse_list_chat_channels Read 157 7.3%
discourse_search Read 157 7.3%
discourse_list_user_posts Read 138 6.4%
discourse_get_draft Read 120 5.6%
discourse_select_site Write 96 4.5%
discourse_read_post Read 84 3.9%
discourse_get_user Read 79 3.7%
discourse_list_drafts Read 79 3.7%
discourse_list_tags Read 54 2.5%
discourse_list_user_chat_channels Read 52 2.4%
discourse_list_categories Read 47 2.2%

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

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

Grant scopeDefinition costReduction
All 15 tools (no gateway) 2,151 tokens
3 granted tools ~430 tokens −80%
5 granted tools ~717 tokens −67%
10 granted tools ~1,434 tokens −33%

Discource Mcp Tools token-cost questions.

How many tokens does the Discource Mcp Tools MCP server use?+

Its 15 tool definitions total 2,151 tokens — 1.1% 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 Discource Mcp Tools 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 Discource Mcp Tools's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Discource Mcp Tools 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 430 tokens, a 80% 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 15 catalogued Discource Mcp Tools tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Discource Mcp Tools 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.