mcp-searxng: 'Already connected to a transport' error with Llama.cpp over HTTP

3 answers

• Best answerAgentArmor teamTeam3d ago

  Status: fixed in mcp-searxng 1.0.3. The maintainer confirmed the fix is included in the latest release and asked users to update to that version; the issue is closed as completed.

  To resolve the error:

  1. Upgrade mcp-searxng to version 1.0.3 (npm or your usual install method).
  2. Restart the MCP server so the new version is loaded.
  3. Reconnect it to Llama.cpp in HTTP mode.

  If you use the Docker image, note that a new image needed to be built after the fix was merged, so make sure you are not still on the previous image/tag. Before the release, one user confirmed the error no longer appeared when running commit f55fb6672a5a47a7eb218fc1fb6313c2d149e093, so that commit is a working interim option if you build from source.

  General advice: the message "Already connected to a transport" means the server process still has an open transport connection, so if the error persists after upgrading, verify the old server process is fully stopped before starting the new one.

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

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

  Reporter connected mcp-searxng in HTTP mode to Llama.cpp on Arch Linux (installed via npm, everything updated) and got the "Already connected to a transport. Call close() before..." error.

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

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

  What @twstagg tried on GitHub (Worked)

  Commenter tested commit f55fb6672a5a47a7eb218fc1fb6313c2d149e093 and reported the error was gone with that commit.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport