Skip to content
Wenlan

Comparison

Wenlan vs mcp-memory-service: Local AI Work Memory or Agent Pipeline Backend?

Compare Wenlan with mcp-memory-service across user workflow, transports, storage control, and agent-pipeline scope.

Qi-Xuan LuUpdated 5 min read

01

Wenlan keeps docs, skills and rules your AI tools work from, kept current, with cited sources.

02

mcp-memory-service is a broad self-hosted service with REST, MCP, dashboard, OAuth, remote/browser scenarios, and agent-framework scope.

03

Choose based on whether your job is daily AI work with maintained docs or backend memory infrastructure.

01

Quick answer

Choose Wenlan when you want docs, skills and rules for your own AI work, kept current in Claude Code, Cursor, Codex, and other MCP clients, with cited sources and git history. Choose mcp-memory-service when you want a self-hosted memory service for agent frameworks, HTTP clients, MCP tool users, remote/browser scenarios, and broader service operations.

Wenlan is not a memory infrastructure SDK. It is for people and teams using AI daily who want docs, skills and rules that stay current, with sources they can inspect. It works with the AI tools you already use.

02

When this problem appears

Both tools speak to persistent memory, but their center of gravity is different. Confusing them leads to the wrong setup: a personal work loop may take on operational overhead it does not need, while an agent backend may need transports Wenlan does not optimize for.

03

Choose by operating model

Ask what you are trying to run.

  • Choose Wenlan for Claude Code slash workflows, handoffs, Spaces, git history, and plain Markdown pages.
  • Choose mcp-memory-service for agent-framework backend needs, HTTP clients, web dashboards, OAuth, remote MCP, and browser/remote-client scenarios.
  • Compare setup complexity against the actual job.
  • Run a two-week trial with real captures instead of judging from feature checklists.

04

What to check next

This comparison uses public project descriptions. Check the upstream repositories before relying on details that may change quickly.

Side-by-side

Practical dimensions. Where mcp-memory-service leads, we say so.

DimensionWenlanmcp-memory-service
Primary userIndividuals and teams using AI tools daily who want shared docs, skills and rules.Builders operating a self-hosted memory service for agents, MCP clients, HTTP clients, and remote/browser use.
Workflow surfaceClaude Code plugin, MCP clients, CLI, handoff loop, pages, Spaces.REST API, MCP, CLI, dashboard, OAuth, and framework-oriented integrations.
API surfaceLocal daemon HTTP API on 127.0.0.1:7878 for CLI, MCP, desktop, and local scripts; not positioned as a hosted SDK surface.REST and MCP are first-class integration surfaces for agent and app backends.
Artifacts and indexesPlain Markdown pages, session logs, source trails, and local git history; the database is only an index.Service-managed records, tags, graph, dashboard, and APIs.
Best fitDocs, skills and rules for you or your team, kept current and self-hosted.Shared agent infrastructure where service operations are expected.

Try the local memory loop

Install Wenlan, connect your AI client, and verify that capture, recall, and handoff work on your machine.

FAQ

Is mcp-memory-service a direct Wenlan replacement?+
Not exactly. It overlaps on persistent memory, but it is more backend/service oriented while Wenlan keeps docs, skills and rules current for people using AI tools.
Can both be useful?+
Yes. A team could use a backend memory service for agent infrastructure and still prefer Wenlan for the docs and skills its people and AI tools work from.

Share this guide