claude-code - 💡(How to fix) Fix Claude Code doesn't know how to register MCP servers into itself [1 comments, 2 participants]

Claude confidently made the change and reported success. The server never connected. There is zero feedback that the settings.json approach is wrong — no warning, no error, nothing. It just doesn't work. 2. Warn or error if mcpServers appears in settings.json, since that key is silently ignored and creates a false sense of success

TL;DR

To fix the issue, Claude should use the claude mcp add command to register MCP servers instead of modifying the settings.json file.

Guidance

• When configuring MCP servers, use the claude mcp add command with the required parameters, such as <name>, -s user, and the server command with arguments.
• Verify the MCP server connection using the claude mcp list command.
• Avoid modifying the settings.json file to add MCP servers, as this approach is silently ignored.
• Consider implementing a warning or error message when mcpServers appears in settings.json to prevent false success scenarios.

Example

claude mcp add my-server -s user -- obsidian-mcp-server --port 8080
claude mcp list

Notes

The current implementation of Claude Code ignores the mcpServers block in settings.json, leading to confusion and silent failures. The suggested fix focuses on using the claude mcp add command and providing feedback when the incorrect configuration method is used.

Recommendation

Apply the workaround by using the claude mcp add command to register MCP servers, as this is the supported and documented method for configuring Claude Code.