MCP Debug

Name: MCP Debug
Author: standardbeagle

by standardbeagleversion 1.1.6i★ –iRuns on your computer

Registry nameio.github.standardbeagle/mcp-debug

Install

Overview

Description from the maker (original English)

Debug and develop MCP servers with hot-swapping, session recording, and playback testing

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "debug": {
      "command": "npx",
      "args": [
        "-y",
        "@standardbeagle/mcp-debug"
      ]
    }
  }
}

Run this in your terminal

claude mcp add debug -- npx -y @standardbeagle/mcp-debug

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "debug": {
      "command": "npx",
      "args": [
        "-y",
        "@standardbeagle/mcp-debug"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "debug": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@standardbeagle/mcp-debug"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account standardbeagle, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32464 servers in this category
Published to the registry more recently than 1% of the other 32464 servers in this category
Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MCP Debug safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.6) reached the registry 10 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MCP Debug

A debugging and development tool for Model Context Protocol (MCP) servers.

MCP Debug enables rapid development and testing of MCP servers with hot-swapping, session recording, and automated playback testing.

Features

Hot-Swap Development

Replace server binaries without disconnecting MCP clients
Add/remove servers dynamically during development
Tool name preservation - same interface, new implementation
Graceful disconnect/reconnect workflow for binary replacement

Session Recording & Playback

Record JSON-RPC traffic for debugging and documentation
Playback client mode - replay requests to test servers
Playback server mode - replay responses to test clients
Regression testing with recorded sessions

Development Proxy

Multi-server aggregation with tool prefixing
Real-time connection monitoring
Management API for server lifecycle control
Comprehensive logging

Installation

# Using uvx (Python - recommended)

uvx mcp-debug --help

Using npx (Node.js)

npx @standardbeagle/mcp-debug --help

Or install globally

pip install mcp-debug # Python npm install -g @standardbeagle/mcp-debug # Node.js

Or build from source

go install github.com/standardbeagle/mcp-debug@latest

Quick Start

# Start proxy with a config file

uvx mcp-debug --proxy --config config.yaml

Or with mcp-tui for interactive testing

mcp-tui uvx mcp-debug --proxy --config config.yaml

Usage

Proxy Mode

# Basic proxy

uvx mcp-debug --proxy --config config.yaml

With recording

uvx mcp-debug --proxy --config config.yaml --record session.jsonl

With custom log file

uvx mcp-debug --proxy --config config.yaml --log /tmp/debug.log

Management Tools:

server_add - Add a server: {name: "fs", command: "npx -y @mcp/filesystem /path"}
server_remove - Remove server completely
server_disconnect - Disconnect server (tools return errors)
server_reconnect - Reconnect with new command
server_list - Show all servers and status

Playback Modes

# Replay recorded requests to test a server

uvx mcp-debug --playback-client session.jsonl | ./your-mcp-server

Replay recorded responses to test a client

mcp-tui uvx mcp-debug --playback-server session.jsonl

Configuration

# config.yaml

servers:

name: "filesystem" prefix: "fs" transport: "stdio" command: "npx" args: ["-y", "@modelcontextprotocol/filesystem", "/home/user"] timeout: "30s"

proxy: healthCheckInterval: "30s" connectionTimeout: "10s" maxRetries: 3

Environment Variables

MCP_LOG_FILE="/tmp/mcp-debug.log"  # Log location

MCP_DEBUG=1 # Enable debug logging MCP_RECORD_FILE="session.jsonl" # Auto-record sessions MCP_CONFIG_PATH="./config.yaml" # Default config

Development Workflow

# 1. Start with empty config

mcp-tui uvx mcp-debug --proxy --config empty-config.yaml

2. Add your server dynamically

server_add: {name: myserver, command: ./my-server-v1}

3. Test tools: myserver_read_file, myserver_process, etc.

4. Make changes and rebuild

go build -o my-server-v2

5. Hot-swap the server

server_disconnect: {name: myserver} server_reconnect: {name: myserver, command: ./my-server-v2}

6. Same tools work immediately with new implementation!

CLI Commands

uvx mcp-debug --help              # Show help

uvx mcp-debug --version # Show version uvx mcp-debug config init # Create default config uvx mcp-debug config show # Show current config uvx mcp-debug config validate # Validate config file uvx mcp-debug env list # List environment variables uvx mcp-debug env check # Check required env vars uvx mcp-debug tools list # List tools with details

Project Structure

mcp-debug/

├── main.go # CLI entry point ├── config/ # Configuration loading ├── client/ # MCP client implementation ├── integration/ # Proxy server and wrapper ├── discovery/ # Tool discovery ├── proxy/ # Request forwarding ├── playback/ # Recording and playback └── test-servers/ # Example MCP servers

Building

# Development build

go build -o mcp-debug .

Production build with version info

go build -ldflags "-X main.BuildTime=$(date -u +%Y-%m-%dT%H:%M:%SZ) -X main.GitCommit=$(git rev-parse HEAD)" -o mcp-debug .

Run tests

go test ./...

Contributing

See CONTRIBUTING.md for guidelines.

License

MIT License - see LICENSE for details.

MCP Debug

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

yontu

README from the maker

MCP Debug

Features

Hot-Swap Development

Session Recording & Playback

Development Proxy

Installation

Using npx (Node.js)

Or install globally

Or build from source

Quick Start

Or with mcp-tui for interactive testing

Usage

Proxy Mode

With recording

With custom log file

Playback Modes

Replay recorded responses to test a client

Configuration

Environment Variables

Development Workflow

2. Add your server dynamically

3. Test tools: myserver_read_file, myserver_process, etc.

4. Make changes and rebuild

5. Hot-swap the server

6. Same tools work immediately with new implementation!

CLI Commands

Project Structure

Building

Production build with version info

Run tests

Contributing

License