We tracked 29 MCP pain points across 7 communities. Which one would you actually pay to fix?

For the last two weeks, I've been doing something unusual: just listening. Reading GitHub issues, Reddit threads, X replies, and Discord servers where developers are building with MCP. Not pitching anything. Not collecting emails. Just cataloging every pain point mentioned, with sources. 29 distinct problems. 7 communities. Here's what kept showing up. The enterprise-scale evidence first Before I get to the patterns, some data points that landed hard: Cloudflare's standard MCP server consumed 1.17M tokens in production. That's not a benchmark — that's an emergency. They shipped a "Code Mode" workaround in February 2026 specifically because of it. Block rebuilt their Linear MCP integration 3 times for the same underlying reason: context destruction from schema overhead. Three rewrites, same root cause. Perplexity's CTO publicly moved away from MCP citing overhead as a core issue. One practitioner I found in a GitHub thread: 45K tokens just for GitHub MCP alone — that's 22.5% of a 200K c