
Ben Nevile
2.1K posts

Ben Nevile
@saoul
father of 3, husband of @amykaufman84, musician and CTO / builder. working on context engineering for dev agents. https://t.co/nMiN782Oz1





@simonw While technically true, that is not necessarily a great feature. I have a harness for MCP that materializes MCP tool calls across sessions and when the MCP changes, the materialized calls no longer work.

MCP is mostly nonsense, but there are good effects: 1. Tricks management to green-light engineering efforts on APIs and OAuth DCR (Dynamic Client Registration) 2. Tricks LLM clients to integrate with everyone, ie an open-ecosystem, not walled gardens 3. (Just discovered this one today) The fact that MCP is a difference surface from your normal API allows you to ship MUCH faster to MCP. This has been unlocked by inference at runtime Normal APIs are promises to developers, because developer commit code that relies on those APIs, and then walk away. If you break the API, you break the promise, and you break that code. This means a developer gets woken up at 2am to fix the code But MCP servers are called my LLMs which dynamically read the spec every time, which allow us to constantly change the MCP server. It doesn't matter! We haven't made any promises. The LLM can figure it out afresh every time This is why we've shipped capabilities to our MCP server that our API doesn't yet have. We aren't worried about committing ourselves to anything. We can always change the MCP server later and the LLM will figure it out












@GaryMarcus intelligent humans scraped their language from other intelligent humans


@farukguney @GaryMarcus I like the phrase... it has a beautiful ring to it. The problem is, as Einstein said, everything is relative. More accurately, the illusion is seeing small steps as giant leaps. Meanwhile, LLMs spin an illusion of sentience, as they use language scraped from intelligent humans.



