How are you testing your MCP servers? (I built a framework for it)

Published: 0 month ago (April 5, 2026 at 10:54 PM EDT)

1 min read

Source: Dev.to

Source: Dev.to

Introduction

There are over 12,000 MCP servers on GitHub and npm right now. I checked a bunch of them—almost none have tests.

Why there are no tests

It’s not because the developers are lazy. There simply isn’t a standard, obvious way to test an MCP server. You’d have to wire up the SDK manually, handle stdio transport, write your own assertions, and so on.

A solution: mcp‑test

I built @lachytonner/mcp-test — a Vitest‑based testing framework that works like Jest but for MCP servers.

(Code examples from the README would normally follow here.)

Back to Blog

Okay, What is Redis?

What is Redis? In simple words, Redis acts like a cache memory to store data as key‑value pairs. Without Redis, a website can take a long time to fetch data on...

Stop Wasting Tokens on npm Install Noise

Problem Running npm install in a medium‑sized project often produces dozens of deprecation warnings, e.g.: text npm warn deprecated inflight@1.0.6: This module...

Building Your First MCP Server: TypeScript vs. Python

The 5‑Minute “Hello World” Comparison Whether you are a TypeScript veteran or a Python enthusiast, building an MCP server is surprisingly simple. Below are “He...

Git bisect saved me from a week of debugging. Should've used it sooner.

Two weeks ago, my coworker merged a feature branch on Friday afternoon. By Monday morning, half our test suite was red. Nobody knew which commit broke things. T...