fix: improve DuckDuckGo MCP gateway reliability and clarify platform … #91
Conversation
…usage - Added mcp-config.yaml with explicit DDG_USER_AGENT to help bypass DuckDuckGo bot detection. - Updated compose.yaml to mount the new MCP config and explicitly set platform: linux/amd64 for all services. - Specifying the platform ensures consistent builds across different host architectures (e.g., Apple Silicon). - These changes make web search more reliable for all users and reduce bot detection issues.
|
Rretiro duck |
| services: | ||
| adk: | ||
| platform: linux/amd64 |
There was a problem hiding this comment.
question: why does this need to hardcode the platform? What problem is solved by adding it?
There was a problem hiding this comment.
It's possible its simply just my local environment that's broken.
When I remove 'platform' the build hangs.
docker compose up ─╯
[+] Running 2/2
✔ Container adk-adk-1 Recreate... 2.5s
! adk The requested image's platform (linux/arm64) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested 0.0s
Attaching to adk-1, mcp-gateway-1
mcp-gateway-1 | - Reading configuration...
mcp-gateway-1 | - Reading catalog from https://desktop.docker.com/mcp/catalog/v2/catalog.yaml
mcp-gateway-1 | - Configuration read in 55.178129ms
mcp-gateway-1 | - No server is enabled
mcp-gateway-1 | - Listing MCP tools...
mcp-gateway-1 | > 0 tools listed in 11.371µs
mcp-gateway-1 | > Initialized in 56.841104ms
mcp-gateway-1 | > Start sse server on port 8811
adk-1 | exec /entrypoint.sh: exec format error
adk-1 exited with code 255
| use_api_socket: true | ||
| volumes: | ||
| # allow gateway to spin up MCP servers via Docker | ||
| - /var/run/docker.sock:/var/run/docker.sock:ro |
There was a problem hiding this comment.
issue: I think this can be safely removed, use_api_socket takes care of mounting the socket.
There was a problem hiding this comment.
valid point. This is a copilot hallucination
There was a problem hiding this comment.
Makes sense, that was recently added to compose :-)
| @@ -1,33 +1,40 @@ | |||
| version: "3.8" | |||
There was a problem hiding this comment.
issue: version is obsolete and should not be used anymore
There was a problem hiding this comment.
valid point. This is a copilot hallucination
| - --cpus=1 | ||
| - --memory=2Gb | ||
| - -e | ||
| - DDG_USER_AGENT="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36" |
There was a problem hiding this comment.
question: I'm not sure if we should get into agent spoofing, but in any case could you please clarify how this environment variable gets used? I cannot find any references to it in https://github.com/nickclyde/duckduckgo-mcp-server - Thanks!
There was a problem hiding this comment.
The DDG_USER_AGENT is another hallucination. I just tested without it and it works. When I tried to run with mcp-gateway as written it wasn't working for me so this was a best effort to get it to work. :)
mcp-gateway:
# mcp-gateway secures your MCP servers
image: docker/mcp-gateway:latest
use_api_socket: true
command:
- --transport=sse
# add any MCP servers you want to use
- --servers=duckduckgo
fix: improve DuckDuckGo MCP gateway reliability and clarify platform usage