MCP Is Not Good Yet
summary
Claims Sentry built a remote MCP server in a few days, wires it into VS Code Insiders and Cursor via a Cloudflare shim for OAuth 2.1, and exposes curated ops that returns markdown instead of raw JSON; a demo run triggers ~20 API queries and costs about $5, produces plausible but flaky fixes, and breaks when clients lack streaming tool responses or hit token limits. MCP works as a plugin arch but is still brittle.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:06What is MCP and its hype
- 3:11Why MCP matters for businesses
- 6:20Challenges with MCP implementation
- 8:07When to focus on remote MCP servers
- 10:12Designing MCP tools effectively
- 12:19Cost and token limits in MCP
- 13:02Building agents with MCP
- 15:05MCP is simpler than it seems
related talks
44mSupercharging DevOps with MCP (Without Opening a Security Hole)
35mMCP, or not MCP
25mAre MCP Servers Dead?
23mMCP = Mega Context Problem
30mLet's make an MCP Server!
55mYour MCP Server is Bad (and you should feel bad)
27mYour MCP Server is Bad (and You Should Feel Bad)
29mMCP in 2026: Context is All You Need