Filamental

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/scottnine-filamental

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

10 read · 3 write · 2 delete · 2 not yet classified

Secrets

None asked for

Install scripts

None found

Runs as

Node.js package

Tools (17)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• create_edge

  Add a relationship from one node to another. Reads the source node file, appends the relationship, writes it back, and updates the SQLite index. Returns { edge_id, source_id, target_id }.

• create_node

  Create a new node in the vault. Writes a markdown file and updates the SQLite index. Returns { id, file_path }. Call get_node(id) to retrieve the full record.

• delete_edge

  Remove a relationship from the vault. Reads the source node file, strips the matching relationship, writes it back, and updates the SQLite index. Returns { deleted: true, edge_id }.

• delete_node

  Delete a node from the vault. Removes the markdown file and all references from the SQLite index (entities, FTS, relationships). Returns { deleted: true, file_path }.

• extract_section

  Move a heading's section out of a node into a new node of its own. The heading stays behind with a [[wikilink]] where the content was, and a connector is created from the source to the new node. A section runs to the next heading of the same or higher level, so extracting an h2 takes its h3 children with it. Content is MOVED, not copied: exactly one copy survives. Use dry_run first to see what would move.

• get_connections

  Get every edge connected to a node. Each result is stated from the point of view of the node you asked about: `node` is that node, `other` is the node at the far end, and `direction` says where the arrowhead is drawn as seen from `node` — "outgoing" points away at `other`, "incoming" points back at `node`, "bidirectional" points both ways, "none" is a plain line with no arrow. This is what the user actually sees on the graph. It is deliberately not the raw stored value, which is relative to whichever end the connector happened to be drawn from and is invisible to the user. `stored_on` names th…

• get_context

  Assemble one readable markdown document for a node and its neighbourhood: the node's notes plus the notes of every node within `depth` hops, inlined with headings that track hop distance and the connector each was reached by. Use this instead of get_subgraph + repeated get_node when you want to READ the surrounding content rather than inspect graph shape. Set dry_run to size the result before pulling it.

• get_node

  Retrieve full node data for a given entity UUID, including the markdown note body in the `notes` field.

• get_subgraph

  BFS traversal from a root node collecting all reachable nodes and edges up to the given hop depth. Results are deduplicated.

• get_vault_info

  Return summary counts (nodes, edges) and the top-level entity and connector type names configured for this vault.

• inline_section

  Fold a node's content back into another node: the inverse of extract_section. The content lands where the [[wikilink]] to it already sits, or is appended if there is no such link, and the connector between the two is removed. The target node is DELETED by default, because keeping it would leave the same text in two files. Deletion is refused if the target is connected to anything other than the source. Pass delete_target: false to keep the node as an empty stub instead. Use dry_run first.

• list_connector_types

  Return the full connector type configuration for this vault (from .filamental/connector_types.json).

• list_node_types

  Return the full entity type configuration for this vault (from .filamental/entity_types.json).

• read_format_reference

  Read the exact on-disk file format: the YAML frontmatter fields of a node markdown file, how relationships are stored, and what the .filamental folder holds. Needed only when reading or writing vault files directly rather than through these tools.

• read_skill_guide

  Read the full Filamental skill guide: how to design a space, choose entity and connector vocabularies, set colours, arrow directions and physics weights, and the conventions that make a structure readable. The server instructions already carry the essentials, so reach for this when you need depth: building a substantial structure from scratch, or a question the essentials do not settle.

Signals

Stars

2

Forks

0

Open issues

0

Last commit (this folder)

Sep 4, 2026 (1 month ago)

Last release

Oct 26, 2026 (5 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.Scottnine/filamental

Version

0.2.16

Auth

No auth

Packages

npm filamental-mcp

License

License unknown

Repository

github.com/Scottnine/filamental

First seen

Oct 24, 2026

Last checked

Oct 26, 2026

Source

Official MCP Registrygithub-graphql