IWE

About

IWE turns a folder of connected Markdown documents into a knowledge base that an AI agent can search, read, write and reorganize. Notes hold specs, plans and decisions, and they stay ordinary files you can edit yourself, keep in git or sync. The same notes also work from the IWE CLI, editor plugins (Neovim, Helix, VS Code, Zed) and the iWe Mac app.

The MCP server runs locally over stdio from the npm package @iwe-org/mcp and works against the notes directory it is started in. It needs no IWE account and no API key. Run iwe init in the notes folder first. The agent you connect has its own setup and account requirements.

What you can do

• Give agents persistent memory stored as plain Markdown notes
• Search and read notes in a local folder
• Save decisions and lessons as notes you can edit or delete
• Organize linked notes across topics
• Share the same notes with CLI and editor tools

Tools

Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.

Example prompts

• Explore my IWE notes and summarize what's here.

• Save the decision we just made about the database schema to my notes.

• Look up what I wrote earlier about the release plan.

• Reorganize my project notes under a single overview note.

Set up

Every client starts IWE on your machine with the same command. Pick yours; the page remembers your choice.

claude mcp add --transport stdio iwe -- npx -y @iwe-org/mcp

{
  "mcpServers": {
    "iwe": {
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "iwe": {
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

code --add-mcp '{"name":"iwe","type":"stdio","command":"npx","args":["-y","@iwe-org/mcp"]}'

{
  "servers": {
    "iwe": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "iwe": {
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

codex mcp add iwe -- npx -y @iwe-org/mcp

[mcp_servers.iwe]
command = "npx"
args = ["-y", "@iwe-org/mcp"]

gemini mcp add iwe npx -- -y @iwe-org/mcp

{
  "mcpServers": {
    "iwe": {
      "command": "npx",
      "args": [
        "-y",
        "@iwe-org/mcp"
      ]
    }
  }
}

Embed

Show IWE in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge Website card iframe JSON AI prompt

README badge

Markdown

[![IWE on mcp.tc](https://mcp.tc/i/iwe/badge.svg)](https://mcp.tc/i/iwe)

HTML

<a href="https://mcp.tc/i/iwe"><img src="https://mcp.tc/i/iwe/badge.svg" alt="IWE on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML

<script src="https://mcp.tc/w/iwe.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML

<iframe src="https://mcp.tc/embed/iwe" title="IWE on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/iwe.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the IWE card to your site.

Markdown

Add the mcp.tc card for IWE, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/iwe.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="iwe"><a href="https://mcp.tc/i/iwe">IWE on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![IWE on mcp.tc](https://mcp.tc/i/iwe/badge.svg)](https://mcp.tc/i/iwe)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

1. 8 Oct 2026, 04:23 UTC, Automatic check

   New version 0.26.0 (was 0.25.0). Read from npm.

2. 6 Oct 2026, 21:23 UTC, Automatic check

   Tracking started: version 0.25.0.

FAQ