Open Agent Memory runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 12 Nov 2026.
Self-hosted OAM memory with cited recall over your existing deployment
We read the source, 4 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
result = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add oam -e 'OAM_BASE_URL=<OAM_BASE_URL>' -e 'OAM_USER_ID=<OAM_USER_ID>' -e 'OAM_USER_API_KEY=<OAM_USER_API_KEY>' -- npx -y @rocke-dong/oam-mcp
{
"mcpServers": {
"oam": {
"command": "npx",
"args": [
"-y",
"@rocke-dong/oam-mcp"
],
"env": {
"OAM_BASE_URL": "<OAM_BASE_URL>",
"OAM_USER_API_KEY": "<OAM_USER_API_KEY>",
"OAM_USER_ID": "<OAM_USER_ID>"
}
}
}
}
[mcp_servers.oam]
command = "npx"
args = ["-y", "@rocke-dong/oam-mcp"]
env = { OAM_BASE_URL = "<OAM_BASE_URL>", OAM_USER_ID = "<OAM_USER_ID>", OAM_USER_API_KEY = "<OAM_USER_API_KEY>" }
{
"mcpServers": {
"oam": {
"command": "npx",
"args": [
"-y",
"@rocke-dong/oam-mcp"
],
"env": {
"OAM_BASE_URL": "<OAM_BASE_URL>",
"OAM_USER_API_KEY": "<OAM_USER_API_KEY>",
"OAM_USER_ID": "<OAM_USER_ID>"
}
}
}
}
{
"servers": {
"oam": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@rocke-dong/oam-mcp"
],
"env": {
"OAM_BASE_URL": "<OAM_BASE_URL>",
"OAM_USER_API_KEY": "<OAM_USER_API_KEY>",
"OAM_USER_ID": "<OAM_USER_ID>"
}
}
}
}
Put your own values in place of
<OAM_BASE_URL> (URL of your existing OAM deployment, for example http://127.0.0.1:17333), <OAM_USER_ID> (Your authorized OAM user ID), <OAM_USER_API_KEY> (User-scoped API key for your OAM deployment).
The author’s registry entry marks them as required.
Deploy and manage websites and apps on Swiss hosting, with HTTPS, from your AI agent.
Your AI agent deploys, migrates & upgrades self-hosted Odoo ERP on a server you own.
Every tool your AI needs in one self-hosted install: memory, reasoning, git, Docker and more.
Web hosting your AI runs itself over MCP: deploy sites, Next.js, Postgres, domains. EU servers.
European cloud hosting. Deploy and manage apps with your favorite AI coding assistant.
Self-hosted NVIDIA NIM API-key manager with a Claude MCP connector; deploy your own instance.
Hosting for AI agents: your AI client deploys Docker apps to live HTTPS URLs over MCP.
Operate ohmyho.st hosting from your coding agent: deploy GitHub apps, Postgres, mail, domains.
Answers built from our own checks of this server.