IWE

Agents ship with an instructions file — CLAUDE.md, AGENTS.md — and it's tempting to let memory accumulate there too. It doesn't hold. Instructions are rules; memory is what builds up: decisions, corrections, the state of everything in flight. Kept in one flat file, the agent appends, contradictions pile up side by side each looking authoritative, and every session re-reads the whole thing.

IWE stores memory as many small linked documents, so the agent asks instead of re-reading. Most recall is a structured question — what's still open, what did we decide about X, which notes mention this person — answered by a query and one retrieve call that expands the linked context. The rest of the graph stays out of the context window. And because it's markdown in git, the memory is inspectable: open what the agent believes, diff what changed, git-blame when.

IWE treats your notes as a connected structure. You organize them with two types of links:

This structure makes retrieval powerful — whether you're browsing in your editor or an agent is querying via CLI, ask for a topic and get its full context in a single call.

IWE gives AI agents structured access to your notes through two interfaces: a CLI for scripting and shell-based workflows, and an MCP server for native connection with AI tools. Both expose the same operations — search, retrieve, create, refactor — so you can choose whichever fits your setup.

IWE pairssearch with structure: built-in fuzzy and full-text search finds the entry point, and the graph turns a hit into usable context — parent context, children, cross-references, link-safe refactoring. It also composes cleanly with any external tooling you already use (ripgrep, full-text, vector): whatever finds the note, IWE supplies the context around it.

The CLI lets you (and AI agents) work with your notes from the terminal or in scripts.

Example: preparing context for an AI conversation

iwe find --fuzzy auth iwe retrieve --key authentication --expand-includes 2 iwe tree --key oauth

- Search— find notes by title or content
- Navigate— go to definition, find references (backlinks)
- Preview— hover over links to see content
- Auto-complete— link suggestions as you type
- Inlay hints— show parent references and link counts
- Extract— pull sections into new notes
- Inline— embed note content back into parent
- Rename— rename files with automatic link updates
- Format— normalize documents, update link titles
- Transform— pipe text through external commands
- Templates— create notes from templates (daily notes, etc.)
- Outline conversion— switch between headers and lists

Connect your AI agent— point it at the MCP server.iwecserves the directory it runs in, so set the working directory to your notes:

{ "mcpServers": { "iwe": { "command": "iwec", "cwd": "~/notes" } } }

No install needed —npxfetches the server on demand:

Standalone Obsidian MCP server with semantic search, knowledge graph analytics (PageRank, Louvain, shortest path), and vault editing — no plugin, no REST API, works when Obsidian is closed.

Markdown and Obsidian compatible knowledge graph.

An MCP server for interacting with the YuQue knowledge base, enabling AI assistants to perform operations on documents and information.

NVIDIA AI Developer Stack as Compressed Knowledge Graph (CKG) - 20 domains, 998 notes, agents traverse typed dependency edges instead of scanning docs.

Automated document processing and extraction

Convert files (DOCX, XLSX, PPTX, images), HTML, and Markdown to pixel-perfect PDFs — npx stdio or hosted Streamable HTTP, free API key in one click.

Connect with 10,000+ tools across HRIS, ATS, CRM, Accounting, Calendar, Meeting, Ticketing, and more categories.

Official Notion MCP server for searching, reading, creating, and updating Notion pages, databases, and workspace content from AI agents.

Collaborative word processor you can use with your agent