IWE vs MCP Obsidian

A side-by-side look at the IWE and MCP Obsidian 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 requiredMCP Obsidian logoMCP ObsidianKnowledge & Memory · Local subprocess (stdio)MCP server that interacts with Obsidian via the Obsidian rest API community plugin48FairAuth: api key required

Verdict: choose IWE for knowledge & memory work; choose MCP Obsidian for knowledge & memory as a local process. 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

MCP Obsidian logoChoose MCP Obsidian when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: OBSIDIAN_API_KEY.
Explore MCP Obsidian

Feature & specification comparison

Rows where the two servers differ are marked.

SpecIWE logoIWEMCP Obsidian logoMCP Obsidian
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal44/100 · Fair48/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNo auth requiredAPI key required
PricingFreeFree
Required env varsNone listedOBSIDIAN_API_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars1,7914,489
Directory activity 2 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

IWE tools

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

MCP Obsidian 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.

MCP Obsidian

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "markuspfundstein-mcp-obsidian": {
      "command": "uvx",
      "args": [
        "mcp-obsidian"
      ],
      "env": {
        "OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

IWE is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. MCP Obsidian belongs to Knowledge & Memory and uses a local stdio subprocess. Pick IWE for knowledge & memory work and MCP Obsidian for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. IWE has no confirmed install command yet — follow its own setup instructions.

IWE is listed as free. Auth: no auth required. MCP Obsidian is listed as free. Auth: api key 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 markuspfundstein-mcp-obsidian 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. MCP Obsidian has 48/100 (Fair) with 7 views, 0 installs and 4,489 GitHub stars.