Add context-cost badge (transparency for the stdio server's schema size) - #344
Open
athakur3 wants to merge 1 commit into
Open
Add context-cost badge (transparency for the stdio server's schema size)#344athakur3 wants to merge 1 commit into
athakur3 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One line: a shields.io badge showing what the stdio notion-mcp-server's tool schemas cost in context tokens — currently 17,500 tokens across 24 tools (measured 2026-08-16). This is neutral transparency users ask for when budgeting context windows — not a judgment; a full-API server naturally carries more schema than a single-purpose one, and your README already points users to the leaner remote Notion MCP.
The per-tool breakdown may be independently useful:
API-update-page-markdown(1,282),API-post-search(1,097), andAPI-patch-page(889) lead, mostly via inputSchema depth — full capture in results/notion/measurement.json. Median across the 57 popular servers we measured: 2,636.The badge JSON refreshes weekly and links to a reproducible methodology (raw
tools/listcapture + pinnedo200k_basetokenizer, re-derivable in five lines). If you'd rather not carry this, close freely — no hard feelings. To own the number in your own CI instead: sd2k/mcp-tokens-action (badge support proposed in sd2k/mcp-tokens-action#5).