Silent Failure

Silent Failure is the MCP ecosystem's nastiest habit. You follow the exact config steps from the article, drop the JSON into claude_desktop_config.json, restart Claude Desktop, and nothing lights up in the tool panel. No red badge, no toast, no log entry that actually reaches you. The Figma MCP server never connects so Claude cannot read your live component tokens or layer structure. Instead it guesses from your last screenshot like it is still 2024. The same thing happens with Filesystem MCP when the directory path is wrong or GitHub MCP when the personal access token lacks repo scope. The host spawns the Node process, the process dies instantly, and the host simply moves on like the server never existed in the config. This breaks the entire promise of MCP. The AI stops acting inside your actual tools and goes back to being a clever description machine that wastes your time.

Silent Failure is not a crash with a stack trace. It is not the AI hallucinating a component name or giving you bad design advice. Those problems announce themselves. Silent Failure is the specific category of plumbing errors where the connection between MCP host and MCP server never forms yet the host UI acts completely normal. It is not user error on the prompt side or a limitation of the underlying model. Those have different symptoms and different fixes. It is not the loud failure where Cursor shows a red MCP status indicator or Claude prints an error message in the chat window. Silent Failure is the ghost that leaves you questioning your own sanity for ninety minutes before you think to check the logs at ~/Library/Logs/Claude/.

Concrete example one happened last week with the Browser Automation MCP using Playwright. The designer added the server to their config, used the exact npx command from the article, and restarted Cursor. The status indicator turned green. They asked Claude to open their live pricing page, screenshot the hero at 1440px, and compare spacing tokens against the Markdown spec in their local assets folder. Claude returned a confident but completely invented analysis based on 2023 design trends. No error surfaced. Two hours of wasted prompting later they discovered the Playwright server could not launch its Chromium binary because their Mac was missing a dependency installed via brew. The process died before it could register with the host. Cursor swallowed the failure and marked everything ready. Concrete example two hit with Figma MCP in a real client file in early 2025. One stray comma after the final property in the JSON object invalidated the entire mcpServers block. Claude Desktop loaded without complaint. The Figma tool never appeared in the panel. The designer spent forty minutes manually listing variant properties before running the config through a validator and spotting the syntax error. Concrete example three involved Notion MCP where the OpenAPI header token had the wrong permissions. Claude could see public pages but not the private design brief database. No error. The AI simply wrote rationale copy that ignored the actual stakeholder comments living in the real Notion workspace. Each case shares the same pattern: the server died quietly, the host stayed quiet, and the designer paid the tax in lost hours.

Apply the silent failure lens the moment an MCP server does not appear after a full quit and restart of Claude Desktop or Cursor. Run the debugging checklist the instant Claude starts describing your design system from memory instead of quoting the actual token values or layer names from the live Figma file. Use it before every handoff session that relies on GitHub MCP to comment on PRs or Linear MCP to update ticket status. Use it when Browser Automation MCP returns vague visual observations instead of pixel measurements pulled from the real DOM. Do not run the silent failure checklist when you see explicit red indicators in Cursor or error text in the Claude chat window. Those are loud failures pointing at expired tokens or network problems. Skip it entirely if you have not verified your Node version sits at 18 or higher or if you never fully quit the host application. Background processes lie. Never debug a production client file until the exact same config runs cleanly against a dummy Figma file and local test directory first.

Silent Failure is the tax designers pay for bleeding edge plumbing until the ecosystem grows up so check your JSON syntax and Node version before you blame the AI.