Bug: MCP Server Installer UI Fails Silently — All MCP Types Affected
Bug Report: Windsurf MCP Server Installer UI Fails Silently
Summary
The Windsurf MCP server installer UI completely fails to install any MCP servers. No error message is shown to the user—the installation simply does nothing. This affects all MCP types (Filesystem, GitHub, Memory, etc.).
Environment
- Product: Windsurf / Claude Code
- Platform: Windows 11
- Date: 2026-05-22
Steps to Reproduce
- Open Windsurf
- Open Claude Code extension settings or MCP manager
- Click "Add MCP Server" or similar UI button
- Select a standard MCP (e.g., Filesystem, GitHub)
- Follow the UI prompts to configure and install
- Click "Install" or "Add"
Expected Behavior
- MCP server configuration is written to
.mcp.json - MCP is added to
enabledMcpjsonServersinsettings.json - Success confirmation message is displayed
- MCP becomes available for use in Claude Code
Actual Behavior
- No visible error message
- No success confirmation
.mcp.jsonandsettings.jsonremain unchanged- MCP is not installed or available
- User has no indication of what went wrong
Root Cause
The Claude VSCode extension does not implement MCP server installation.
Investigation shows:
- The webview UI sends an
update_session_statemessage with title="Install and configure Filesystem MCP tool" - The Claude extension receives this message but has no handler to process it
- The message is silently lost—no
.mcp.jsonwrite occurs - No error is logged or reported back to the UI
- Errors are caught and suppressed without user-facing feedback
Evidence
- Extension logs show webview message sent but no corresponding installation response
.mcp.jsonremains unchanged after installation attempts- Manual
.mcp.jsonfile-based configuration works perfectly, proving the MCP infrastructure is functional - The issue is isolated to the UI installer pathway
Impact
- Severity: High
- Scope: All MCPs (GitHub, Filesystem, Memory, custom servers, etc.)
- User impact: Users cannot install MCPs through the advertised UI feature; must manually configure
.mcp.jsonfiles - Workaround: Manual
.mcp.jsonconfiguration andenabledMcpjsonServersarray updates work, but this defeats the purpose of a graphical installer
Workaround
Users can work around this by manually editing configuration files:
- Create/edit
.mcp.jsonwith MCP server definitions - Add server names to
enabledMcpjsonServersarray insettings.json - Restart the application
However, this is not a scalable solution for users trying to manage hundreds of agents.
Product Context
Windsurf/Claude Code is being marketed as a tool for managing hundreds of AI agents on a single system. A broken MCP installer UI undermines this value proposition and signals incomplete product readiness.
Recommendation
- Immediate: Add error logging and user-facing error messages to the MCP installation pathway
- Short-term: Implement the missing MCP installation handler in the extension
- Long-term: Add integration tests for MCP installation via UI to prevent regression
---
Reporter Notes:
This bug was discovered during a GitHub token integration setup for MCPs. Manual configuration proved the MCP infrastructure itself is sound—the issue is purely in the UI installer feature implementation.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗