Claude Code
Build, push and deploy from your terminal-based agent, then let it roll back if a release goes wrong.
AI & MCP
Zinn Digital® exposes your hosting as a single MCP server, so your preferred AI agent can manage, build and deploy sites in plain language. Connect Claude Code, Cursor, ChatGPT or Claude Desktop once, and every capability we ship becomes available to it automatically.
MCP (the Model Context Protocol) is the open standard for connecting AI agents to real systems. We support the protocol, not each app, so you connect the tool you already use and control hosting conversationally.
Build, push and deploy from your terminal-based agent, then let it roll back if a release goes wrong.
Drive staging clones, cache purges and wp-cli commands from your editor without leaving your flow.
Ask for site status, run audits and trigger guarded actions from any MCP-capable ChatGPT client.
Diagnose a site, prepare a migration or check billing usage in natural language, from the desktop app.
The MCP server is a thin adapter over our engine API, so it reuses the same action catalog, RBAC and audit trail. It exposes three things.
Actions the AI can invoke — the same API endpoints behind the dashboard, with no separate logic to drift out of sync.
Read-only context — site health, config, recent logs, metrics, uptime and KB articles — so the agent reasons with real data before it acts.
Reusable workflow templates we publish, such as "diagnose this site" or "prepare a migration", so common jobs are one instruction.
Every tool is gated by the connected identity's scopes. A sample of what your agent can do:
Because the MCP server rides the same API, everything new we add to the platform becomes available over MCP automatically — you are never waiting on a per-tool integration.
An agent with access to production needs guardrails that are designed in, not bolted on. Ours are:
Your AI client authorises against your org; every session is bound to your user and permissions, with Postgres row-level security enforced.
Tokens are scoped and revocable per tool, with sandbox and production kept separate, so you grant only what each agent needs.
Delete, suspend, billing and large-spend actions require explicit confirmation or a human-approval policy before they run.
Rate limits and spend caps bound AI-triggered paid actions, and every MCP action — identity, tool, arguments, result — is audit-logged.
Any MCP-capable client. We publish one-click and paste config snippets for Claude Code, Cursor, ChatGPT and Claude Desktop, and because we support the protocol rather than each app, new MCP tools work too.
In your dashboard, choose "Connect AI tool" to generate an MCP endpoint — a URL plus OAuth — then paste the config into your agent. Tokens are scoped, per-tool and revocable, with separate sandbox and production access.
No. An agent can only do what the connected identity is permitted to do, and destructive actions — delete, suspend, billing or large spend — require explicit confirmation or a human-approval policy. Spend caps and a full audit log bound the rest.
Yes. Through MCP Resources it can read site health, config, recent logs, metrics, uptime and KB articles, so it diagnoses with real context before taking any action.
You can start on a card-free 7-day trial, and every plan carries a 30-day money-back guarantee, free migrations and no vendor lock-in.
Connect the AI tool you already use to hosting built for scale, with scoped access and a full audit trail. Start on a card-free 7-day trial.
Start free