M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionIWETurn a folder of Markdown notes into a queryable knowledge graph for you and your AI agentsSafe Docx MCP ServerAI-native surgical editing of Word and OpenDocument files with formatting preservation
FMRS56 / 100 · C68 / 100 · C
Reliability8 / 208 / 20
Security and permissions11 / 2016 / 20
Maintenance13 / 2014 / 20
Documentation13 / 2018 / 20
Setup experience11 / 2012 / 20
Best for
  • Individuals whose knowledge lives in plain markdown files and who value local-first, git-versioned notes.
  • AI agent users who want their note graph as agent memory and want retrieval by structure rather than similarity guessing.
  • Developers and writers who use both an editor LSP workflow and the command line over the same notes.
  • Teams that need agent writes to declare their blast radius and to pass schema and graph-hygiene checks.
  • Developers who need precise, format-preserving edits to .docx/.odt files via coding agents
  • Workflows that require tracked-changes output for human review
Not for
  • People who want a cloud-hosted notes or memory service with no local file directory.
  • Users expecting the server to include its own AI model or inference — IWE has no built-in AI and must be paired with an external agent.
  • Scenarios that only need generic vector search and do not care about note hierarchy or link structure.
  • Builders who need a stable library-level API — the liwe crate is published but not yet API-stable.
  • Visual editing scenarios needing browser rendering, real-time collaboration, or pixel-level pagination guarantees
  • Using .dotx templates directly (they must be converted to .docx first)
Required permissions
  • Read markdown note files under the working directory the server is started in.
  • Write and modify note files in that directory, including creating, renaming, deleting, refactoring, and targeted block updates.
  • Watch the notes directory for file changes so editor edits are reflected immediately.
  • Communicate over stdio with MCP clients; running via npx requires network access to fetch the @iwe-org/mcp package.
  • Filesystem access to read and write local .docx / .odt documents
Risks and side effects
  • The agent holds write access to the notes directory; MCP writes must declare expect guards and validate before writing, but permitted changes still land on disk.
  • Pointing the MCP server at the wrong working directory lets the agent read and write markdown files in an unintended folder.
  • Using npx fetches an npm package from the network on first run, adding a dependency on the network and the upstream package.
  • Validation covers schemas, frontmatter, and graph-hygiene warnings, but dangling links, orphan pages, and near-duplicates are surfaced as warnings and still need human judgement.
  • The liwe crate in the repository is published but not yet API-stable, so projects building on it should pin versions.
  • Edits apply to local files; incorrect targeted changes could overwrite original content — use the clean/tracked-changes dual output for review
  • The project is not a visual editor or layout engine, so complex layout results should be verified manually
Supported clientsClaude Code, Claude Desktop, Cursor, Windsurf
Tools50