Moxie Docs MCP vs Zactonz
A side-by-side look at the Moxie Docs MCP and Zactonz MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Z
ZactonzDeveloper Tools · Local subprocess (stdio)Screenshots, page to Markdown, link previews, DNS, SSL, WHOIS, QR codes and more for AI agents.53GoodAuth: api key requiredVerdict: choose Moxie Docs MCP for knowledge & memory work as a local process; choose Zactonz for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
ZChoose Zactonz when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ZACTONZ_API_KEYS. - You want tools like
capture_screenshot, render_html, read_webpage.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Z Zactonz | |
|---|---|---|
| Category | Knowledge & Memory | Developer Tools |
| Quality signal | 80/100 · Excellent | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Freemium | Freemium |
| Required env vars | None listed | ZACTONZ_API_KEYS |
| Verified owner | Verified | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 36 views 25 installs 4 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 19 |
| Full listing | View Moxie Docs MCP | View Zactonz |
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-tracked doc your change makes obsolete; returns the path to delete in your branch.
Zactonz tools 19
capture_screenshotCapture a web page as an image or PDFrender_htmlRender HTML to an image or PDFread_webpageRead a web page as Markdownconvert_html_to_markdownConvert HTML to Markdownpreview_linkTitle, description, image and metadata of a URLlookup_dnsDNS records and DNSSEC statusinspect_ssl_certificateCertificate, chain, expiry and TLS detailslookup_whoisRegistrar, dates and nameservers of a domaincheck_email_domainMX, SPF, DKIM, DMARC and related records, scoredverify_emailsWhether addresses can receive mailgenerate_qr_codeGenerate a QR coderead_qr_codeDecode a QR code- +7 more on 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": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
Zactonz
{
"mcpServers": {
"zactonz": {
"command": "npx",
"args": [
"-y",
"@zactonz/mcp"
],
"env": {
"ZACTONZ_API_KEYS": "YOUR_ZACTONZ_API_KEYS_HERE"
}
}
}
}
Frequently asked questions
Moxie Docs MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Zactonz belongs to Developer Tools and uses a local stdio subprocess. Pick Moxie Docs MCP for knowledge & memory work and Zactonz for developer tools.
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: api key required. Zactonz 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 moxie-docs-mcp and zactonz 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 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars. Zactonz has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.