Archon icon indicating copy to clipboard operation
Archon copied to clipboard

🐛 [Bug]: unable to connect to MCP server

Open syberkitten opened this issue 4 months ago • 2 comments

Archon Version

0.1.0

Bug Severity

🔴 Critical - App unusable

Bug Description

Hi Install archoon connected to supabase, added api keys. I'm running the GUI, MCP server seems to be running. But I'm not able to connect to it with any of thse:

  • cline
  • kilo code
  • claude code

ps: I have other MCP's altready, this is not a configuration issue.

The best way to debug MCP is to use the inspector from anthropic: npx @modelcontextprotocol/inspector

https://modelcontextprotocol.io/legacy/tools/inspector this should be the source of truth for debugging MCPs.

For some reason I'm not able to connect to it, also there are no immediate logs, errors come from the archon-server after a few seconds.

seems like MCP server does not emit any logs.

Steps to Reproduce

Basic setup and lunch, no customizations just try to connect to the MCP server.

docker compose --profile full up

Expected Behavior

Should be able to connect to MCP server MCP server should show logs.

use this tool to connect to MCP (this is by Anthropic which set the standard) npx @modelcontextprotocol/inspector

Actual Behavior

no mcp, and no mcp logs, in GUI mcp server shown as running. there are no logs and mcp server is not reachable (curl)

Error Details (if any)

[INFO] INFO: 172.64.149.246:30657 - "GET /mcp HTTP/1.1" 400 Bad Request

Affected Component

🔍 Knowledge Base / RAG

Browser & OS

139.0.7258.139

Additional Context

No response

Service Status (check all that are working)

  • [x] 🖥️ Frontend UI (http://localhost:3737)
  • [x] ⚙️ Main Server (http://localhost:8181)
  • [x] 🔗 MCP Service (localhost:8051)
  • [x] 🤖 Agents Service (http://localhost:8052)
  • [x] 💾 Supabase Database (connected)

syberkitten avatar Aug 24 '25 21:08 syberkitten

hey @syberkitten Any additional info here would be great, what json config are you using, have you pulled the latests main branch?. Have you followed all the steps in the README correctly etc?

Im running Archon right now with no issues.

Wirasm avatar Aug 25 '25 06:08 Wirasm

I am using Roocode, and the mcp json looks like this: "archon": { "command": "npx", "args": [ "mcp-remote", "http://localhost:8051/mcp" ], "alwaysAllow": [ "perform_rag_query" ] } I am using the Cline option basically. When i ask it to run the archon mcp server, I get that kind of error:

Error executing MCP tool: MCP error -32000: Connection closed

Any ideas?

GioPetro avatar Aug 29 '25 16:08 GioPetro

Same, I followed the set up instructions. I've tried changing the port in case 8051 was taken or something. But every time I try to connect, it give the same error described above. It doesn't have any logs that seem to indicate failure. If I go to http://localhost:8051/ in a browser then it logs 404 not found in my docker container logs for the mcp server, but I can't get it to work. Also, my configuration I assume to be correct, I copied it for my appropriate use case (roo code). I have other mcp servers that connect just fine. I'm on wsl, so i don't know if that would be a potential issue. But I'm able to access http://localhost:3737/ just fine and add documents. It's just the mcp server that doesn't seem to work at all.

weldonla avatar Sep 16 '25 19:09 weldonla

Ok, so I was able to fix it for myself. It had to do with whatever model context protocol stuff I had installed with npm. But essentially, the commands that I think ended up fixing it was. npm cache clean --force and npm i mcp-remote -g

If that alone doesn't fix it, you can dig through the chatgpt convo I had to debug and fix it: https://chatgpt.com/share/68c9e6e2-957c-8003-9d12-06c605f0df82

you should note that i didn't seem to need to change my mpc config for it to actually work though. i have

"archon": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:8051/mcp",
        "--allow-http"
      ],
      "disabled": false,
      "alwaysAllow": []
    }

weldonla avatar Sep 16 '25 22:09 weldonla

Also, for wsl, removing or renaming the .vscode-remote folder fixed issues too

weldonla avatar Sep 17 '25 15:09 weldonla