Post

okay sorry to my mcp-hating oomfs but I might be mcp-pilled

0 reposts43 likes

It was initially a huge context slob, but now that most harnesses support tool-discovery and MCP 2.0 decided on a senseful stateless API i can accept it.

it actually reliably executes without flooding the context window, and it allows it to communicate over a sensible json schema without shell noise.

I thought it was poorly designed and had a lot of protocol noise that flooded the context window? Rest makes sense

yeah good luck reliably teaching your agent how to use a novel REST api, esp a REST api that is niche or doesn't really exist publicly. it's far more natural for it to be a tool call available to it.

i have an mcp that hosts a clangd server plus a skill to use it to perform LSP queries against a codebase that allows for the language server to persist across calls

mcp apps is fire, I didn’t know mcp was like that but now it is

yea idk if there’s any that work in the terminal? hmm in web ui chats they are v cool map and calendar are basic examples where me n my agent can get on the same page much better than via prose, you can imagine others