ZAP MCP Server not reachable

Questions
1

I wish to connect a n8n MCP Client to the Zap MCP Server ( ZAP – The ZAP MCP Server )

It does not work either as localhost ZAP or distant via http.

How to trace the detailed http requests sent by the n8n MCP Client ?

Information on your n8n setup

  • n8n version: self hosted, latest
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): via WSL docker
  • Operating system: Linux
4

One thing I would check first is the ZAP side. From what I saw, the ZAP MCP server defaults to port “8282”, and it won’t accept plain HTTP unless you turn off “Secure Only.”

Also, if you have the security key enabled, n8n needs to pass that in the “Authorization” header. Since the n8n MCP Client supports Bearer/generic header auth, I’d probably test it with a generic header first and see if that clears it up.

5

@qualitesys to trace the actual requests, set N8N_LOG_LEVEL=debug on your container and watch the logs while you fire the MCP Client — you’ll see the exact URL, headers and body it sends, which makes the ZAP-side mismatch (port 8282, Secure Only, missing Authorization header that @Exnav29 mentioned) obvious in seconds.

6

Thanks for your answers

I managed to start Zap as a docker image in the same network as n8n (–network host), adding the mcp extension, it works fine.