How to fix 'MCP error -32000: Connection closed' when configuring mcp-searxng with npx?

6 answers

• Best answerAgentArmor teamTeam3d ago

  Status: fixed. The maintainer closed this issue as COMPLETED after reworking the project: you no longer need to clone the mcp-searxng repository. Use the mcp-searxng NPM package and check the project README for the current invocation (the thread doesn't show the exact new config string).

  The config example from the issue body was:

  jsonCopy to clipboard

  {
    "mcpServers": {
      "searxng": {
        "command": "npx",
        "args": ["-y", "<full path to mcp-searxng repo>/"],
        "env": { "SEARXNG_URL": "YOUR_SEARXNG_INSTANCE_URL" }
      }
    }
  }
  

  The reporter asked what <full path to mcp-searxng repo>/ should be when SearXNG runs on a remote server. The maintainer first said to clone the repo on the Mac, use its full path, and set SEARXNG_URL to the remote instance. Follow-up comments reported the same McpError: MCP error -32000: Connection closed in Claude Code (started with uv run claude --mcp-debug) and in another MCP client. The maintainer explained the error means the server did not respond, and asked which client and SearXNG instance were being used, and whether public instances from https://searx.space (opens external site) ↗ behaved differently.

  Resolution: use the published NPM package instead of a local repo path; the maintainer validated it locally before closing. General advice if the error persists: confirm your client can reach the SearXNG URL, and test the same setup against a public instance to narrow down whether your own instance is the problem.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @ihor-sokoliuk tried on GitHub (Worked)

  The maintainer changed the setup to use the mcp-searxng NPM package instead of a local clone, tested and validated it locally, then closed the issue as COMPLETED.

  Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/6#issuecomment-2800450008 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @Abbie7737 tried on GitHub (Didn't work)

  A Mac user ran Claude Code with uv run claude --mcp-debug; the searxng MCP server was found but the connection failed with MCP error -32000: Connection closed.

  Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/6#issuecomment-2763911166 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @Twilight-9 tried on GitHub (Didn't work)

  A user reported still being unable to use it, with McpError: MCP error -32000: Connection closed in an MCP client other than Claude Desktop. They shared the error but no config details.

  Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/6#issuecomment-2746063576 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @ihor-sokoliuk tried on GitHub (Outcome unclear)

  The maintainer asked which MCP client and SearXNG server were used, whether public instances from https://searx.space (opens external site) ↗ were tried, and explained that Connection closed means the server did not respond.

  Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/6#issuecomment-2772802270 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What a GitHub user tried on GitHub (Outcome unclear)

  The reporter posted the config example and asked what <full path to mcp-searxng repo>/ should be on a Mac with a remote SearXNG instance.

  Source: https://github.com/ihor-sokoliuk/mcp-searxng/issues/6 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport