Phloem MCP Server

by canopyhq Your server? Claim it

local only

Phloem runs on your own machine — the client starts it, so there is no endpoint to ping.

Local-first AI memory with causal graphs. Fully offline, zero config, your data stays local.

The linked repository no longer exists on GitHub — it was deleted or made private.

—

Installs / week

not published

—

Stars

on GitHub

—

Last commit

from GitHub

—

License

language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Alternatives to Phloem

same job, measured the same way

Yggdrasil

by vondervuflya

One shared, durable memory for your AI coding agents — local-first, zero-dependency.

341 installs/wk local only

Midas

by vornicx

Local-first, source-traceable agent memory — no LLM at ingest, fully offline

59 installs/wk local only

chatmux

by echoedinvoker

Local-first MCP server for your own LINE and Telegram chats. Data stays on your machine.

local only

Memory Engine MCP

by simoneb79

Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.

local only

Superlocalmemory

by varun369

Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.

848 installs/wk local only

heropen — AI Agent Memory

by heropen

Persistent memory for AI agents: local-first MCP server, zero-config. No cloud, no API keys.

local only

ContextDB Memory

by mikhailbovt

Local-first durable AI memory with policy-bound recall and a typed project graph.

local only

Backstory: search your data exports locally

by magna-nz

Search your Google, Telegram, Spotify and Instagram exports locally. Fully offline.

local only

Phloem — questions

Answers built from our own checks of this server.

Why is there no uptime for Phloem?

Phloem runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.

Is Phloem still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.