Iwe

v1.0.0Knowledge & Memorystable

Markdown memory system for you and your AI agent

aiai-agentsclideveloper-toolsgraph
Share:
1,051
Stars
0
Downloads
0
Weekly
0/5

What is Iwe?

Iwe is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to markdown memory system for you and your ai agent

Markdown memory system for you and your AI agent

This server falls under the Knowledge & Memory category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • Markdown memory system for you and your AI agent

Use Cases

Markdown-based memory system for AI agents
Knowledge graph and GTD task management
iwe-org

Maintainer

LicenseApache-2.0
Languagerust
Versionv1.0.0
UpdatedMay 22, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx iwe

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use Iwe

Iwe is a Markdown-native personal knowledge management system and MCP server written in Rust, designed to give both humans and AI agents structured access to a local notes workspace. It exposes a command-line interface with eight operations — including fuzzy find, hierarchical retrieval, subtree squashing, section extraction, and automatic link refactoring on rename — and integrates with editors like Helix via an LSP server. The `iwec` MCP client binary lets Claude Desktop, Cursor, and Windsurf query and manipulate your notes through natural language.

Prerequisites

  • Rust toolchain or Homebrew (macOS/Linux) for installation
  • A directory of Markdown notes to use as the workspace
  • An MCP-compatible client such as Claude Desktop, Cursor, or Windsurf
  • Basic familiarity with Markdown and knowledge management concepts
1

Install iwe

Install the iwe suite — the core `iwe` CLI, the `iwes` LSP server, and the `iwec` MCP client — using Homebrew or Cargo.

# Homebrew (macOS/Linux)
brew tap iwe-org/iwe
brew install iwe

# Or via Cargo
cargo install iwe iwes iwec
2

Initialize your notes workspace

Navigate to the directory that contains (or will contain) your Markdown notes and run `iwe init` to set up the workspace metadata.

cd ~/notes
iwe init
3

Test basic CLI operations

Verify the installation by running a fuzzy search across your notes and retrieving a note with its hierarchy context.

iwe find auth
iwe retrieve --key authentication --depth 2
iwe tree
4

Configure Claude Desktop

Add the `iwec` MCP server to your Claude Desktop configuration file. Replace `~/notes` with the absolute path to your workspace.

5

Restart Claude Desktop and verify connection

Restart Claude Desktop. The iwe server should appear in the connected tools list. Ask Claude to list or search your notes to confirm the integration works.

Iwe Examples

Client configuration

Add this block to `claude_desktop_config.json`. Replace `~/notes` with the absolute path to your Markdown workspace.

{
  "mcpServers": {
    "iwe": {
      "command": "iwec",
      "args": ["--project", "/Users/yourname/notes"]
    }
  }
}

Prompts to try

Sample prompts to use with iwe connected to Claude Desktop.

- "Search my notes for anything related to authentication and summarize what I have."
- "Show me the hierarchical structure of my project notes."
- "Retrieve my note on OAuth2 with two levels of sub-notes."
- "Create a new note titled 'API Design Patterns' with these key points: [your points]."
- "Rename my note 'old-project' to 'legacy-api' and update all links automatically."

Troubleshooting Iwe

`iwec` command not found after installation

Ensure the Cargo bin directory (`~/.cargo/bin`) is in your PATH, or that the Homebrew prefix is on your PATH. Run `which iwec` to verify. If missing, re-run `cargo install iwec` or `brew install iwe`.

Claude Desktop shows iwe as connected but find/retrieve return empty results

Verify the `--project` path in the config is an absolute path (not `~/notes`) and that the directory was initialized with `iwe init`. Confirm your notes are `.md` files directly inside that directory.

LSP server (iwes) crashes in Helix or another editor

Update to the latest version with `brew upgrade iwe` or `cargo install iwe iwes iwec`. Check that the editor's LSP config points to the `iwes` binary, not the `iwe` CLI.

Frequently Asked Questions about Iwe

What is Iwe?

Iwe is a Model Context Protocol (MCP) server that markdown memory system for you and your ai agent It connects AI assistants to external tools and data sources through a standardized interface.

How do I install Iwe?

Follow the installation instructions on the Iwe GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with Iwe?

Iwe works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is Iwe free to use?

Yes, Iwe is open source and available under the Apache-2.0 license. You can use it freely in both personal and commercial projects.

Browse More Knowledge & Memory MCP Servers

Explore all knowledge & memory servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "iwe": { "command": "npx", "args": ["-y", "iwe"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use Iwe?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides