IWE MCP Server

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. Version everything with git. It runs locally over stdio via the published package.

People who work with lsp, markdown and notes and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in Rust.

VERIFIED ACTIVE

LAST COMMIT 2026-09-17 · ★ 1,650 · #9 OF 208 MAINTAINED DOCUMENTATION · VERIFIED 2026-09-18

Apache-2.0 · Rust servers · how we verify → /methodology

01 · Install IWE

Claude Code

claude mcp add iwe-org-iwe -- npx -y @iwe-org/mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "iwe-org-iwe": {
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license Apache-2.0 - declared in the repository

npm package @iwe-org/mcp - published under the repo owner's npm scope (@iwe-org)

registry namespace io.github.iwe-org is GitHub-verified and matches the repo owner

03 · What IWE can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

iwe-v0.24.1 · 2026-09-16

Running iwe normalize over a whole library no longer rewrites every file: documents whose formatting does not change are left alone, so their modification times and the library's edit history survive. Every command…

iwe-v0.24.0 · 2026-09-09

You can now scope a query to a folder. $startsWith on $key selects every · document whose key begins with a prefix - --filter '$key: { $startsWith: notes/ }' · on the CLI, the same shape in the iwe_query MCP tool - so…

iwe-v0.23.2 · 2026-09-08

Formatting a long paragraph with wrap_column set is safe again. When the wrap pushed a character like -, #, > or --- to the start of a new line, the next read saw it as a list, heading, quote or rule and reshaped your…

04 · Who maintains IWE

IWE is maintained by iwe-org. It's the only MCP server we track from this author; the repo dates to Sep 2024.

05 · Facts

website
https://iwe.md/
category
documentation - ranked #9 of 208 actively-maintained documentation servers as of 2026-09-18.
release cadence
10+ releases in the last 90 days (latest 2026-09-16)
registry
io.github.iwe-org/iwe (active, first published 2026-08-15 · 10 versions)
packages
npm:@iwe-org/mcp

06 · IWE FAQ

What is IWE?

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. Version everything with git. It runs locally over stdio via the published package.

Is IWE still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-17 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

How do I install IWE?

Run `npx -y @iwe-org/mcp`. You can also paste the ready-made client config above.

Does IWE run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to IWE