Skip to content

Add context-cost badge to markitdown-mcp (64 tokens — leanest of 57 measured servers) - #2309

Closed
Akshansh Thakur (athakur3) wants to merge 2 commits into
microsoft:mainfrom
athakur3:context-cost-badge
Closed

Add context-cost badge to markitdown-mcp (64 tokens — leanest of 57 measured servers)#2309
Akshansh Thakur (athakur3) wants to merge 2 commits into
microsoft:mainfrom
athakur3:context-cost-badge

Conversation

@athakur3

Copy link
Copy Markdown

One line in the markitdown-mcp README: a shields.io badge showing what the server's tool schemas cost in context tokens — currently 64 tokens for its single convert_to_markdown tool (measured 2026-08-16). That makes it literally the leanest of the 57 popular MCP servers we measured (median: 2,636; heaviest: 54,422) — a number worth wearing.

The badge JSON lives in our repo and refreshes weekly; it links to a reproducible methodology — raw tools/list capture + pinned o200k_base tokenizer, re-derivable in five lines from results/markitdown/measurement.json.

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).


[![context cost](https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fathakur3%2Fmcp-context-cost%2Fmain%2Fbadges%2Fmarkitdown.json)](https://athakur3.github.io/mcp-context-cost/METHODOLOGY)

> [!IMPORTANT]

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

test

@afourney

Copy link
Copy Markdown
Member

Thanks for the PR. It looks like an interesting project -- and I'm super supportive of it (see our work last year on MCP issues https://www.microsoft.com/en-us/research/blog/tool-space-interference-in-the-mcp-era-designing-for-agent-compatibility-at-scale/).

But, I'm not yet ready to add it as a badge. Perhaps we will revisit this in the future.

@afourney afourney closed this Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants