Wrap

A transparent MCP (Model Context Protocol) proxy server that sits between MCP clients and MCP servers (wrappees), logging all requests/responses while operating as a transparent proxy.

Overview

Wrap-MCP wraps existing MCP servers and provides the following features:

• 🔄 Transparent proxy: Appears as a regular MCP server to clients
• 📝 Request/response logging with type-safe storage
• 🔍 Log search and display tools (show_log)
• ⚠️ Captures and logs stderr output from the wrappee process
• 🔁 Auto-restart on binary file changes (development mode)
• 🎨 ANSI escape sequence handling for clean logs

Note: Wrap-MCP currently only supports wrapping MCP servers that use stdio transport. The wrapped server (wrappee) must communicate via stdin/stdout.

System Architecture

MCP Client ◄────────► Wrap-MCP ◄────────► Wrappee (MCP Server)
   (stdio/http)           │                    (stdio only)
                      Log Storage
                   (In-Memory VecDeque)

Installation

cargo build --release

Usage

Command Line

wrap-mcp [wrap-mcp options] -- <wrappee_command> [wrappee arguments]

Options

• --ansi: Preserve ANSI escape sequences in stderr logs

  • By default, Wrap-MCP removes ANSI escape sequences using a hybrid approach:
    • Sets NO_COLOR=1, CLICOLOR=0, and RUST_LOG_STYLE=never environment variables for the wrappee
    • Additionally removes any remaining ANSI escape sequences from stderr output
  • Use this option to preserve the original formatting

• -w: Watch the wrapped binary file for changes and automatically restart

  • Requires absolute path to the wrappee binary
  • Monitors the wrappee binary file for modifications
  • Automatically restarts the wrapped server when the binary is updated
  • Uses a 2-second debounce to handle multiple rapid file changes during compilation
  • Shows old and new PIDs in logs for verification
  • Sends notifications/tools/list_changed to MCP clients after restart
  • Useful for development when frequently recompiling the wrapped server

Environment Variables

• WRAP_MCP_TRANSPORT: Transport method for client connection (stdio or http, default: stdio)
  • This controls how MCP clients connect to Wrap-MCP
  • The wrapped server always uses stdio regardless of this setting
• WRAP_MCP_LOGSIZE: Maximum number of log entries to retain (default: 1000)
• WRAP_MCP_PROTOCOL_VERSION: Protocol version to use when initializing the wrapped server (default: 2025.03.26)
  • This allows compatibility with wrapped servers that require specific protocol versions
  • Example: WRAP_MCP_PROTOCOL_VERSION="2025.06.18"
• WRAP_MCP_TOOL_TIMEOUT: Timeout for tool calls in seconds (default: 30)
  • Controls how long to wait for a tool response before timing out
  • Example: WRAP_MCP_TOOL_TIMEOUT=60 (1 minute timeout)
• WRAP_MCP_LOG_COLORS: Enable ANSI color codes in log output (default: false)
  • Set to true or 1 to enable colors in terminal output
  • Default is disabled for compatibility with MCP Inspector and other tools
• RUST_LOG: Log level configuration (e.g., info, debug, trace)

Examples

# Wrap and launch another MCP server (ANSI removed by default)
WRAP_MCP_LOGSIZE=500 \
WRAP_MCP_TOOL_TIMEOUT=60 \
RUST_LOG=info \
cargo run -- my-mcp-server --option1 value1

# Launch with HTTP transport
WRAP_MCP_TRANSPORT=http cargo run -- my-mcp-server

# Launch while preserving ANSI escape sequences
cargo run -- --ansi -- my-mcp-server --option1 value1

# After building, run directly (ANSI removed by default)
./target/release/wrap-mcp -- my-mcp-server --port 8080 --config config.json

# Preserve ANSI escape sequences
./target/release/wrap-mcp --ansi -- my-mcp-server --port 8080

# Watch binary file for changes and auto-restart (requires absolute path)
./target/release/wrap-mcp -w -- /path/to/my-mcp-server --port 8080

# Combine options: watch + preserve ANSI (requires absolute path)
./target/release/wrap-mcp -w --ansi -- /path/to/my-mcp-server

# Use a specific protocol version for the wrapped server
WRAP_MCP_PROTOCOL_VERSION="2024.12.01" ./target/release/wrap-mcp -- my-mcp-server

Available Tools

Tools Inherited from Wrappee

All tools provided by the wrappee server are automatically available.

Wrap-MCP Specific Tools

show_log

Displays recorded logs.

Parameters:

• limit: Maximum number of entries to display (default: 20)
• tool_name: Filter by tool name
• entry_type: Filter by entry type (request, response, error, stderr)
• keyword: Regular expression pattern to search in log content (supports regex or literal string)
• format: Output format (default: ai)
  • ai: Concise format optimized for AI consumption
  • text: Detailed human-readable format with timestamps and formatting
  • json: Raw JSON output with full structure

clear_log

Clears all recorded logs.

restart_wrapped_server

Restarts the wrapped MCP server while preserving all recorded logs.

This is useful when:

• The wrapped server becomes unresponsive
• You want to reload the wrapped server after updating its code
• You need to reset the wrapped server's state

Features:

• Sends notifications/tools/list_changed to notify MCP clients of tool updates
• Preserves all existing logs during restart
• Automatically rediscovers tools from the restarted server

Note: During restart, client requests will fail temporarily.

Development

Build

cargo build

Test

# Run all tests
cargo test

Format

cargo fmt

Lint

cargo clippy

Known Limitations

Claude Code Reconnect Issue

When using Wrap-MCP with Claude Code, the reconnect functionality may fail on the first attempt. This occurs because Claude Code doesn't wait for the previous process to fully terminate before starting a new one.

• stdio transport: Process doesn't release file handles immediately
• HTTP transport: Port remains in TIME_WAIT state after process termination

Workaround: Execute the reconnect command twice. The second attempt usually succeeds.

This is a limitation of Claude Code's reconnect implementation and cannot be fully resolved from the Wrap-MCP side.

License

MIT