Add Filamental to Zed as an MCP server and the agent in Zed can read a structure of the decisions, constraints and dependencies around your code, and add to it. It’s a local process reading Markdown on your own disk, with no account behind it, set up from Zed’s own settings. Free on every plan.
In Zed, open Settings, then AI, then MCP Servers, click Add Server and choose Add Local Server. Or add it to your settings file yourself, under context_servers:
"context_servers": {
"filamental": {
"command": "node",
"args": [
"--no-warnings",
"/absolute/path/to/filamental-mcp/dist/index.js",
"--vault",
"/absolute/path/to/your/vault"
],
"env": {}
}
}Mind the key. Zed calls them context servers, so an entry copied from another client under mcpServers won’t be read. The command and arguments are the same; only the key they sit under changes. Copy both absolute paths from Settings, then AI, then Other AI apps inside Filamental rather than typing them, since the server ships with the application and lands somewhere platform-specific.
Back in Settings, then AI, then MCP Servers, the dot beside filamental turns green and its tooltip says the server is active. Any other colour means the configuration needs another look.
An agent working in your editor can find what calls what without any help, because that’s written in the code. What it can’t find is why, such as the constraint that ruled out the obvious approach, the decision a change would quietly reverse, or the dependency that only exists in a contract.
In a space those are typed connections between named things. The agent can read the ones that touch the file in front of it, follow them to whatever they depend on, and ask for the route between two things when it wants to know whether they’re related at all.
It writes too, so a decision can be recorded from the agent panel while it’s being made, rather than reconstructed later by whoever inherits it.
A short briefing arrives when the connection opens, covering what nodes, categories and connectors are and the conventions that keep a structure readable, and the full skill guide and file format specification are pulled on demand only when a task needs them.
Both are published on this website in full, word for word as they are sent: the skill file and the file format reference. Nothing else runs underneath them. The server is a local process with no network access of its own, and Filamental has no account, no sign-in and no telemetry of any kind.
One prerequisite, and it is the only one that catches people out. The server reads the index Filamental builds and never builds one itself, so the space has to have been opened in the application at least once on that machine. A folder it has not seen stops with a message saying exactly that. If reading a folder somebody sent you is what you want, point the AI at the files directly instead, since a space is plain Markdown and no index is involved.
You need Node.js 22 or later and Filamental v0.2.4 or later, on Windows, macOS or Linux. The server ships inside the application, so there is nothing separate to install, and it is also on npm as filamental-mcp for a machine without Filamental on it.
The connection is free on the Personal plan, which is free permanently with no account and no card, and it is not metered, credited or seat-limited. The paid tier is $120 a year, or $12 a month, and covers handing work over beyond the one live link that’s free.
In Zed, open Settings, then AI, then MCP Servers, click Add Server and choose Add Local Server, or add an entry named filamental under context_servers in your settings file. Give it node as the command, and the bundled server's path followed by --vault and your space folder as the arguments. Copy both absolute paths from Settings, then AI, then Other AI apps inside Filamental.
Because Zed reads MCP servers from a key called context_servers in its own settings file, not from mcpServers, which is what most other clients use. The command and the arguments are the same, so copy the entry across and change the key it sits under.
Open Settings, then AI, then MCP Servers in Zed. If the dot beside filamental is green and its tooltip says the server is active, it is running. Any other colour means something in the configuration needs attention, most often a path, or a space that has never been opened in Filamental on that machine.
No. The MCP server is a separate local process reading the same folder, so it works whether or not the application window is open, and the --vault argument means it does not depend on which space you last had open. Many people keep Filamental open on a second screen anyway, since watching the structure change while the model writes to it is the quickest way to catch it misunderstanding something.
No, because there is nothing of ours in the path. The server is a local process talking to Markdown files in a folder on your own disk, and whatever leaves the machine is what Zed sends to whichever model provider you have chosen, exactly as it does for the rest of your work. Filamental has no account, no sign-in and no telemetry of any kind.
Nothing. It is free on the Personal plan, which is free permanently with no account and no card, and it is not metered, credited or seat-limited. The paid tier, at $120 a year or $12 a month, covers handing work over beyond the one live link that's free, such as more links, updating a link already sent, the HTML download and presenting.
One node for the decision, one for each constraint behind it, and the connections between them. The next person to ask the agent why gets an answer.