4 posts
A working MCP server in about 80 lines: two real tools, a resource, a prompt template, and the one design mistake that turns it into a security hole.
Not another 'agents are the future' piece. One real request, traced stage by stage through planning, memory, tool calls, MCP, evaluation, and back.
A chatbot answers. An agent acts, checks, and tries again. Here's the real architecture behind agent loops, tool calling, memory, and long-running tasks.
A deep architectural look at MCP: what problem it solves, how client-server and auth work, and what the July 2026 spec rewrite changed.
