IWE vs NoteDiscovery

A side-by-side look at the IWE and NoteDiscovery MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

IWE logoIWEKnowledge & MemoryMarkdown knowledge base as agent memory. Runs against the notes directory it is started in.44FairAuth: no auth requiredNoteDiscovery logoNoteDiscoveryKnowledge & MemorySelf-hosted plain-markdown knowledge base with a built-in MCP server. Lets Claude Desktop, Cursor, and any MCP client search, read, create, edit, tag, and template notes — same vault that powers the web UI. Pure-stdlib client, no extra deps, MIT-licensed. Can run in Docker.55GoodAuth: no auth required

Verdict: choose IWE for knowledge & memory work; choose NoteDiscovery for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

IWE logoChoose IWE when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
Explore IWE

NoteDiscovery logoChoose NoteDiscovery when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: NOTEDISCOVERY_URL.
Explore NoteDiscovery

Feature & specification comparison

Rows where the two servers differ are marked.

SpecIWE logoIWENoteDiscovery logoNoteDiscovery
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal44/100 · Fair55/100 · Good
Install commandNot confirmed yetNot confirmed yet
Transport——
AuthNo auth requiredNo auth required
PricingFreeFree
Required env varsNone listedNOTEDISCOVERY_URL
Verified ownerCommunity listingCommunity listing
GitHub stars1,7912,847
Directory activity 2 views 0 installs 0 upvotes 6 views 2 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

IWE tools

No tool names declared yet. Check the project README from the listing page.

NoteDiscovery tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

IWE

No confirmed install command for IWE yet — follow the setup steps linked from its listing page rather than a guessed package name.

NoteDiscovery

No confirmed install command for NoteDiscovery yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

IWE is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. NoteDiscovery belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick IWE for knowledge & memory work and NoteDiscovery for knowledge & memory.

Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.

IWE is listed as free. Auth: no auth required. NoteDiscovery is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add iwe and gamosoft-notediscovery as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, IWE has a quality signal of 44/100 (Fair) with 2 views, 0 installs and 1,791 GitHub stars. NoteDiscovery has 55/100 (Good) with 6 views, 2 installs and 2,847 GitHub stars.