What is the key difference between Mwe Mcp — Memory Wiki Engine and Codebase Memory MCP?

Mwe Mcp — Memory Wiki Engine belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Codebase Memory MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mwe Mcp — Memory Wiki Engine or Codebase Memory MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Mwe Mcp — Memory Wiki Engine and Codebase Memory MCP free or paid?

Mwe Mcp — Memory Wiki Engine operates under a Free / Open Source model (No auth required). Codebase Memory MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mwe Mcp — Memory Wiki Engine lists 0 tools with 0 views and 6 GitHub stars. Codebase Memory MCP lists 17 tools with 7 views and 43,832 GitHub stars.

Can I use both Mwe Mcp — Memory Wiki Engine and Codebase Memory MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Mwe Mcp — Memory Wiki Engine vs Codebase Memory MCP

In-depth architectural comparison of the Mwe Mcp — Memory Wiki Engine and Codebase Memory MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Mwe Mcp — Memory Wiki Engine

Knowledge & Memory · Remote HTTP/SSE

Quality: 41/100 (Fair) | Auth: No auth required

Codebase Memory MCP

Knowledge & Memory · Local stdio

Quality: 73/100 (Great) | Auth: No auth required

Verdict Summary: Choose Mwe Mcp — Memory Wiki Engine if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Codebase Memory MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Mwe Mcp — Memory Wiki Engine when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Mwe Mcp — Memory Wiki Engine Details

Choose Codebase Memory MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: index_repository, search_graph, query_graph.

Explore Codebase Memory MCP Details

Feature & Specification Comparison

Specification	Mwe Mcp — Memory Wiki Engine Knowledge & Memory	Codebase Memory MCP DeusData Knowledge & Memory
Summary	Self-hosted multi-user memory for AI agents: a human-readable Markdown wiki with per-fragment ACL.	Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp
Category & Scope

Tools & Capabilities Breakdown

Mwe Mcp — Memory Wiki Engine Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Codebase Memory MCP Tools (17)

index_repository

Index a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.

search_graph

Find symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.

query_graph

Read-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.

trace_path

Trace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Mwe Mcp — Memory Wiki Engine Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mwe-mcp-memory-wiki-engine": {
      "url": "http://127.0.0.1:8742/mcp"
    }
  }
}

Codebase Memory MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

Frequently Asked Questions

Mwe Mcp — Memory Wiki Engine is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Codebase Memory MCP belongs to Knowledge & Memory using local stdio subprocess. Select Mwe Mcp — Memory Wiki Engine when you need capabilities focused on knowledge & memory and Codebase Memory MCP when you require tools for knowledge & memory.

More alternatives to Mwe Mcp — Memory Wiki Engine More alternatives to Codebase Memory MCP Knowledge & Memory category hub Canonical compare URL