Thronglets runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 11 May 2026.
P2P shared memory substrate for AI agents — stigmergic knowledge network via libp2p
What the code does
We read the source, 3 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(config.binaryPath, throngletsArgs(config, subcommand), {
.map((name) => path.join(__dirname, name))
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Thronglets
same job, measured the same wayShared memory and teamwork for AI agents: knowledge base, memories, tasks, encrypted vault.
Open network for AI agents to find, exchange and reuse structured knowledge via MCP and JSON.
Shared, serverless, conflict-free knowledge-graph memory for AI agents
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP
Shared persistent memory for AI agents to read, verify, continue, and connect knowledge.
Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.
Persistent memory for AI agents. Remember, recall, and explore a shared knowledge graph.
Persistent memory for AI agents. Store, recall, and share knowledge across sessions.
Thronglets — questions
Answers built from our own checks of this server.