The job of a software engineer is rapidly evolving. We're now beyond using AI as a Stack Overflow alternative or even as a pair programmer. Agentic engineering - the act of building and maintaining a system to reliably give coding agents the tools and context they need to complete work autonomously - is the new layer of abstraction the industry is moving toward.
Core to building these autonomous coding agents is the notion of a "closed agentic loop". To create a closed loop for your coding agent, you need to provide it (1) tools to verify work is complete, (2) tools to debug work along the way, and (3) a carefully crafted prompt that communicates a "definition of done" that pulls it all together. That empowers your agent to iterate on solutions - sometimes for hours - until it delivers to completion.
As you might imagine, MCP is often the ideal delivery mechanism for those loop-closing tools.
In this workshop, we will:
Introduce the concept of agentic engineering and the "aha" moments that can take you from pair programming with a single agent to regularly wielding 5-10 coding agents at once.
Close a simple loop: Figma design to working, pixel-perfect UI element verified by Playwright.
Close a more complex loop: take an alert from an observability platform, reproduce the problem in a staging environment with Playwright, capture the logs, open a PR with a fix, deploy to staging, verify the fix, and close the alert - all in one prompt.
Encourage you to try building a loop on your own codebase for a real piece of work on your plate - and raise to the group what kind of hurdles you might run into while trying to do so
You'll leave with actionable next steps to make your team's codebase agentic-engineering-ready and a clear picture of what success looks like.
Pre-registration and additional fee is required. To register: add it to your
MCP Dev Summit North America registration.
