Home / Token cost / Colour Memory

The Colour Memory MCP server costs 12,864 tokens before the first call.

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

QUICK ANSWER The Colour Memory MCP server's tool definitions consume 12,864 tokens — 6.8× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 65 tools · 12,864 tokens · 6.4% of 200k · 1.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 6.4%
1M WINDOW 1.3%

Corpus context: Colour Memory ranks #116 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 12,864 tokens go.

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

ToolCategoryTokens% of server
colour_strategy Write 463 3.6%
session_brief Write 407 3.2%
agent_brief Read 399 3.1%
interior_specify Write 365 2.8%
archive_report_brief Write 347 2.7%
brand_report Write 341 2.7%
style_match Write 334 2.6%
session_design Write 304 2.4%
ecommerce_copy Write 301 2.3%
colour_forensics Write 287 2.2%
brand_audit Write 286 2.2%
palette_generate Write 280 2.2%
colour_verdict Write 275 2.1%
image_personal Write 271 2.1%
ecommerce_namer Read 269 2.1%
palette_verdict Write 264 2.1%
archive_cultural_anachronism Write 263 2.0%
brand_collision Write 256 2.0%
archive_evidence_gap Write 255 2.0%
index_resonance Read 243 1.9%
archive_cliche Write 240 1.9%
image_palette Write 223 1.7%
palette_translate Read 222 1.7%
palette_strict Write 212 1.6%
palette_iterate Write 202 1.6%
archive_search Write 200 1.6%
archive_coverage_gap Write 199 1.5%
colour_hooks Write 198 1.5%
palette_pdf Write 195 1.5%
colour_mix Write 188 1.5%
agent_verify Read 186 1.4%
brand_system Write 184 1.4%
colour_namer Write 183 1.4%
colour_cultural_risk Write 182 1.4%
palette_concept Write 182 1.4%
ui_states Write 176 1.4%
palette_heritage Write 167 1.3%
colour_compare Write 162 1.3%
colour_dna Write 159 1.2%
palette_audit Read 156 1.2%
archive_audit Write 155 1.2%
brand_asset_pack Write 155 1.2%
palette_export Write 150 1.2%
query_conceptual Read 147 1.1%
archive_provenance Write 147 1.1%
colour_story Write 145 1.1%
palette_compare Write 145 1.1%
colour_timeline Read 140 1.1%
accessibility_matrix Read 135 1.0%
palette_specify Write 135 1.0%
colour_combination Write 126 1.0%
palette_light_dark Write 111 0.9%
colour_match_paint Write 110 0.9%
query_hex Read 107 0.8%
colour_slugs Write 103 0.8%
colour_card Write 101 0.8%
accessibility_font Write 95 0.7%
accessibility_rules Write 93 0.7%
colour_metrics Write 92 0.7%
colour_harmonies Write 91 0.7%
accessibility_check Read 84 0.7%
accessibility_simulate Write 76 0.6%
meta_capabilities Read 75 0.6%
colour_variants Write 72 0.6%
archive_status Write 48 0.4%

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

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

Grant scopeDefinition costReduction
All 65 tools (no gateway) 12,864 tokens
3 granted tools ~594 tokens −95%
5 granted tools ~990 tokens −92%
10 granted tools ~1,979 tokens −85%

Colour Memory token-cost questions.

How many tokens does the Colour Memory MCP server use?+

Its 65 tool definitions total 12,864 tokens — 6.4% 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 Colour Memory 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 Colour Memory's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Colour Memory 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 594 tokens, a 95% 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 65 catalogued Colour Memory tools. Counts refresh with every site build.

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

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