Using the PankoBlitz MCP server: every tool explained

What the PankoBlitz MCP server does

The PankoBlitz MCP server lets an agent build and publish a landing page without you touching a dashboard. It is nine tools over one HTTP endpoint, and every action your agent takes maps to a named tool with typed arguments. No screen scraping, no browser automation, no clicking through a builder UI.

The PankoBlitz MCP server exposes nine tools over Streamable HTTP at POST https://api.pankoblitz.com/mcp. Any MCP client (Claude Code, Cursor, or your own) authenticates with a Bearer API key, then calls tools to list organizations, create and edit sites, set a panko.page subdomain, publish, and list templates. The core sequence is create-site, set-subdomain, publish-site. A site stays a private draft until you publish it.

Connect and authenticate

Install it in Claude Code with one command:

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

Authentication is a Bearer header carrying an API key that starts with pk_. Set it as the Authorization header for the transport when you add the server. Minting an API key requires a verified email, so verify your address before you expect any call to succeed.

The nine tools

Tool	Required arguments	What it does
list-orgs	none	Lists your organizations and returns their org ids.
create-org	name, slug	Creates an organization.
list-sites	org_id	Lists sites in an org.
create-site	org_id, slug, title	Creates a draft site. Optional: description, theme, primary_color, content, block_order.
update-site	org_id, site_id	Edits a site. Optional: title, description, theme, primary_color, content, block_order.
publish-site	org_id, site_id	Makes a site live.
set-subdomain	org_id, site_id, subdomain	Sets the panko.page subdomain.
delete-site	org_id, site_id	Deletes a site.
list-templates	org_id	Lists available templates.

How content is shaped

Two arguments control the page body. content is a block map keyed by block id, and block_order is the array that decides render order. A minimal example:

"content": {
  "hero:0": { "headline": "Ship faster" },
  "features:0": [ { "title": "Fast" }, { "title": "Typed" } ]
},
"block_order": ["hero:0", "features:0", "cta:0"]

Pass both to create-site to seed a page, or to update-site to rewrite one. The block ids in block_order must exist in content.

A full sequence

Building a live page from nothing looks like this:

1. list-orgs to get an org_id, or create-org with a name and slug if you have none.
2. create-site with that org_id, a unique slug, a title, and optionally content, block_order, and theme. This returns a site_id.
3. set-subdomain with the org_id, site_id, and the subdomain you want on panko.page.
4. publish-site with the org_id and site_id. The page goes live.

Iterate afterward with update-site, then publish-site again to push the changes.

Errors you will hit

• Unverified email. Publishing a site and creating API keys both require a verified email. Until you verify, those calls fail.
• Duplicate slug. A site slug must be unique within its org. Reusing one is rejected, so pick per-org unique slugs.

Honest limits

The MCP surface covers the create-to-publish path and site management, and nothing more. Custom domains are not set through these tools. There is no separate reordering tool: order is whatever you pass in block_order at create or update time. Draft sites are private, so a page you never publish stays invisible no matter how complete it looks.

Next: open the interactive API docs to see live request and response shapes for each tool, or read the REST API guide to drive the same endpoints with curl.