debug-cowork-mcp-issues

Diagnose Cos MCP server failures in Claude Cowork Desktop and Claude Code.

4|1|Updated Jun 10, 2026

Search Tags:#troubleshooting #MCP server #server diagnostics #Cos #Claude Cowork

Ready to run

npx skills add https://github.com/philipyaz/cos --skill debug-cowork-mcp-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug-cowork-mcp-issues
Source: https://github.com/philipyaz/cos/tree/main/.claude/skills/debug-cowork-mcp-issues
Command: npx skills add https://github.com/philipyaz/cos --skill debug-cowork-mcp-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the diagnosis and repair of Cos MCP server issues in Claude Cowork Desktop and Claude Code, ensuring uninterrupted operations for server-related functionalities.

Core Features & Use Cases

Diagnose Server Issues: Detect and identify issues with Cos MCP servers that are failing in Claude Cowork Desktop or Claude Code, including board unresponsiveness, missing tools, tool call errors, and authentication errors.
Escalation Ladder: Offers a structured approach to problem-solving, including relaunching the service, inspecting logs, reproducing issues outside the application, applying known fixes, and regenerating configurations.
Technical Support: Supports the two distinct MCP server wiring paths of Claude Cowork Desktop and Claude Code, aiding in identifying which layer the user is encountering issues with.

Quick Start

Run the debug-cowork-mcp-issues skill to start diagnosing Cos MCP server issues in Claude Cowork Desktop.

Frequently Asked Questions about debug-cowork-mcp-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix MCP server issues when the board is not responding in Claude Cowork Desktop?▼

To fix MCP server issues when the board is not responding in Claude Cowork Desktop, diagnose Cos MCP server failures by relaunching the service, inspecting logs, and reproducing the issue outside the application to identify the failing layer.

Why does my MCP server show a 401 error or go missing from the tool list in Claude Code?▼

MCP server 401 errors and missing tools in Claude Code occur due to authentication failures or configuration issues. Resolve these by applying known fixes, inspecting launchd supergateway bridges, and regenerating configurations from the claude_desktop_config.json file.

What is the best way to troubleshoot tool call errors in a Cos MCP server?▼

The best way to troubleshoot Cos MCP server tool call errors is following an escalation ladder: relaunch the service, inspect server logs, reproduce the issue externally, apply known fixes, and regenerate configurations to restore functionality.

Do I need Bash and Read tools to diagnose Claude Cowork MCP server failures?▼

Yes, you need Bash and Read tools to diagnose Claude Cowork MCP server failures. These dependencies are required for inspecting direct stdio from claude_desktop_config.json and launchd supergateway bridges to identify server issues.

How does Claude Cowork Desktop handle direct stdio and launchd supergateway bridges for MCP servers?▼

Claude Cowork Desktop and Claude Code route MCP server wiring through two distinct paths: direct stdio from claude_desktop_config.json and launchd supergateway bridges. Diagnosing issues requires identifying which layer the failure occurs in.