Home / Token cost / Memento

The Memento MCP server costs 2,098 tokens before the first call.

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

QUICK ANSWER The Memento MCP server's tool definitions consume 2,098 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 17 tools · 2,098 tokens · 1.0% 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.0%
1M WINDOW 0.2%

Corpus context: Memento ranks #1541 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,098 tokens go.

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

ToolCategoryTokens% of server
create_relations Write 297 14.2%
update_relation Write 283 13.5%
add_observations Write 246 11.7%
create_entities Write 215 10.2%
semantic_search Read 191 9.1%
delete_relations Destructive 118 5.6%
delete_observations Destructive 103 4.9%
get_relation Read 88 4.2%
get_relation_history Read 88 4.2%
get_decayed_graph Read 82 3.9%
get_graph_at_time Read 60 2.9%
delete_entities Destructive 58 2.8%
search_nodes Read 57 2.7%
get_entity_embedding Read 56 2.7%
open_nodes Write 56 2.7%
get_entity_history Read 54 2.6%
read_graph Read 46 2.2%

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

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

Grant scopeDefinition costReduction
All 17 tools (no gateway) 2,098 tokens
3 granted tools ~370 tokens −82%
5 granted tools ~617 tokens −71%
10 granted tools ~1,234 tokens −41%

Memento token-cost questions.

How many tokens does the Memento MCP server use?+

Its 17 tool definitions total 2,098 tokens — 1.0% 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 Memento 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 Memento's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Memento 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 370 tokens, a 82% 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 17 catalogued Memento tools. Counts refresh with every site build.

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

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