NOW LIVE Core dna MCP

How to build a website with

Claude

inside enterprise guardrails

Anyone can vibe-code a site with Claude now. The hard part was never building it. It's running it securely, across every property, without a developer in the loop for every change. Here's how to do both.

Live · Agentic Operations One prompt · every property
MCP tools · APIs
80+ / 400+
▲ built in 15 min, one chat 22 modules, agent-addressable

SEE IT IN ACTION

Watch Claude run a real multi-property job

A short demo of the Core dna MCP translating and localising a site across every property, all from one prompt.

Onboarding illustration

No technical skills. No onboarding.

If you can describe what you want, you can build and run your site. No CMS to learn, no manuals, no waiting on a developer. Your whole team is productive from day one, in plain English.

  • No CMS to learn: describe the change, Claude makes it
  • No dev tickets: the person who wants it, does it
  • Productive on day one, not week three
  • Anyone on the team can do it, safely
PART 1 · THE CORE DNA WAY

Building with Claude on Core dna, step by step

Connect Claude to Core dna
01

Connect Claude to Core dna

Add Core dna as a custom connector in Claude, sign in with your existing login, and approve. Now Claude can act inside your real platform, not just talk about it. This is the unlock.

Describe what you want
02

Describe what you want

Tell Claude in plain English what you want: a new landing page, a campaign, a price change across every location. No code, no dev ticket.

Within your guardrails and permissions
03

Within your guardrails and permissions

Claude only acts inside your roles and permissions. It can touch what your account can touch, scoped to your brands, regions, and content, and nothing more. Powerful, but never off-leash.

Preview and approve
04

Preview and approve

Every change lands as a draft revision on your real site. Preview it, run it through your approval workflow, and diff or roll back before anything goes live.

Publish across every property
05

Publish across every property

Promote it live when you're ready: one property or all of them at once, with full version history and an audit trail behind every change.

You don't need to learn prompting

Claude already understands how your Core dna site is built: your components, your content model, your pages and how they connect. So you don't have to be precise or spell everything out. Say what you want in plain words and it fills in the structure for you. No special syntax, no prompt engineering, no learning curve.

Five things to start with

  • "Add an FAQ page"
  • "Make the homepage hero punchier"
  • "Add a testimonials section to the About page"
  • "Spin up a landing page for our next promo"
  • "Find and fix pages missing a meta description"

Vibe coding, for enterprise

All the speed of describing what you want in plain English, with the permission controls a real business needs. You decide, per action and per role, what an agent can do on its own, what it has to ask about first, and what it can never touch.

  • Per-action control: allow, ask, or deny every tool the agent can use
  • Your Core dna roles: the agent inherits the exact permissions of whoever is signed in
  • Approval before publish: nothing goes live without human sign-off
  • Full audit trail: every prompt, change, and approval logged
Permissions illustration
FAQ

Questions people ask about building with Claude

No. Add Core dna as a connector in Claude, sign in with your existing login, and approve. No code, no config files, no IT ticket. If you can describe what you want, you can build it.

Want the exact steps? See the full setup guide.

Read the full answer →

Yes. Claude acts inside your roles and permissions, every change lands as a draft for approval, and everything is versioned and logged. You can preview, diff, and roll back before anything goes live.

Read the full answer →

Always. Changes land as drafts on your real Core dna site, so you can fine-tune them in the editor, ask for more changes, or roll back, all before publishing.

Read the full answer →

Not for everyday work. The person who wants a change makes it by describing it. Developers get their time back for what genuinely needs engineering.

Read the full answer →

Yes. Once connected, Claude can update pages, refresh content, fix SEO, and manage your existing Core dna site through conversation.

Read the full answer →

The same Core dna MCP works with Claude, ChatGPT, Gemini, Copilot, and Cursor. Connect whichever your team already uses.

Read the full answer →

PROOF, NOT PROMISE THIS PAGE BUILT ITSELF

Every section of this page was built with Claude

The structure, the copy, the layout, the components: all of it built with Claude, in one conversation, inside these exact guardrails. Nothing here was hand-coded. If this page was built with Claude, yours can be too.

Core dna MCP · live now

Stop building sites by hand.

The speed of describing what you want, with the permissions, approvals, version history, and audit trail that make it safe to actually turn on. Building was never the bottleneck; running the site safely was.

Live · Agentic Operations Every property, one prompt
Guardrails · built in
4 / 4
▲ security · approval · revisions · audit OAuth 2.1 · tenant-scoped · revocable