jevmem MCP Server

What the code does

We read the source, 5 d 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.

    const child = spawn(process.execPath, [cliPath, "daemon", "--serve"], {

const pluginsRoot = (env: NodeJS.ProcessEnv, home: string) => (env.CLAUDE_CODE_PLUGIN_CACHE_DIR ? path.resolve(env.CLAUDE_CODE_PLUGIN_CACHE_DIR) : path.join(configDir(env, home), "plugins"));

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 jevmem -- npx -y jevmem

{
  "mcpServers": {
    "jevmem": {
      "command": "npx",
      "args": [
        "-y",
        "jevmem"
      ]
    }
  }
}

[mcp_servers.jevmem]
command = "npx"
args = ["-y", "jevmem"]

{
  "mcpServers": {
    "jevmem": {
      "command": "npx",
      "args": [
        "-y",
        "jevmem"
      ]
    }
  }
}

{
  "servers": {
    "jevmem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "jevmem"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: TYPESAFE_API_KEY (TypeSafe API key for Jev, which add_memory, search_memory and audit_memory use. If unset, the server reads it from <project>/.jevmem/.env or ~/.jevmem/env), JEVMEM_ROOT (Project root, for clients that start the server without a project working directory (Claude Desktop). One server entry serves one project), TYPESAFE_BASE_URL (Send Jev requests through a proxy or gateway instead of api.typesafe.ai), JEVMEM_CACHE (0 turns off the answer cache in .jevmem/).