{
  "id": 16006030,
  "title": "Browser MCP token cost: 68 runs of Playwright MCP vs Chrome DevTools MCP, and a proxy that cuts snapshots by up to 96%",
  "url": "https://urgent.news/2026/10/22/browser-mcp-token-cost-68-runs-of-playwright-mcp-vs-chrome-devtools",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-22T06:06:30.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jaehyun_cho_0dff271e0d2e5/browser-mcp-token-cost-68-runs-of-playwright-mcp-vs-chrome-devtools-mcp-and-a-proxy-that-cuts-1ee"
  },
  "original_language": "en",
  "account": "When hooking up a browser MCP server to Claude Code, it can burn tokens, with estimates ranging from 10,000 to 50,000 tokens per page look. To test this, the author measured Microsoft Playwright MCP and Google Chrome DevTools MCP. Using Playwright MCP 0.0.83 and Chrome DevTools MCP 1.11.0, both headless, 68 runs were conducted, totaling 68 MCP runs.\n\nPlaywright MCP input tokens for everyday tasks averaged 178,408 tokens ($0.19) and Chrome DevTools MCP input tokens 199,737 tokens ($0.22). The average cost per run was $0.205 for Playwright and $0.236 for Chrome DevTools. Everyday tasks were lighter than expected, with only a small percentage of the total cost.\n\nHowever, reading long pages in one go can cost over 200,000 tokens, and at OpenAI's o200k tokenizer, this comes out more than 50% larger than Claude's count. Text with many link targets and element IDs is especially expensive for Claude's tokenizer. Fortunately, Claude Code already prevents this by refusing the result as too large and saving it to a file.\n\nA proxy tool, tokensave-mcp-diet, was built to cut the cost by compacting large snapshots, sending only relevant elements, and allowing on-demand access to the full snapshot. Using this proxy on Hacker News and Wikipedia showed an average 63% reduction in tokens for Hacker News and a 96% reduction for Wikipedia, resulting in significant cost savings.\n\nThe key takeaway is that most of the browser-MCP bill is the number of steps, not the page size. Asking for specific elements or short scripts can reduce costs, and using a proxy like tokensave-mcp-diet can further minimize expenses.",
  "summary": "You often hear that hooking a browser MCP server up to Claude Code burns tokens, and some posts put it at 10,000 to 50,000 tokens every time the agent looks at a page. I wanted to know whether that holds up, and whether it can be reduced, so I measured the two most popular servers: Microsoft's Playwright MCP and Google's Chrome DevTools MCP. Along the way I ended up building a small tool to cut…",
  "key_points": [
    "Playing Playwright MCP 68 times cost 0.19 USD per run",
    "Chrome DevTools MCP cost 0.22 USD per run, totaling 0.236 USD per run",
    "Proxy tool tokensave-mcp-diet cuts tokens by up to 96%"
  ],
  "editors_take": "Optimizing how browser MCP servers transmit snapshots through compacting tools shifts the focus from managing page size to reducing the high token costs driven by repetitive interaction steps.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}