Yggdrasil MCP Server

What the code does

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

PLIST="$HOME/Library/LaunchAgents/${LABEL}.plist"

  const r = spawnSync(cmd, ['--version'], { stdio: 'ignore' });

        return subprocess.call(["bash", str(INSTALL_SH), cmd, *rest])

    env = dict(os.environ)

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 yggdrasil -- uvx yggdrasil-memory

{
  "mcpServers": {
    "yggdrasil": {
      "args": [
        "yggdrasil-memory"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.yggdrasil]
command = "uvx"
args = ["yggdrasil-memory"]

{
  "mcpServers": {
    "yggdrasil": {
      "args": [
        "yggdrasil-memory"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "yggdrasil": {
      "args": [
        "yggdrasil-memory"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: YGG_ENGINE_URL (Base URL of the Yggdrasil engine HTTP API.), YGG_ENGINE_TOKEN (Bearer token for authenticating to the Yggdrasil engine (from ~/.yggdrasil/token after `ygg install`).). The author declared them in the registry entry; get the values from the project itself.