The latest articles on DEV Community by lachy (@lachytonner). https://dev.to/lachytonner https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3863012%2Fa51a2a84-7497-4f69-8f4b-fa676d7f9db9.jpeg https://dev.to/lachytonner en lachy Mon, 06 Apr 2026 02:54:52 +0000 https://dev.to/lachytonner/how-are-you-testing-your-mcp-servers-i-built-a-framework-for-it-5clh https://dev.to/lachytonner/how-are-you-testing-your-mcp-servers-i-built-a-framework-for-it-5clh <p>There are over 12,000 MCP servers on GitHub and npm right now. I checked a bunch of them. Almost none have tests.<br> It's not because the developers are lazy. It's because there was no standard, obvious way to test an MCP server. You'd have to wire up the SDK manually, handle stdio transport, write your own assertions...<br> So I built <a class="mentioned-user" href="https://dev.to/lachytonner">@lachytonner</a>/mcp-test — a Vitest-based testing framework that works like Jest but for MCP servers...<br> (continue with code examples from README)</p> javascript mcp showdev testing