Zactonz MCP Server

The Zactonz MCP Server is a Model Context Protocol server for the Zactonz APIs. Connect it to an MCP client such as Claude Desktop, Claude Code, Cursor, Windsurf or VS Code, and the assistant can capture a screenshot of a web page, read a page as Markdown, preview a link, look up DNS, SSL and WHOIS records, check a domain's email setup, verify addresses, generate QR codes, barcodes and social card images, convert images and translate text.

It runs on your machine over stdio and needs Node.js 18 or newer. Keys stay in the server process and are sent to api.zactonz.com and nowhere else.

What the assistant can do#

Once connected, requests like these work as you would expect:

• "Take a screenshot of example.com on a 390 pixel wide screen and tell me whether the menu fits."
• "Read https://example.com/pricing and summarise the plans."
• "Does example.com have SPF and DMARC set up correctly?"
• "When does the SSL certificate for example.com expire?"
• "Make a QR code for our contact page."

How it fits together#

• Eighteen tools, one per API operation, named for what they do: capture_screenshot, read_webpage, lookup_dns, generate_qr_code and so on, plus check_api_key for plan and quota. The Tools tab lists them all.
• Generated from the API specifications that also produce this portal's reference pages, so argument names and descriptions match the API.
• Only the tools you have keys for are offered. A Zactonz key works for one product, and the server reads the product from the key, so an assistant never sees a tool it cannot call.
• Arguments are validated against each tool's schema before any request leaves the machine.
• Images come back inline when they are small enough for the assistant to look at, and as a link otherwise.
• Cancellation is honoured, and a call never outlives the client's own timeout.

Requirements#

Node.js 18 or newer, an MCP client that speaks stdio, and one or more API keys from the console. There is a free plan.

Versioning#

The package follows semantic versioning. While it is at 0.x, a minor release may rename a tool or an argument; such changes are listed in the changelog. The server is listed in the official MCP Registry as io.github.zactonz/zactonz-mcp, so clients that browse the registry can add it from there.