{"id":77623,"plugin_id":"plugins_6ae8cbe5a6708191b99fec2318f2e009","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:25.009Z","digest":"84b2a618d8181ad2a55a03ed11265039345d986546cb748336d35ca10f97d7b9","against":null,"payload":{"description":"Diagnose and fix a broken MCP server, UI bridge, authentication, transport, tools/list, tools/call or resource-rendering issue from errors, logs or code.","included_files":[],"name":"debug-mcp-project","skill_md_contents":"---\nname: debug-mcp-project\ndescription: Diagnose and fix a broken MCP server, UI bridge, authentication, transport, tools/list, tools/call or resource-rendering issue from errors, logs or code.\n---\n# Diagnose MCP defects\n\n1. Establish symptoms and environment: protocol version, installed SDK, transport, host, recent changes, failing command. Inspect actual files/logs if available.\n2. Reproduce the failure before changing code; use Inspector/known client when possible. For remote transport, check endpoint reachability, auth and session lifecycle.\n3. Identify the failing boundary: startup/initialize, schema validation, tool discovery/call, resource registry/read, Apps resource link, iframe bridge or external provider.\n4. Fix the smallest cause while preserving stable tool names and input/output contracts. Look for SDK v1/v2 migration mismatch rather than guessing imports. Verify against current official docs.\n5. Add a regression test, rerun the failing case and baseline. When reproduction is blocked, give reasoned diagnosis with clear uncertainty, not a fabricated fix.\n6. Never print secrets or raw customer information from logs; don't deploy or push without approval.\n\nRead `../../references/troubleshooting.md`, `../../references/protocol-and-ui.md`, and `../../references/testing.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}