Business vs Moxie Docs MCP — MCP Server Comparison | AllMCPs
Business vs Moxie Docs MCP
A side-by-side look at the Business 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.
Verdict: choose Business for developer tools work over a hosted endpoint; choose Moxie Docs MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Business when
You need dedicated capabilities in the Developer Tools domain.
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_update
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.
Business is categorized under Developer Tools and uses a remote HTTP/SSE transport. Moxie Docs MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Business for developer tools 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.
Business has no declared pricing — check the project's own site. Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. 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 business and moxie-docs-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Business has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Moxie Docs MCP has 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars.