Publish a landing page from Claude Code

Most tools that call themselves "AI-native" mean a chat box bolted onto a dashboard. PankoBlitz means your agent never opens a browser. You stay in Claude Code, describe the page, and the agent builds and ships it to a live URL. This guide is the exact end-to-end flow, with the real tool calls and the real timing from a run I did.

Direct answer: Connect Claude Code to the PankoBlitz MCP server with one command, authenticate with your API key, then describe the page in plain language. The agent calls list-orgs, create-site, set-subdomain, and publish-site in sequence. The page goes live at your-subdomain.panko.page on publish. In a real run, the create-to-publish step took about a second. You never leave the terminal.

What you need

• A PankoBlitz account with a verified email. Publishing is blocked until your email is verified. Start free.
• An API key created in the dashboard. It carries the pk_ prefix.
• Claude Code installed and working.

Connect the MCP server

One command adds PankoBlitz as an HTTP transport MCP server:

claude mcp add --transport http pankoblitz https://api.pankoblitz.com/mcp

Authenticate with your API key as a Bearer token when prompted. Once connected, Claude Code sees the PankoBlitz tools and can call them directly. For the full list of tools and their parameters, see the MCP tools reference.

Describe the page

Now talk to your agent like you would a colleague. A prompt that works:

Build me a landing page on PankoBlitz. Use the glass theme.
Hero, three feature cards, three testimonials, an FAQ, and a
call to action. Publish it to the subdomain guide-demo.

You do not write any HTML or CSS. The theme handles styling. You specify the blocks and their content, the agent handles the API.

Watch the tool calls

Here is the order the agent runs, and what each call does:

1. list-orgs reads back your organization id, which every following call needs.
2. create-site takes a slug, a title, a theme, and the array of content blocks. This creates a draft.
3. set-subdomain claims guide-demo for the site.
4. publish-site flips the draft to live.

In my run, the create-and-publish step took about a second of wall-clock time.

Your page is live

On publish, the site serves at <subdomain>.panko.page. The glass-theme page I built (hero, three features, three testimonials, FAQ, CTA) went live at https://guide-demo.panko.page. Open it in a browser to confirm, or just trust the publish-site response, which returns the URL.

Limits

Worth knowing before you build:

• Drafts are private. A site created but not published is not reachable by anyone. Nothing is public until publish-site runs. This is a feature: you can build and revise without exposing a half-finished page.
• The free tier allows three sites. Past that you hit a cap and the agent gets an error back on create-site.
• Custom domains are a separate step and need the Pro tier. The free flow gets you a panko.page subdomain. Pointing your own domain at the site is not part of this flow and is not free.
• Your email must be verified first. If it is not, publish-site fails even though create-site succeeded, so you can end up with a draft you cannot ship.

Next step

Run the claude mcp add command above, then ask your agent to build a one-block hero page and publish it to a test subdomain. That single round trip tells you the connection and your API key both work. When you want the request and response shape behind each tool, read the API docs.