mem0-oss-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mem0-oss-mcpAdd a memory that I like dark mode."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mem0-oss-mcp
Small MCP bridge for the self-hosted Mem0 OSS server from mem0ai/mem0/server.
It exposes the Mem0 MCP tool names expected by Codex and forwards them to a self-hosted Mem0 REST API.
Configuration
MEM0_OSS_BASE_URL=http://192.168.1.20:18080
MEM0_OSS_API_KEY=m0sk_xxx
MEM0_OSS_MCP_HOST=0.0.0.0
MEM0_OSS_MCP_PORT=8080
MEM0_OSS_MCP_TOKEN=change-me
MEM0_OSS_DEFAULT_USER_ID=codex
MEM0_OSS_DEFAULT_APP_ID=defaultMEM0_OSS_BASE_URL is the base URL of your Mem0 OSS REST server. The port is
not assumed.
Codex should connect to this bridge, not directly to Mem0 OSS:
[mcp_servers.mem0]
url = "http://<bridge-host>:8080/mcp"
bearer_token_env_var = "MEM0_OSS_MCP_TOKEN"Related MCP server: Mem0 MCP Server
Run
PYTHONPATH=src python3 -m mem0_oss_mcp.serverDocker:
docker build -t mem0-oss-mcp .
docker run --rm -p 8080:8080 --env-file .env mem0-oss-mcpTools
add_memorysearch_memoriesget_memoriesget_memoryupdate_memorydelete_memorydelete_all_memoriesdelete_entitieslist_entitieslist_eventsget_event_status
list_events and get_event_status are implemented locally because the OSS
REST server writes synchronously and does not expose the platform event API.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SteinX/mem0-oss-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server