MCP Obsidian Configuration Issue: Invalid Server Connection and JSON Configuration Fix

[mkprevo]

written by claude sonnet.

Describe the bug
The default configuration for MCP Obsidian fails to establish a proper connection with the markdown server, resulting in "Tool 'markdown' not found" errors. This occurs despite the server showing as "running" in the interface. The issue appears to stem from incomplete server configuration settings in the default JSON configuration file.

To Reproduce
Steps to reproduce the behavior:

1. Install mcp-obsidian via npm
2. Use the default configuration
3. Attempt to connect to the markdown server
4. Observe error message: "Tool 'markdown' not found"
5. Check server status showing as "running" despite connection failure

Expected behavior
The markdown server should properly connect and allow access to Obsidian notes when using the MCP protocol. Users should be able to search and retrieve notes from their specified Obsidian vault directory.

Solution Implementation
The following modified JSON configuration resolves the connection issues:

{
    "mcpServers": {
        "markdown": {
            "command": "npx",
            "args": [
                "mcp-obsidian",
                "/PATH/TO/OBSIDIAN/VAULT"
            ],
            "settings": {
                "connection": {
                    "type": "local",
                    "timeout": 30000
                },
                "search": {
                    "enabled": true,
                    "caseSensitive": false
                }
            }
        }
    }
}

Additional context

• Operating System: macOS
• Node.js Version: v22.13.0
• The solution has been verified to work with both local and iCloud-based Obsidian vaults
• The fix maintains all core functionality while resolving the connection issues

This configuration enhancement improves the reliability of the MCP Obsidian integration and ensures proper server connectivity for users implementing the tool.

[olaservo]

Hi @mkprevo , the Obsidian integration isn't maintained here - if you're still having this issue please open an issue in the repo for the integration. Thanks!