5 posts tagged #mcp.
Loop engineering's six building blocks are all context primitives wearing new names. The scheduling is cron. The part that decides whether the loop works is the context delivered on every iteration.
Prompt injection isn't an unsolvable model problem — it's a context-engineering one. Fence untrusted tool output as data in your rules, run a parallel guardrail hook that cancels on a hit, and cap the blast radius with a permissions allowlist.
Hand-writing an adapter for every external system is the contextless agent's biggest tax. An MCP server collapses the M×N integration blowup into one standard connection the agent discovers at runtime — scoped by permissions, configured once.
Hand-passing one plan per run keeps you inside the loop doing task selection for the agent. Pipe your whole issue tracker in and let it pick the next ticket itself.
MCP is the standard protocol for plugging external systems — issue trackers, databases, design tools — into AI agents. Every major tool added support for it this year. Here's what changes when you use it.