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

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

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

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

Which MCP server has more tools and community activity?

Moxie Docs MCP lists 12 tools with 17 views and 2 GitHub stars. Projectmem lists 6 tools with 2 views and 538 GitHub stars.

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

How do I install Moxie Docs MCP or Projectmem in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Moxie Docs MCP and Projectmem free to use, or do they require API keys?

Moxie Docs MCP is listed under a Freemium model with API Key required . Projectmem operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Moxie Docs MCP and Projectmem at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both moxie-docs-mcp and riponcm-projectmem as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Moxie Docs MCP has a Quality Score of 82 /100 ( Excellent ) with 17 views, 25 installs, and 2 GitHub stars. Projectmem holds a Quality Score of 47 /100 ( Fair ) with 2 views, 0 installs, and 538 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Moxie Docs MCP vs Projectmem

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

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

Projectmem

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Moxie Docs MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Projectmem 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 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).
You have access to required keys: MOXIE_TOKEN.
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Choose Projectmem 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: Local-first memory stored in .projectmem directory, Typed event storage: issues, attempts, fixes, decisions, notes, Pre-commit git hook warnings for repeated mistakes.

Feature & Specification Comparison

Specification	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory	Projectmem riponcm Knowledge & Memory
Summary	MCP & Agent Skills for Automated Documentation, and codebase conventions + context	Local-first memory and judgment layer for AI coding agents. Captures issues, failed attempts, fixes, and decisions in readable Markdown + JSONL, re-injects them into future sessions, and warns at git commit before you repeat a mistake. 14 tools, works with Claude, Cursor, Antigravity, and Codex.
Category & Scope

Tools & Capabilities Breakdown

Moxie Docs MCP Tools (12)

moxie.get_ai_context

Compact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.

moxie.get_doc_impact

Given the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.

moxie.get_api_context

Given paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.

moxie.review_change

Self-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.

moxie.get_conventions

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

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Projectmem Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

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