How do I let Cursor or Codex deploy without manual steps?
Give the agent a command it can run without questions, and a place to read the rules. The command is one line with --yes, so nothing waits for a keypress; the rules are an AGENTS.md you download from the portal and put in the root of the repository. Cursor and Codex read that file on their own.
npx github:dorelli-cloud/cli deploy dist --email [email protected] --yesThe first run publishes a trial site for 14 days and writes .dorelli.json in the folder, so every later run updates the same site. Keeping it with your own domain is € 10 a month; an app with a database is € 15.
| Without manual steps | How |
|---|---|
| Publish | the command above, or the deploy_site tool on the MCP server |
| Know the rules | AGENTS.md per site from the portal: address, commands, limits |
| Check the result | npx github:dorelli-cloud/cli status, or site_status on MCP |
| Read logs, submissions, usage | an agent key with only those rights |
| Stay in control | every action lands in an audit log; deploys per day are capped |
For a claimed site you can give the agent its own key with only the rights it needs (publish, read status, read logs) and point it at the site's MCP server:
claude mcp add --transport http dorelli https://mcp.dorelli.cloud/<your-site> --header "Authorization: Bearer <agent key>"Cursor and Codex take the same URL and header in their MCP settings. Everything the agent does is in the audit log in your portal, and on the Website plan an agent may deploy 50 times a day. See Hosting your agent can operate.
Not for
Apps with a database: those are built on GitHub through a workflow, so the agent's job is to push, not to deploy. Not for teams that need one key shared by several agents with different rights; one key has one set of rights.
Checked against the code on 2026-09-22 · Evidence: packages/dorelli/src/cli.ts, lib/agents-md.ts, lib/agent-grenzen.ts, lib/mcp.ts