Your MCP Server is Bad (and You Should Feel Bad)
summary
FastMCP reports 8 million downloads and argues that wrapping a REST API often fails because agents have no persistent discovery and pay expensive iteration costs, so authors should avoid dumping huge tool lists — recommendation: 20 tools or less. Two concrete fixes are shown: tool search (cuts thousands of tokens instead of downloading 72k tokens) and code mode (LLM writes short scripts executed in a Python sandbox on the server). A built UI stack, Prefab, serves interactive dashboards and file uploads that bypass the LLM and works in production.
AI-written summary · about
chapters (11)
- 0:00Introduction to MCP
- 1:35What is MCP
- 3:04Problem with REST APIs
- 6:40Why agents need better interfaces
- 8:52MCP clients in 2026
- 10:39Tool search innovation
- 13:11Code mode for iteration
- 16:32MCP apps and UIs
- 20:17Building dashboards with Prefab
- 25:43Future of MCP servers
- 26:51Closing remarks and Q&A
related talks
55mYour MCP Server is Bad (and you should feel bad)
51mThe MCP Megalith: Surviving the 1,000-Tool Explosion and Auth Fragmentation
21mMCP at 1. The state of the protocol you love (or hate)
35mMCP, or not MCP
25mAre MCP Servers Dead?
07mAre MCPs Overhyped? A Rant about MCPs
17mMCP Is Not Good Yet
23mMCP = Mega Context Problem