diff --git a/quickstart.mdx b/quickstart.mdx
index 4fc7601ca..5c3860f8b 100644
--- a/quickstart.mdx
+++ b/quickstart.mdx
@@ -5,23 +5,25 @@ keywords: ["quickstart", "deploy", "get started", "first steps", "tutorial", "se
 boost: 3
 ---
 
-import SkillMcpPrompt from "/snippets/skill-mcp-prompt.mdx";
+import SetupAgentPrompt from "/snippets/setup-agent-prompt.mdx";
 
 After you complete this guide, you'll have a live documentation site ready to customize and update.
 
-## Before you begin
+<Tip>
+  Using an AI agent?
 
-Mintlify uses a docs-as-code approach to manage your documentation. Every page on your site has a corresponding file stored in your documentation <Tooltip tip="Your documentation's source code where all files and their history are stored. The web editor connects to your documentation repository to access and modify content, or you can edit files locally in your preferred IDE.">repository</Tooltip>.
+  Copy the following prompt to have your agent set up your site for you. It directs your agent to create your account and deploy your site. It also adds the Mintlify [skill](/ai/skillmd) and [MCP server](/ai/model-context-protocol) for better results when you update your content.
+  
+  The prompt splits the quickstart into tasks your agent can complete and directs it to ask you for any information it needs while getting everything set up.
+</Tip>
 
-When you connect your documentation repository to your project, you can work on your documentation locally or in the web editor and sync any changes to your remote repository.
+<SetupAgentPrompt />
 
-<Tip>
-  Using an AI coding tool?
+## Before you begin
 
-  Copy the following prompt to add the Mintlify [skill](/ai/skillmd) and [MCP server](/ai/model-context-protocol) for better results when updating your documentation.
-</Tip>
+Mintlify uses a docs-as-code approach to manage your documentation. Every page on your site has a corresponding file stored in your documentation <Tooltip tip="Your documentation's source code where all files and their history are stored. The web editor connects to your documentation repository to access and modify content, or you can edit files locally in your preferred IDE.">repository</Tooltip>.
 
-<SkillMcpPrompt />
+When you connect your documentation repository to your project, you can work on your documentation locally or in the web editor and sync any changes to your remote repository.
 
 ## Deploy your documentation site
 
diff --git a/snippets/setup-agent-prompt.mdx b/snippets/setup-agent-prompt.mdx
new file mode 100644
index 000000000..8cff28564
--- /dev/null
+++ b/snippets/setup-agent-prompt.mdx
@@ -0,0 +1,25 @@
+{/* vale off */}
+
+<Prompt description="Copy and paste to have your agent set up your Mintlify site." actions={["copy", "cursor"]}>
+Get my documentation live on a published Mintlify site. You are successfully done when you give me the live URL and confirm it loads. Tell me clearly whenever a step needs my input—do everything else yourself. If this prompt was pasted before (for example, after a restart), continue from where things left off instead of starting over. If you don't have terminal or command execution access, tell me to follow the manual steps at [mintlify.com/start](https://mintlify.com/start) instead. Everything below requires running commands and requires Node.js v 20.17.0+ (LTS versions recommended).
+
+1. Ask for my existing content that will be used for my Mintlify site. This may be a local folder or a repo. Verify the source before building: echo back exactly what you're reading and list its top-level contents so I can confirm it's right. If you can't access something I named (private repos return 404, same as nonexistent), stop and ask. Never substitute a different source.
+2. Check whether `mint` is installed with `mint --version`. If it's missing, install it with `npm i -g mint` (or `pnpm add -g mint`). If it's already installed, run `mint update` instead of reinstalling.
+3. Run `mint status`. If it already shows an organization, skip to step 7.
+4. Needs me: If `mint status` shows I'm not logged in, ask me directly whether I already have a Mintlify account. Don't guess.
+   - If I have one: run `mint login`. You need me for browser steps and to approve access.
+   - If I don't: ask me for my first name, last name, company, and email if I haven't given them already—never invent these. Run `mint signup --firstName [firstName] --lastName [lastName] --company [company] --email [email]` as a background task since it blocks until I click a verification link that can take several minutes.
+5. Needs me: I'll check my email and click the verification link. That opens a browser tab that automatically finishes the rest of account creation/logging in. I must approve the CLI, then connect a GitHub repository or let Mintlify host one. Tell me clearly this step is mine, then wait for it before continuing.
+6. Run `mint status` again to confirm an organization and subdomain now exist. Provisioning can lag a moment after onboarding finishes — if no subdomain appears yet, wait about 10 seconds and retry a few times before concluding something is wrong.
+7. Needs me: ask for the URL of the repository connected to my Mintlify project — `mint status` doesn't expose it, so you can't look it up yourself. Clone it once I give it to you.
+8. Check what's in that repo. If I connected my own existing docs repo, my content is already there — don't overwrite it. If Mintlify created the repo, it contains starter template content — replace that with my actual docs content from step 1. Only use `mint new [directory]` if I want a different theme or template than what's in the repo — scaffold it locally, then use its output in place of the seeded content.
+9. Preview with `mint dev`, which generally starts on `http://localhost:3000` unless that port is in use. It blocks until stopped, so run it as a background task. Verify the preview loads, then stop it before continuing.
+10. Commit and push your changes. Mintlify deploys automatically on push.
+11. Needs me: If I want a custom domain, run `mint add-domain <domain>`. It prints the DNS records I need to add with my domain provider. Tell me the DNS records, since only I can configure them at my registrar. Make it clear that this is a step I must complete.
+12. Confirm my site is live: fetch `https://<subdomain>.mintlify.site` (find the subdomain via `mint status`) and confirm it loads. If I added a custom domain in step 11, also fetch that domain and confirm it loads before calling this step done-DNS propagation can lag, so retry a few times before treating a failed fetch as an error.
+13. Set yourself up to keep working here: install the [Mintlify skill](https://mintlify.com/docs/ai/skillmd.md) with `npx skills add https://mintlify.com/docs`, then register the [admin MCP server](https://mintlify.com/docs//ai/model-context-protocol.md) at `https://mcp.mintlify.com` for your specific tool. For example, `claude mcp add --transport http mintlify https://mcp.mintlify.com` for Claude Code or fetch https://mintlify.com/docs/ai/mintlify-mcp.md for instructions for Claude, Cursor, Codex, or ChatGPT. Do this step yourself—don't ask me to run these commands.
+14. Needs me: the first admin MCP tool call opens a browser window for OAuth login. Approve it there. Most tools don't load newly added MCP servers mid-session — if the Mintlify tools don't show up, tell me to restart you and we'll pick up from here.
+15. If any command fails in a way not covered above, stop and tell me the exact error rather than guessing or retrying blindly. If it looks like something's wrong on Mintlify's end rather than in what you're doing, check https://status.mintlify.com or point me to https://mintlify.com/docs/contact-support.
+</Prompt>
+
+{/* vale on */}