Moxie Docs MCP vs ResumeQuick

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

Moxie Docs MCP logoMoxie Docs MCPKnowledge & Memory · Local subprocess (stdio)MCP & Agent Skills for Automated Documentation, and codebase conventions + context81ExcellentAuth: oauth 2.0Featured
R
ResumeQuickKnowledge & Memory · Remote HTTP/SSE
Career assistant: resumes, job-match analysis, interview results and career memory.39FairAuth: oauth 2.0

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

Which MCP server should you choose?

Moxie Docs MCP logoChoose Moxie Docs MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • 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

R
Choose ResumeQuick when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore ResumeQuick

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMoxie Docs MCP logoMoxie Docs MCP
R
ResumeQuick
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal81/100 · Excellent39/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthOAuth 2.0OAuth 2.0
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified owner VerifiedCommunity listing
GitHub stars2—
Directory activity 45 views 25 installs 4 upvotes 0 views 0 installs 0 upvotes
Tools12Not listed

Tools & capabilities

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.

ResumeQuick tools

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

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.

Moxie Docs MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "moxie-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "moxie-docs"
      ]
    }
  }
}

ResumeQuick

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "resumequick": {
      "command": "npx",
      "args": [
        "-y",
        "resumequick"
      ]
    }
  }
}

Frequently asked questions

Moxie Docs MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. ResumeQuick belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Moxie Docs MCP for knowledge & memory work and ResumeQuick 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 is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. ResumeQuick has no declared pricing — check the project's own site. 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 moxie-docs-mcp and resumequick as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Moxie Docs MCP has a quality signal of 81/100 (Excellent) with 45 views, 25 installs and 2 GitHub stars. ResumeQuick has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.