IWE turns a directory of markdown files into a knowledge graph — a connected structure you browse from your editor and your AI queries from the
IWE turns a directory of markdown files into a knowledge graph — a connected structure you browse from your editor and your AI queries from the command line. Same
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| find | Search notes with fuzzy matching |
| retrieve | Get a note with its children and parent context |
| tree | Show the hierarchy from any starting point |
| squash | Flatten a subtree into one document |
| new | Create a note (accepts content from stdin) |
| extract | Pull a section into its own note |
| inline | Merge a linked note back into its parent |
| rename | Rename a note; all links update automatically |
| delete | Remove a note and clean up references |
{
"mcpServers": {
"iwe": {
"command": "iwec",
"cwd": "~/notes"
}
}
}Configuration as documented by the project. Restart the client after saving.
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Structured knowledge base for AI agent solutions. Search, explore, and retrieve build logs.
Multi-platform AI memory. One save, recall everywhere—Claude, ChatGPT, Cursor, and more.
Part of the StudioMeyer MCP Stack — Built in Mallorca 🌴 · ⭐ if you use it
Read-only MCP for the Eco game wiki: search, Markdown pages, and wiki_ lookups. No keys, no writes.