Happy slice of mcp pizzaMCP.pizza

mcp-client-server

MCP.Pizza Chef: willccbb

Six tools let an assistant launch a half-built server from a folder on your computer, call one of its tools by hand, read its log file, list what is running, and shut it down. Despite a source file named after Docker and a Docker library in the project, nothing is ever placed in a container: the code just runs the folder's start command directly on your machine and hands it every environment setting your own session holds. The named test suite you pass in is ignored. No licence is attached, and the code has not changed since March 2025.

Unmaintained · No commits in 18 months.
Coding

Use This MCP server To

Start a server I am building without restarting my chat app Call one tool by hand and see what comes back Read the log a misbehaving server just wrote List which test servers are still running Shut down a test server when I am finished

README

MCP Test Client

An MCP middleware that acts as both a server (to Claude) and a client (to servers under test) for testing MCP servers during development.

Architecture

The MCP Test Client has a dual role:

  • It's a server registered with Claude that exposes tools for testing
  • It's a client that connects to and tests other MCP servers
┌─────────────┐          ┌───────────────────┐          ┌────────────────┐
│             │  Tools   │                   │  Client  │                │
│   Claude    │─────────>│  MCP Test Client  │─────────>│  Server Under  │
│             │          │                   │          │     Test       │
└─────────────┘          └───────────────────┘          └────────────────┘

This architecture lets you test MCP servers without registering them directly with Claude.

Features

  • Deploy MCP servers to test environments
  • Call individual tools with custom arguments
  • Run automated test suites
  • View server logs
  • Test servers before formal registration with Claude

Implementation

The MCP Test Client is implemented with:

  • Process Management: Spawns and manages MCP server processes
  • MCP SDK Client: Uses the official MCP SDK to communicate with servers
  • Custom Transport: Implements a custom transport for stdio communication
  • Test Execution: Runs tests and validates responses
  • CLI Interface: Provides an interactive testing interface

The current implementation is Phase 1 of the design plan, with future enhancements planned for Phases 2 and 3.

Installation

# Install dependencies
npm install

# Build the TypeScript project
npm run build

mcp-client-server FAQ

Who is this actually for?
People writing their own MCP servers. If you just want your assistant to do a task like reading email or searching the web, this does nothing for you.
Does it run other people's code safely, in a sandbox?
No, and this is the thing to know. A Docker library is bundled and one file is named after it, but no container is ever created. Your assistant's chosen folder is run straight on your computer, inheriting every setting and secret already in your session.
Can I test a server written in Python?
No. It insists on finding a package.json file, so only servers built with Node work.
Can I run my own saved test file against a server?
No. The test-suite name is accepted and then thrown away. It only calls every tool with empty input. Four example test files sit in the project and no code ever opens them.
Do I need an API key?
Not for the tool itself. Any keys involved belong to the server you are testing, and it simply passes them through.
Is it still maintained?
The last change was March 2025. The notes describe a phase two and three, including the real container support, and neither arrived.
Can I use this at work?
Be careful. There is no licence file at all, which by default means nobody has permission to reuse it. Check with whoever handles that where you work.
How hard is setup?
You clone the code, install its parts, build it, and register it by hand. This is a developer tool through and through.