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 connecting documentation tools to Claude, Cursor, VS Code, or another MCP client. The project is written in Rust.

VERIFIED ACTIVE

LAST COMMIT 2026-08-24 · ★ 1,571 · #17 OF 183 MAINTAINED DOCUMENTATION · VERIFIED 2026-08-25

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.20.1 · 2026-08-24

The MCP server now speaks every protocol revision from 2024-11-05 through 2026-07-28, so newer clients that negotiate a recent revision - or probe with server/discover - connect cleanly instead of being pinned to…

iwe-v0.20.0 · 2026-08-24

IWE can now remember across Claude Code sessions: iwe init offers to switch memory on when it finds a .claude/ directory, session transcripts are digested into a queue, and an agent distills each one into your markdown…

iwe-v0.19.1 · 2026-08-15

Maintenance release - no user-visible changes to the CLI, LSP server, or MCP tools. · It republishes the npm packages with the ownership metadata the official MCP Registry requires, so IWE's MCP server can be listed…

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 #17 of 183 actively-maintained documentation servers as of 2026-08-25.
release cadence
10+ releases in the last 90 days (latest 2026-08-24)
registry
io.github.iwe-org/iwe (active, first published 2026-08-15 · 3 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-08-25, its last commit was 2026-08-24 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