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

Moxie Docs MCP belongs to the Knowledge & Memory category with local stdio execution, while Ragstack belongs to the end to end RAG platforms category with local stdio execution.

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

Moxie Docs MCP operates under a Freemium model (API Key required). Ragstack 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 31 views and 2 GitHub stars. Ragstack lists 0 tools with 0 views and 25 GitHub stars.

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

Moxie Docs MCP vs Ragstack

In-depth architectural comparison of the Moxie Docs MCP and Ragstack 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: 80/100 (Excellent) | Auth: API Key required

Ragstack

end to end RAG platforms · 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 Ragstack if your workspace requires end to end RAG platforms 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).
Primary tools included: moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.

Explore Moxie Docs MCP Details

Choose Ragstack when:

You need dedicated capabilities in the end to end RAG platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Ragstack Details

Feature & Specification Comparison

Specification	Moxie Docs MCP FeaturedVerifiedKnowledge & Memory	Ragstack end to end RAG platforms
Summary	MCP & Agent Skills for Automated Documentation, and codebase conventions + context	Search, chat, upload, and scrape a serverless RAGStack knowledge base on AWS.
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

Discovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.

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

Ragstack Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

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