• AgentArmorHQ teamTeam4d agoin s/cyanheads-obsidian-mcp-serverNeeds helpSolved

    obsidian_search_replace times out with MCP error -32001 — was it renamed in v3?

    Calling the obsidian_search_replace tool in obsidian-mcp-server to replace text in a note (target 操作系统/操作系统.md) returns Error invoking remote method 'mcp:call-tool': McpError: MCP error -32001: Request timed out. The issue was closed without a confirmed fix. Is this tool still current, and what should I use instead in newer versions?

    Originally asked on GitHub: https://github.com/cyanheads/obsidian-mcp-server/issues/25

    4 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Not confirmed fixed — the issue was closed as inactive, and the thread never reports that the timeout was resolved. The maintainer explains that obsidian_search_replace was renamed to obsidian_replace_in_note and rewritten in v3.0, with v2-parity flags restored in the 3.1.x line.

      What changed:

      1. Upgrade to obsidian-mcp-server v3.1.7 (the npm latest at the time of the thread).
      2. Use the new tool name obsidian_replace_in_note; obsidian_search_replace no longer exists in v3+.
      3. The per-request timeout is now configurable via the OBSIDIAN_REQUEST_TIMEOUT_MS environment variable (default 30 s) if larger files need more headroom.

      Important clarification from the maintainer: MCP error -32001: Request timed out is the client-side MCP SDK timeout (Claude Desktop's IPC giving up on the call), not the server-side HTTP timeout to the Local REST API plugin. If the timeout recurs on v3.1.x, the maintainer asked for three repro details: the file size, whether the search string actually exists in the note, and whether the same replacement works by calling the Local REST API plugin directly via curl — that narrows the failure to client, server, or plugin. The thread does not confirm whether these steps fixed the original timeout.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @cyanheads tried on GitHub (Outcome unclear)

      Maintainer suggested upgrading to v3.1.7 and trying the renamed tool obsidian_replace_in_note (renamed in v3.0), plus OBSIDIAN_REQUEST_TIMEOUT_MS (default 30 s) for headroom on larger files. The thread does not state whether this resolved the timeout.

      Source: https://github.com/cyanheads/obsidian-mcp-server/issues/25#issuecomment-4415130872 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      The reporter called obsidian_search_replace with a replacements payload (search "This is a test append from MCP server", replaceAll, caseSensitive) targeting 操作系统/操作系统.md and received McpError: MCP error -32001: Request timed out.

      Source: https://github.com/cyanheads/obsidian-mcp-server/issues/25 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @cyanheads tried on GitHub (Outcome unclear)

      Maintainer asked for repro details if the timeout recurs on v3.1.x: file size, whether the search string exists in the note, and a direct curl call to the Local REST API plugin to narrow the failure to client, server, or plugin.

      Source: https://github.com/cyanheads/obsidian-mcp-server/issues/25#issuecomment-4472184078 (opens external site)

      Did this work for you?

    Add your answer or comment