OMEM MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

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.

этот файл ставится пользователю, но в репозитории его нет

self.__BUILD_MANIFEST={__rewrites:{afterFiles:[],beforeFiles:[],fallback:[]},"/_error":["static/chunks/pages/_error-7ce03bcf1df914ce.js"],sortedPages:["/_app","/_error"]},self.__BUILD_MANIFEST_CB&&self.__BUILD_MANIFEST_CB();

            target = os.path.join(dest, os.path.relpath(root, source))

    return subprocess.Popen([sys.executable, "-m", "omem.mcp_server"],

…e[o]}}),Qe("at");var Ze=function(t,e){return b(i[t].prototype[e])},tr=(Ze("Array","at"),TypeError),er=function(t,e){if(!delete t[e])throw new tr("Cannot delete property "+Y(e)+" of "+Y(t))},rr=Math.min,nr=[].copyWithin||function(t,e){var r=it(this),n=de(r),o=he(t,n),i=he(e,n),a=a…

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

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 omem -- uvx omem-infrastructure

{
  "mcpServers": {
    "omem": {
      "args": [
        "omem-infrastructure"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.omem]
command = "uvx"
args = ["omem-infrastructure"]

{
  "mcpServers": {
    "omem": {
      "args": [
        "omem-infrastructure"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "omem": {
      "args": [
        "omem-infrastructure"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: OMEM_API_KEY (API key from the OMEM server. It is printed on first run of `omem-server`.), OMEM_PROJECT (Project id to read and write memory in, also printed on first run.), OMEM_BASE_URL (URL of the OMEM server.), OMEM_AGENT (The agent whose memory this process reads and writes. Fixed here rather than passed as a tool argument, so the model cannot act as a different agent.), OMEM_USER (The end user this process is acting for. Also fixed here, not a tool argument. Leave unset and no user-scoped memory is visible.). The author declared them in the registry entry; get the values from the project itself.