First Deploy

This walkthrough takes you from zero to a live waitlist page with form capture in under a minute.

Prerequisites

• Invoker MCP server installed (Installation)
• A Claude Desktop or Claude Code session with Invoker available

Step 1: Ask Claude to deploy

Open Claude and type:

"Deploy a waitlist page for my app called Acme"

That is it. One sentence.

Step 2: Claude builds and deploys

Behind the scenes, Claude will:

1. Sign you in (first time only) -- calls login, opens your browser for email OTP verification
2. Grab a template -- calls use_template to fetch the waitlist template HTML
3. Customize it -- rewrites the copy, colors, and branding to match "Acme"
4. Deploy it -- calls deploy with the final HTML and the slug acme

You will see each step happen in the conversation. After a few seconds, Claude responds with something like:

Your waitlist page is live at:
https://acme.invoker.page

It includes an email signup form. All submissions
will be captured automatically.

Choosing your subdomain

The slug you get (e.g., acme) becomes part of the URL: acme.invoker.page. Claude picks a slug based on your prompt, but you can be specific: "Deploy it at cool-product.invoker.page".

Step 3: Share your URL

Open https://acme.invoker.page in your browser. You will see a fully styled waitlist page with a working email signup form. Share the link anywhere -- social media, email, Slack -- and start collecting signups immediately.

Every form submission hits the endpoint that Invoker injects at deploy time. No backend code, no database setup, no infrastructure to manage.

Step 4: Check your submissions

After people start signing up, ask Claude:

"Show me the submissions for my Acme waitlist"

Claude calls get_submissions and returns the data:

You have 12 submissions for acme.invoker.page:

 #  | Email                  | Submitted
----|------------------------|-------------------
 1  | alice@example.com      | 2025-01-15 09:23
 2  | bob@company.co         | 2025-01-15 10:41
 3  | carol@startup.io       | 2025-01-15 11:05
 ...

You can also ask Claude to export the data, filter by date, or check the total count.

Step 5: Update or tear down

Need to change something? Just tell Claude:

"Update my Acme waitlist -- change the headline to 'Join the revolution'"

Claude calls update with the new HTML, and the same URL reflects the changes instantly.

When you are done:

"Take down the Acme waitlist page"

Claude calls teardown and the URL stops serving.

What just happened

Here is the full sequence of MCP tool calls Claude made on your behalf:

Step	Tool	Purpose
1	login	Authenticated via browser (first time only)
2	use_template	Fetched the waitlist template
3	deploy	Published HTML to acme.invoker.page
4	get_submissions	Retrieved form submissions
5	update	Updated the live page
6	teardown	Removed the deployment

You never wrote a line of code, configured a server, or set up a database. Claude handled everything through natural language.

Going further

• Using Templates -- explore all available templates
• Custom Sites -- deploy any HTML, not just templates
• Form Submissions -- webhooks, email notifications, and exports
• MCP Tools Reference -- full documentation for every tool