> Over time the limitations of MCP have started to emerge. The most significant is in terms of token usage: GitHub’s official MCP on its own famously consumes tens of thousands of tokens of context, and once you’ve added a few more to that there’s precious little space left for the LLM to actually do useful work. Supabase MCP really devours your context window. IIRC, it uses 8k for its search_docs tool alone, just on…
It's also not clear to me why using "skills" would consume less context once invoked. It's just instructions with RAG. The more I read about this the more convinced I am that this is just marketing.
That's why it's common advice to turn off MCPs for tools you dont think are relevant to the task at hand.
The idea behind skills us that they're progressively unlocked: they only take up a short description in the context, relying on the agent to expand things if it feels it's relevant.