MCP Servers · Memory
IWE (iwe.md)
by iwe-org
Markdown knowledge graph — LSP for your editor, CLI + MCP memory for your AI agents
Our verdict
We have not reviewed IWE (iwe.md) yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About IWE (iwe.md)
Markdown knowledge graph — LSP for your editor, CLI + MCP memory for your AI agents
Best for
Developers building markdown-centric knowledge bases with AI agent integration.
Use cases
- Link and navigate markdown notes as a knowledge graph in an editor
- Provide AI agents with persistent memory via MCP
- Query and manage markdown-based knowledge from the CLI
Notes
1,821 stars on GitHub. Last updated 2026-11-08. Licensed Apache-2.0.
Indexed from mcp-official-registry. Verified against the live GitHub repo.
Pros
- Fast and lightweight due to Rust implementation
- Integrates with editors via LSP and agents via MCP
- Open source with active community (1.8k stars)
Cons
- Requires Rust toolchain for building from source
- Markdown-specific, not suitable for other data formats
- Young project, may lack mature documentation
Key facts
What we have checked
- Days since the last commit
- 1
- GitHub forks
- 94
- GitHub stars
- 1,821
- Days to a first reply on issues
- 0.6
- Open issues
- 1
- Releases in the last 90 days
- 23
Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
brew install iwe-org/iwe/iweClients the listing names (not checked here)
Claude Desktop, Claude Code, Cursor, VS Code
Install
Add IWE (iwe.md) to your client
No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.
Until then, follow the project's own README, or the setup the listing publishes under How to set it up.
Works with
What IWE (iwe.md) connects to
No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.
Stars and usage
How IWE (iwe.md) is growing
1,804 to 1,821
Health and security
Is IWE (iwe.md) looked after, and what do its setup files show
Health score
80 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 30 of 30 | Last push 1 days ago |
| Releases | 15 of 15 | 23 releases in 90 days |
| Issue replies | 20 of 20 | First reply in 0.6 days (median) |
| Maintainer | 15 of 15 | Owned by an organisation |
| Official source | 0 of 20 | Community server |
Alternatives
Alternatives to IWE (iwe.md)
| Record | Type | How we know | Checked |
|---|---|---|---|
| 0spoon/seamlessAlternative to this | MCP server | Matched from the listing text |
Compare
Compare IWE (iwe.md) side by side
Sources
Where this comes from
- GitHubRegistry
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Open-source & AI alternatives
Swap-in tools that solve the same job. Weigh the trade-offs before you commit.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.