Zenod — the AI librarian of your memory MCP Server

What the code does

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

    const child = spawn(command, args, { stdio: ["ignore", "ignore", "pipe"], ...(signal ? { signal } : {}) });

  document.getElementById("code").innerHTML = lines.map((l) => `<li class="${l[2] || ""}"><span>${fmt(l) || "&nbsp;"}</span></li>`).join("");

    const response = await this.fetchImpl(`https://api.telegram.org/file/bot${token}/${file.file_path}`, {

    const parts = (await readdir(dir)).filter((f) => f.startsWith("seg")).sort().map((f) => join(dir, f));

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

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

claude mcp add memory --transport http https://cloud.zenod.dev/mcp

https://cloud.zenod.dev/mcp

[mcp_servers.memory]
url = "https://cloud.zenod.dev/mcp"

{
  "mcpServers": {
    "memory": {
      "url": "https://cloud.zenod.dev/mcp"
    }
  }
}

{
  "servers": {
    "memory": {
      "type": "http",
      "url": "https://cloud.zenod.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints