Zactonz vs Chatpack MCP
A side-by-side look at the Zactonz and Chatpack MCP 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 requiredC
Chatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.86ExcellentAuth: no auth requiredVerdict: choose Zactonz for developer tools work as a local process; choose Chatpack MCP 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?
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.
CChoose Chatpack MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_document, get_integration_guide.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Z Zactonz | C Chatpack MCP |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 86/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | ZACTONZ_API_KEYS | None listed |
| Verified owner | Community listing |
Tools & capabilities
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
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.
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.
Zactonz
{
"mcpServers": {
"zactonz": {
"command": "npx",
"args": [
"-y",
"@zactonz/mcp"
],
"env": {
"ZACTONZ_API_KEYS": "YOUR_ZACTONZ_API_KEYS_HERE"
}
}
}
}
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/mcp"
]
}
}
}
Frequently asked questions
Zactonz is categorized under Developer Tools and uses a local stdio subprocess. Chatpack MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Zactonz for developer tools work and Chatpack MCP 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.
Zactonz is listed as freemium — a free tier with paid plans. Auth: api key required. Chatpack MCP is listed as free. Auth: no auth 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 zactonz and chatpack-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Zactonz has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Chatpack MCP has 86/100 (Excellent) with 2 views, 0 installs and 224 GitHub stars.
