What is the key difference between MCP Assist — Coordination Memory and Moxie Docs MCP?

MCP Assist — Coordination Memory 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 MCP Assist — Coordination Memory 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 MCP Assist — Coordination Memory and Moxie Docs MCP free or paid?

MCP Assist — Coordination Memory 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?

MCP Assist — Coordination Memory lists 0 tools with 0 views and 0 GitHub stars. Moxie Docs MCP lists 12 tools with 17 views and 2 GitHub stars.

Can I use both MCP Assist — Coordination Memory 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.

How do I install MCP Assist — Coordination Memory or Moxie Docs MCP 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 MCP Assist — Coordination Memory and Moxie Docs MCP free to use, or do they require API keys?

MCP Assist — Coordination Memory is listed under a Free / Open Source model with No auth required . Moxie Docs MCP operates under a Freemium model with API Key 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 MCP Assist — Coordination Memory and Moxie Docs MCP at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both mcp-assist-coordination-memory and moxie-docs-mcp 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, MCP Assist — Coordination Memory has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Moxie Docs MCP holds a Quality Score of 82 /100 ( Excellent ) with 17 views, 25 installs, and 2 GitHub stars.

Side-by-Side Model Context Protocol Comparison

MCP Assist — Coordination Memory vs Moxie Docs MCP

In-depth architectural comparison of the MCP Assist — Coordination Memory 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

MCP Assist — Coordination Memory

Knowledge & Memory · Local stdio

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

Moxie Docs MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose MCP Assist — Coordination Memory 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 MCP Assist — Coordination 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 MCP Assist — Coordination Memory 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).
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

Feature & Specification Comparison

Specification	M MCP Assist — Coordination Memory Knowledge & Memory	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory
Summary	Coordination memory with verification: reconcile-against-GitHub, verdict freshness, provenance.	MCP & Agent Skills for Automated Documentation, and codebase conventions + context
Category & Scope

Tools & Capabilities Breakdown

MCP Assist — Coordination Memory 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).

MCP Assist — Coordination Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-assist-coordination-memory": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-assist-coordination-memory"
      ]
    }
  }
}

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"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to MCP Assist — Coordination Memory More alternatives to Moxie Docs MCP Knowledge & Memory category hub