Beta application
AI Deploy is in closed beta (until Q3 2026). New users are asked to send a short message via the contact form — we do not issue tokens without prior contact, so that we can deliberately manage infrastructure limits and help out if any problems arise.
→ Fill in the contact form (subject ai-deploy-beta is pre-selected — the form will prompt you for the information we need).
Direct contact: ai-deploy@….
Sandbox activation
After your application, an mDiv admin sets the flag ai_deploy: sandbox on your account. Sandbox is read-only — the agent can list resources (list_my_websites, list_my_domains, list_my_databases, list_packages), but cannot modify anything.
Activation typically takes one business day. In the meantime, it's a good idea to prepare the MCP client (step 4).
Choosing the authentication method
Option A — OAuth 2.1 + PKCE (recommended for per-user agents)
The MCP client registers via Dynamic Client Registration (RFC 7591) at https://moje.mdiv.pl/api/oauth/register, opens https://moje.mdiv.pl/oauth/authorize in the browser, the user approves the scope set, and the agent receives an access token.
PKCE is required (S256 only, plain is rejected). Discovery: https://moje.mdiv.pl/.well-known/oauth-authorization-server.
Option B — Personal API Token
Go to https://moje.mdiv.pl/account/api-tokens, click "Issue token", select scopes. The token in the format mpt_<64hex> is shown only once — copy and store it securely. Usage:
Authorization: Bearer mpt_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
MCP client configuration
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"mdiv": {
"type": "streamable-http",
"url": "https://mcp.mdiv.pl/api/mcp"
}
}
}Cursor (Settings → Features → MCP): add an entry with the same url. Continue.dev: in the configuration ~/.continue/config.json the mcpServers section with analogous content.
After starting the client, run tools/list — it should return 26 tools. If nothing appears, check the client logs — in 99% of cases the cause is a typo in the endpoint or an inactive token.
First call
In the agent's chat window: "Show my websites on the mDiv account". The agent will run list_my_websites() and show a table. If you see correct data, the connection works.
Next steps in the sandbox: list_my_domains, list_my_databases, list_my_mailboxes, list_packages, list_jobs. All are safe — they don't change anything.
Promotion from sandbox to beta
After 1–2 weeks of testing in the sandbox, write to ai-deploy@… or via the form:
- which operations you want to perform (write/install/delete),
- what scale of traffic you expect,
- whether you need a higher limit than 500 ops/day (full).
After promotion, tokens start accepting install_wordpress, request_ssl, set_dns_records, two-step delete_domain etc. Limit 500/day (beta) or no limit (full, included in mBiznes/mPro plans after launch).