| ▲ | thenewnewguy 2 hours ago | |
These AI slop articles about AI are getting especially boring to read. > Problem 1: It Devours the Context Window Don't harnesses support progressive discovery these days? Claude (200K).... GPT-4o..........? > every MCP server adds a process layer between the LLM and the underlying API But a CLI doesn't? ------------------ > Measurement: Tool Definition Sizes > MCP Server: Linear, Notion, Slack, Postgres Oh, so these are the MCP servers that are examples of context bloat we're going to replace! Later in the article: > At Quandri we use all three approaches side by side... > MCP for services without a strong CLI (Slack, Linear, Notion) | ||
| ▲ | kristopolous 2 hours ago | parent [-] | |
There's a fix for the context which involved an mcp search and execute gateway. Essentially the mcp server queries for desired capabilities, gets search results with execution and requirement details and fires off the actual mcp as subcalls: https://github.com/day50-dev/mcp-search-and-run You can call it "rag for mcp". I was pushing it hard a few months ago and nobody seemed to care but I'm all in if the timing has caught up to the tech. It's nontrivial effort: basically a giant survey of all the mcp servers, running inference over them to figure out how to instrument them, cross referencing to make sure they are the "official" sources (or at least the ones that search engines think are) then using qdrant to do embeddings and reranking and offering it for free. If people have become interested I'm all in. I'll bring the infra back up. I just don't want to spin my wheels on dead end streets. The value proposition is solid, the problem is real, this fix works, it's fast, it's free, and people give exactly zero shits. I dunno... One day I'll figure it out, hopefully... | ||