mcpproxy-debug

Diagnoses MCPProxy server logs and suggests configuration fixes.

25|6|Updated Feb 24, 2010
One-click install
npx skills add https://github.com/technicalpickles/dotfiles --skill mcpproxy-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcpproxy-debug
Source: https://github.com/technicalpickles/dotfiles/tree/main/home/.claude/skills/mcpproxy-debug
Command: npx skills add https://github.com/technicalpickles/dotfiles --skill mcpproxy-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured, automated approach to debug, configure, and troubleshoot MCPProxy (Model Context Protocol Proxy) servers. It automates diagnostic steps, intelligently identifies common error patterns, and offers immediate solutions, significantly reducing the time and complexity of resolving proxy-related issues.

Core Features & Use Cases

  • Automated Status Checks: Quickly verifies MCPProxy server status, connectivity, and tool availability via API and process checks, giving you an instant overview of your proxy's health.
  • Intelligent Error Diagnosis: Analyzes server-specific logs for common error patterns like "unexpected argument" or "not a TTY", providing immediate root cause analysis and targeted fixes.
  • Configuration Remediation: Guides you through fixing common configuration mistakes for uvx, npx, and Docker-based servers, including critical Docker isolation settings, ensuring your servers connect reliably.
  • Use Case: An MCP server fails to connect. Use this skill to run diagnose_server.sh, which automatically checks logs, identifies a "TTY" error, and suggests adding "isolation": {"enabled": false} to the server config, resolving the issue in minutes instead of hours of manual log digging.

Quick Start

Use the mcpproxy-debug skill to diagnose the 'buildkite' MCP server.