What is the key difference between RE Call MCP Memory Server and Moxie Docs MCP?

RE Call MCP Memory Server 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 RE Call MCP Memory Server 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 RE Call MCP Memory Server and Moxie Docs MCP free or paid?

RE Call MCP Memory Server 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?

RE Call MCP Memory Server lists 0 tools with 1 views and 5 GitHub stars. Moxie Docs MCP lists 12 tools with 31 views and 2 GitHub stars.

Can I use both RE Call MCP Memory Server 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

RE Call MCP Memory Server vs Moxie Docs MCP

In-depth architectural comparison of the RE Call MCP Memory Server 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

RE Call MCP Memory Server

Knowledge & Memory · Local stdio

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose RE Call MCP Memory Server 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 RE Call MCP Memory Server 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 RE Call MCP Memory Server 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	RE Call MCP Memory Server Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	Trustworthy Postgres plus pgvector memory for AI agents.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope

Tools & Capabilities Breakdown

RE Call MCP Memory Server Tools (0)

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

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.

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

RE Call MCP Memory Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "re-call-mcp-memory-server": {
      "command": "npx",
      "args": [
        "-y",
        "re-call-mcp-memory-server"
      ]
    }
  }
}

Moxie Docs MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

RE Call MCP Memory Server 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 RE Call MCP Memory Server when you need capabilities focused on knowledge & memory and Moxie Docs MCP when you require tools for knowledge & memory.

More alternatives to RE Call MCP Memory Server More alternatives to Moxie Docs MCP Knowledge & Memory category hub Canonical compare URL