TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Why MCP can't be as simple as Naive Context Protocol

4 pointsby hmdai8 days ago

1 comment

hmdai8 days ago
Since the introduction of Model Context Protocol, I&#x27;ve been wondering why this protocol is so complicated to work with and after many wasted hours and a few MCP spec updates, I&#x27;ve decided to write down what I think MCP should have been and I call it Naive Context Protocol ¯\_(ツ)_&#x2F;¯.<p>Maybe this approach is in fact naive (please tell why!), the &quot;spec&quot; is very minimal at this point (I will expand based on feedback here) and it probably ignores some use-case (some of them on purpose), but I would like to hear:<p>1. What everyone here thinks the MCP&#x2F;NCP should&#x27;ve been&#x2F;should be?<p>2. What use-cases would you like a context protocol to support?