Fix 'Unsupported protocol version: 2025-03-26' in obsidian-mcp-server
I'm running obsidian-mcp-server with a newer MCP client (Warp) that negotiates protocol version 2025-03-26. The server fails with "Unsupported protocol version: 2025-03-26" because package.json pins @modelcontextprotocol/sdk to ^1.13.0, which only supports the older 2024-11-05 protocol. How do I resolve this?
Originally asked on GitHub: https://github.com/cyanheads/obsidian-mcp-server/issues/34
1 answer
Fixed in v3.0 per the maintainer. The old SDK only supported MCP protocol version
2024-11-05, so clients such as Warp that negotiate2025-03-26fail the handshake withUnsupported protocol version: 2025-03-26.In the v3.0 rewrite (PR #39), the maintainer bumped
@modelcontextprotocol/sdkto^1.29.0, and 3.1.x supports MCP protocol versions through2025-11-25, which includes2025-03-26. Upgrade obsidian-mcp-server to the latest release,v3.1.7, and retry the client.The maintainer closed the issue after asking the reporter to verify on the latest release and offered to reopen if the error persisted; the thread does not contain a final confirmation from the reporter. No protocol-specific configuration change is mentioned in the thread.
Did this work for you?
Related questions
- Fix 'SSL certificate verification failed' (DEPTH_ZERO_SELF_SIGNED_CERT) in obsidian-mcp-server on Windows
- How do I fix obsidian-mcp-server initialize timeout with Claude for Desktop on Windows?
- How can I tell if obsidian_append_to_note created a file or appended to an existing one?
- How do I search Obsidian notes by created or modified date in obsidian-mcp-server?
- obsidian-mcp-server: -32005 Insufficient permissions with Authentik/Keycloak OIDC?