Which end of a connector is stored as source depends on which end you happened to drag from, and that is invisible on the graph — so a naive server hands back edges that read backwards half the time. `get_connections` reports direction relative to the node you asked about, the way it looks on screen, and filtering by outgoing gives you arrows pointing away from that node rather than edges that merely list it as source. Writes go to the Markdown and the index together, so this is a full seat at the vault, not a viewer.
A local server that opens the same SQLite index the Filamental desktop app uses, so an assistant can search your vault, follow its connections and write new nodes back. It follows whichever vault you currently have open. Writes update the Markdown file on disk and the index together, so the app shows the change on next load.
- `search_nodes` runs full-text search across node names, note bodies and property values
- `get_node` returns a full node record by UUID; `get_connections` returns every edge on it
- `get_subgraph` walks outward from a root node, up to max depth 3
- `create_node`, `update_node` and `delete_node` write the Markdown file and update the index together
- `create_edge` and `delete_edge` add and remove relationships between two nodes
- `get_vault_info`, `list_node_types` and `list_connector_types` report counts and the vault's type configuration
Node.js 22 or later, plus the Filamental desktop app with at least one vault opened — the app is what creates the SQLite index this server reads. Install with `npm install -g filamental-mcp` (package `filamental-mcp`, version 0.2.9) and point your client at it over stdio, or let the app write the config from Settings > AI Integrations. The prebuilt `better-sqlite3` binary is Windows x64 only; other platforms build from source.
One command — npm install -g filamental-mcp