IWE

IWE turns a directory of markdown files into a knowledge graph, exposed both as a language server for editors and as an MCP server for AI agents. The MCP server, implemented in the iwec crate of the iwe-org/iwe Rust workspace, exposes fourteen tools including iwe_find, iwe_create, iwe_query and iwe_rename, plus three prompts and four resources. It is distributed as the npm installer package @iwe-org/mcp and, separately, as the crates.io package iwe; it communicates over stdio by default, with an optional self-hosted streamable-http mode reachable at /mcp when the operator starts it with --transport http. The HTTP mode binds to 127.0.0.1 by default and documents no built-in authentication, leaving TLS and access control to a reverse proxy for any exposure beyond localhost.

The GitHub organization iwe-org owns the repository and lists iwe.md as its blog URL; that same site links back to github.com/iwe-org/iwe repeatedly as its canonical source and releases page. The repository's own server.json, which the registry ingests, was authored in the same repo and matches the live registry record exactly, and the npm package's maintainer email, dmytro@iwe.md, sits on the product's own domain. Because the team that builds and documents IWE at iwe.md is the same team publishing the MCP server, authority is first_party.

No README, documentation page, changelog entry or server.json names a supported MCP specification revision. The iwec crate depends on rmcp version 3, the official Rust MCP SDK, but that dependency range is not itself evidence of which revision the server implements, so spec_status remains unknown.