What is the key difference between Pindoc and CP Memory?

Pindoc belongs to the Knowledge & Memory category with local stdio execution, while CP Memory belongs to the Knowledge & Memory category with local stdio execution.

How do I install Pindoc or CP Memory 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 Pindoc and CP Memory free or paid?

Pindoc operates under a Free / Open Source model (No auth required). CP Memory operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Pindoc lists 0 tools with 0 views and 0 GitHub stars. CP Memory lists 0 tools with 0 views and 1 GitHub stars.

Can I use both Pindoc and CP Memory 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

Pindoc vs CP Memory

In-depth architectural comparison of the Pindoc and CP Memory 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

Pindoc

Knowledge & Memory · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

CP Memory

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Pindoc if you need specialized Knowledge & Memory tools running via a local process. Choose CP Memory 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 Pindoc 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).

Explore Pindoc Details

Choose CP Memory 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).

Explore CP Memory Details

Feature & Specification Comparison

Specification	P Pindoc Knowledge & Memory	C CP Memory Knowledge & Memory
Summary	Code-pinned team memory for AI coding agents — typed artifacts, MCP-native, self-host.	Local-first, governable long-term memory for AI coding agents
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Pindoc Tools (0)

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

CP Memory Tools (0)

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

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

Pindoc Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pindoc": {
      "command": "npx",
      "args": [
        "-y",
        "pindoc"
      ]
    }
  }
}

CP Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cp-memory": {
      "command": "uvx",
      "args": [
        "cp-memory-mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Pindoc More alternatives to CP Memory Knowledge & Memory category hub Canonical compare URL