Your PowerShell Scripts Are Already MCP Tools. You Just Don't Know It Yet

About this event

I'm going to open with the trick and then show you how it works. VS Code is open, chat is running, and the agent has a set of tools. I drop a plain PowerShell script into a folder. A few seconds later it shows up in chat, ready to use. I don't restart anything, reconnect anything, or write any glue code. That's PSMcpServer, a native PowerShell streamable-HTTP MCP server. Point it at a folder of scripts and it reads the param blocks, builds the tool schemas, and serves them. Turn on \-Watch\ and the folder stays live. Add a file and the tool list updates. Edit a signature and the client gets notified. Then it gets interesting: • Your existing modules become tools. • Pipe \Get-Command\ into one cmdlet and you get a curated tool config. • Tools that return UI. A few lines of PowerShell render as sortable tables and live forms right inside chat. No HTML, no JavaScript. • Agents that build their own tools. If the agent can write a script into that folder, it can extend its own toolbox mid-session. That's the part that should change how you think about harnesses. I also built the whole thing without touching the plumbing code myself. I'll show how that worked too, including handing the hardest bug to an AI with computer use and watching it dig the fix out of the logs. The language is incidental. The pattern isn't. Come see it run. About the Host Doug Finke is a 16-time Microsoft MVP, author of PowerShell for Developers, and creator of ImportExcel, PSAI, and PSClaudeCode. His work focuses on practical agentic AI: using scripts, shells, CLIs, and AI tools to build repeatable automation.