weave runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 16 Oct 2026.
Connected tables, relations, workflows and markdown documents in one SQLite file, over MCP.
What the code does
We read the source, 22 h ago · rules ccca72095570
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 next = String(text ?? '').slice(0, suggestion.start) + item.insert + String(text ?? '').slice(suggestion.end);
cp.execSync(cmd);
return new Function(src)();
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 weave
same job, measured the same wayRule-tiered AST and sqlite-vec capability oracle for A-MEM agent workflows.
Zero-config MCP server for searchable documentation. SQLite or PostgreSQL.
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.
Project tracker for AI agents: roadmap, periods, tasks and a validation gate, in one SQLite file
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
Record debug sessions, commands, failed attempts, and successful fixes in local SQLite storage.
Records coding-agent decisions with their limits and marks old ones superseded. Local SQLite.
weave — questions
Answers built from our own checks of this server.