MCP lets you use Codex or Claude with ZoraForms resources owned by your account: websites, forms, protection, webhooks, integration code, and limits. It can speed up repeatable configuration, but before connecting, decide deliberately which token scope is needed and how the secret will be handled.
Create a token with the smallest useful scope
In the dashboard, open Settings → MCP and create a named token. Choose an expiry that fits the task: a short-lived token for a one-time setup reduces the period in which it could be used. The token is shown only once, so keep it in a trusted secret manager or in the client process’s environment variable.
Configuration access can read and, depending on the selected scope, change your own websites, forms, CAPTCHA, webhooks, and integration code. Reading submissions is a separate permission and is disabled by default. Enable it only when a specific task truly needs submission contents, because they may contain personal data and untrusted text.
- Use a recognizable token name and the shortest practical expiry.
- Enable configuration writes only when the agent must make changes.
- Keep submission reading disabled when it is unnecessary.
- Revoke a token after one-time work is complete.
Connect a client without exposing the secret
Current instructions for Codex and Claude Code are in Settings → MCP and the public /docs/mcp guide. Copy the configuration prepared for your domain and provide the token through an environment variable, not a repository, configuration file, or command history. The server address ends in /mcp and production requires public HTTPS.
Do not give an agent your ZoraForms account password. An MCP token is separate, limited Bearer authentication that can be revoked without changing the password. Restart the client after changing an environment variable so it inherits the new value. Never paste the token into a prompt, submission, or website code.
Plan requests and approve changes
Start with a read-only request, such as checking available limits and listing forms. Then ask for a precise change: create a form for a named domain, set an allowed origin, or generate HTML integration code with UTM. State the names and domains it should use, then verify the result in the dashboard.
Some operations change configuration, and deleting a website or form is destructive. MCP respects resource ownership, account status, and current limits, but tool approval remains the client’s decision. Treat a change preview as a configuration review: check the domain, form, origin, and CAPTCHA mode before approving it.
MCP does not provide access to administration, billing, passwords, profiles, or CAPTCHA secret readback. If you suspect token exposure, revoke it in the dashboard and create a narrower replacement. Find client-specific steps at /docs/mcp rather than copying arbitrary commands from the internet.