What is the key difference between Linklore MCP and Moxie Docs MCP?

Linklore MCP belongs to the Knowledge & Memory category with local stdio execution, while Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Linklore MCP or Moxie Docs 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 Linklore MCP and Moxie Docs MCP free or paid?

Linklore MCP operates under a Free / Open Source model (No auth required). Moxie Docs MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Linklore MCP lists 24 tools with 2 views and 1 GitHub stars. Moxie Docs MCP lists 12 tools with 23 views and 2 GitHub stars.

Can I use both Linklore MCP and Moxie Docs 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

Linklore MCP vs Moxie Docs MCP

In-depth architectural comparison of the Linklore MCP and Moxie Docs 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

Linklore MCP

Knowledge & Memory · Local stdio

Quality: 57/100 (Good) | Auth: No auth required

Moxie Docs MCP

Knowledge & Memory · Local stdio

Quality: 80/100 (Excellent) | Auth: API Key required

Verdict Summary: Choose Linklore MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Moxie Docs 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 Linklore 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: doc_flow, doc_map, brief.

Explore Linklore MCP Details

Choose Moxie Docs MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Feature & Specification Comparison

Specification	Linklore MCP linklore Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	AI-native structured memory for coding agents — typed lore/doc entries with status and links, read and written by agents via MCP.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope

Tools & Capabilities Breakdown

Linklore MCP Tools (24)

doc_flow

[read-only] doc_flow(id) — renders a doc's flowLink chain in order (journey view).

doc_map

[read-only] doc_map(oneline) — overview of the full doc link network.

brief

project dashboard — call at the start of every session. external source 🔔 = a new push has arrived. receive it with openbox(action='show'). options: dismiss(turn off a nudge), undismiss(restore it), help.

init

init(blueprint='') — set up .linklore in this directory (starts local footprint memory). - init() basic setup - init(blueprint='X') apply a blueprint project_dir: set up .linklore in another folder (creating a boundary is init-only). setting up there doesn't change this session's base project — to keep working there, config(action='pin').

config

Project settings (openbox source options) + iam + session pin. WARNING: handle/name/email apply machine-wide, not per-project. Sharing lives in a separate tool: openbox (openbox sharing/members). 11 actions: - action='whoami' → your identity (handle/name/email) - action='version' → server code version (git commit) - action='sources' → list registered external sources (openboxes) - action='option' → change an external source's settings (auto_search=/show_prefix=) - action='sync' → force-refresh an external source's cache - action='forget' → deregister an external source - action='pin' → pin this session to a specific project - action='unpin' → unpin the session - action='sessions' → list/revoke your account sessions (revoke=) - action='projects' → list every LinkLore project on this machine - action='delete_project' → permanently delete your personal-server copy of this project (returns guidance, no execution — use the forced() command it prints) help=true for details.

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).

Linklore MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "linklore-linklore-mcp": {
      "command": "uvx",
      "args": [
        "llre"
      ]
    }
  }
}

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ]
    }
  }
}

Frequently Asked Questions

Linklore MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Moxie Docs MCP belongs to Knowledge & Memory using local stdio subprocess. Select Linklore MCP when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.

More alternatives to Linklore MCP More alternatives to Moxie Docs MCP Knowledge & Memory category hub