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 MCP server exists for a simple reason — assistants are far more useful when they can act on Iwe directly instead of describing what you should do. 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 files, same links, two interfaces. No cloud, no database, no lock-in.
Once Iwe is connected, these are the calls the assistant has available:
find — Search notes with fuzzy matchingretrieve — Get a note with its children and parent contexttree — Show the hierarchy from any starting pointsquash — Flatten a subtree into one documentnew — Create a note (accepts content from stdin)extract — Pull a section into its own noteinline — Merge a linked note back into its parentrename — Rename a note; all links update automaticallydelete — Remove a note and clean up referencesSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Iwe's toolset — find, retrieve, tree and 6 more — is a fair guide to whether it matches your workflow. It is maintained by iwe-org; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| 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.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.