Atlaso Labs MCP vs Moxie Docs MCP

A side-by-side look at the Atlaso Labs MCP and Moxie Docs MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Atlaso Labs MCP logoAtlaso Labs MCPKnowledge & Memory · Remote HTTP/SSEAI memory layer — one shared, persistent memory across every AI tool you connect.37FairAuth: not declaredMoxie Docs MCP logoMoxie Docs MCPKnowledge & MemoryMCP & Agent Skills for Automated Documentation, and codebase conventions + context76GreatAuth: oauth 2.0Featured

Verdict: choose Atlaso Labs MCP for knowledge & memory work over a hosted endpoint; choose Moxie Docs MCP for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Atlaso Labs MCP logoChoose Atlaso Labs MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
Explore Atlaso Labs MCP

Moxie Docs MCP logoChoose Moxie Docs MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
Explore Moxie Docs MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAtlaso Labs MCP logoAtlaso Labs MCPMoxie Docs MCP logoMoxie Docs MCP
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal37/100 · Fair76/100 · Great
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthNot declaredOAuth 2.0
PricingNot declaredFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars02
Directory activity 0 views 0 installs 0 upvotes 44 views 25 installs 4 upvotes
ToolsNot listed12

Tools & capabilities

Atlaso Labs MCP tools

No tool names declared yet. Check the project README from the listing page.

Moxie Docs MCP tools 12

  • moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.
  • moxie.get_doc_impactGiven 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_contextGiven 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_changeSelf-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_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.
  • moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.
  • moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.
  • moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.
  • moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).
  • moxie.list_docsPaginated, section-grouped table of contents of every generated doc.
  • moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.
  • moxie.propose_doc_removalRemove a Moxie Docs-tracked doc your change makes obsolete; returns the path to delete in your branch.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Atlaso Labs MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-3": {
      "url": "https://mcp.atlaso.ai/mcp"
    }
  }
}

Moxie Docs MCP

No confirmed install command for Moxie Docs MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Atlaso Labs MCP is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Moxie Docs MCP belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Atlaso Labs MCP for knowledge & memory work and Moxie Docs MCP for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Moxie Docs MCP has no confirmed install command yet — follow its own setup instructions.

Atlaso Labs MCP has no declared pricing — check the project's own site. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-3 and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Atlaso Labs MCP has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Moxie Docs MCP has 76/100 (Great) with 44 views, 25 installs and 2 GitHub stars.