mem0ai
Enable debug for Openmemory mcp server
🐛 Describe the bug
How to enable Debug for openmemory mcp server in docker-compose.yaml? services: openmemory-mcp: image: mem0/openmemory-mcp:latest build: api/ environment: - OPENAI_BASE_URL=https://api.siliconflow.cn/v1 - OPENAI_API_KEY=sk-... - USER=worker - MILVUS_HOST=x.x.x.x - MILVUS_PORT=19530 - MILVUS_DB_NAME=default ports: - "8765:8765" volumes: - ./api/:/usr/src/openmemory openmemory-ui: image: mem0/openmemory-ui:latest build: ui/ ports: - "3000:3000" environment: - NEXT_PUBLIC_API_URL=http://openmemory-mcp:8765 - NEXT_PUBLIC_USER_ID=worker
Hey @HelloJelly2021 in the command: > of the docker-compose file you can add in uvicorn main:app --host 0.0.0.0 --port 8765 --log-level debug --reload this to enable logging, this will help you in debugging.
Thanks for your feedbacks. I updated the docker-compose.yml as you saied, but it didn't work.
services: openmemory-mcp: image: mem0/openmemory-mcp:latest build: api/ environment: - OPENAI_BASE_URL=https://api.siliconflow.cn/v1 - OPENAI_API_KEY=sk-... - USER=worker - MILVUS_HOST=10.x.x.x - MILVUS_PORT=19530 - MILVUS_DB_NAME=default ports: - "8765:8765" volumes: - ./api/:/usr/src/openmemory command: sh -c "uvicorn main:app --host 0.0.0.0 --port 8765 --log-level debug --reload"
Openmemory mc server logs as flow:
openmemory-mcp-1 | INFO: Started server process [9] openmemory-mcp-1 | INFO: Waiting for application startup. openmemory-mcp-1 | INFO: Application startup complete. openmemory-mcp-1 | INFO: 10.x.x.x:52523 - "GET /mcp/openmemory/sse/worker HTTP/1.1" 200 OK openmemory-mcp-1 | INFO: 10.x.x.x:52524 - "POST /mcp/messages/?session_id=758c392177d94a19a926713ab09c1bf2 HTTP/1.1" 200 OK openmemory-mcp-1 | INFO: 10.x.x.x:52525 - "POST /mcp/messages/?session_id=758c392177d94a19a926713ab09c1bf2 HTTP/1.1" 200 OK openmemory-mcp-1 | INFO: 10.x.x.x:64829 - "POST /mcp/messages/?session_id=758c392177d94a19a926713ab09c1bf2 HTTP/1.1" 200 OK openmemory-mcp-1 | [10/17/25 02:18:41] INFO Processing request of type server.py:664 openmemory-mcp-1 | CallToolRequest
This is the best way you can get the logs when using openmemory, as there's no proper debugger support for the same. Sorry for the trouble.