Originally published on AI Tech Connect.
What you need to know Most people who build a Model Context Protocol server stop at the first two primitives. They expose a handful of tools the model can call, maybe a few resources it can read, and ship it. That gets you a long way — an agent that can query your database, file a ticket or fetch a document. But it leaves the server in a purely reactive posture: it waits to be called, does the one thing, and returns. It cannot reason. It cannot ask. If you have built your first MCP server with FastMCP and wondered how to make it do something more collaborative, this guide is the next step. The two primitives that change the game are sampling and elicitation, and the quickest way to hold them in your head is by who the server is talking to. With sampling, a server pauses mid-task and asks…
Top comments (0)