AI

// ai

This is not an AI website builder.

It is a CMS with guardrails, built so you can point your favourite AI assistant at your site and trust what comes back. Bring Claude Code, Codex, Claude Desktop, or anything else that speaks MCP. BlockNinja gives the AI room to work and a fence it cannot cross, so everything it ships still uses your blocks, your design, and your content rules. You get the speed of AI without the generic site it usually leaves behind.

1

Bring the assistant you already use

Claude Code in the terminal, Codex in your editor, Claude Desktop open beside your work. BlockNinja speaks MCP, so it connects to all of them. Nothing new to learn, and no walled-garden chatbot to babysit.

2

Your design sets the limits

The AI cannot invent a layout or reach for an off-brand colour. It works from the blocks, theme tokens, and templates you already approved, so every page it touches looks like it belongs on your site.

3

It works like a real admin

Every action runs through the same engine your editors use: create a page, publish a post, reorder a menu, resize an image. The same permissions and validation apply each time, so nothing sneaks in through a side door.

4

You keep the final say

One API key decides what the AI can reach, from a single section to the whole site. Every change is logged and reversible, and you review it in the editor before it goes live. The AI does the work; the decision to publish stays yours.

// in practice

Watch it build a page.

It plans with a checklist, calls your CMS tools over MCP one at a time, and builds the page from blocks you already approved.

claude — ~/sites/banana.phone

$claude mcp add --transport http blockninja_banana_phone "https://banana.phone/.mcp-server"

Added HTTP MCP server blockninja_banana_phone → https://banana.phone/.mcp-server (project)

$claude

▐▛███▜▌Claude Code v2.1.195

▝▜█████▛▘Fable 7 (1M context) with high effort · Claude Max

▘▘ ▝▝~/sites/banana.phone

⚠3 MCP servers need authentication · run /mcp

❯read @plans.md and build out BananaPhone's new pricing page

⏺I'll read the plan, then build it from your approved blocks and theme tokens.

⏺Update Todos

⎿☒Load theme tokens and block library

☒Create the /pricing page

☒Add hero, pricing-table, faq

☐Publish after review

⏺First, let me see what I'm working with.

⏺blockninja_banana_phone - get_theme (MCP)()

⎿tokens loaded · colour, type, spacing (locked to your design system)

⏺blockninja_banana_phone - list_blocks (MCP)()

⎿24 approved blocks · hero, pricing-table, faq, feature-grid …

⏺Now I'll create the page and drop in the blocks.

⏺blockninja_banana_phone - create_page (MCP)(title: "Pricing", slug: "/pricing")

⎿draft created · /pricing

⏺blockninja_banana_phone - add_block (MCP)(page: "/pricing", block: "hero")

⎿added hero · "Plans for every banana"

⏺blockninja_banana_phone - add_block (MCP)(block: "pricing-table", tiers: 3)

⎿added pricing-table · 3 tiers, your tokens

⏺blockninja_banana_phone - add_block (MCP)(block: "faq")

⎿added faq · 6 questions

⏺/pricing is saved as a draft, built only from your blocks and tokens.

⏺Want me to publish it?

❯yes, publish it

⏺blockninja_banana_phone - publish_page (MCP)(slug: "/pricing")

⎿published · live at banana.phone/pricing

⏺Done. On brand, on grid.

✻Thinking(0s · ↓ 0 tokens · thinking with high effort · esc to interrupt)

❯

⏵⏵ bypass permissions on (shift+tab to cycle) · ⌥ for agents

Every tool call stays inside

Your blocks It assembles from the block library you approved. Nothing hand-rolled, nothing off-system.
Your theme Colour, type, and spacing come straight from your tokens, so every page lands on brand.
Real permissions Scoped to exactly the tools you grant, and logged like any other admin action.
Your review Work lands as a draft first. Nothing goes live until you say publish.