Claude Code website builder for hosted marketing sites.
Yes, Claude Code can help build a website. Boomlink adds the substance: connect over MCP with your project's .mcp.json, start from a full-stack template with an embedded database, let isolated plugins do the heavy work, and let Claude Code edit the thin frontend. Preview and publish a hosted multi-page site without setting up a separate repo, host, forms, or domain workflow.
Free plan available. Publish on a Boomlink subdomain. No credit card required.
Last updated
{
"mcpServers": {
"boomlink": {
"url": "https://boomlink.agimon.win/api/v1/mcp/0.0.1"
}
}
}What is a Claude Code website builder?
A Claude Code website builder is a workflow where Claude Code calls website-building tools from your project, not just writes files in a repo. With Boomlink connected over MCP, you start from a full-stack template with an embedded database, isolated plugins handle the heavy features, and Claude Code edits the thin frontend and BFF, shows a live preview, and publishes a hosted site. You guide the outcome in plain English, and Boomlink brings the durable substance and site lifecycle.
The short version
- Claude Code is the agentic CLI where you describe the site and edit the thin frontend.
- Boomlink brings the full-stack templates, embedded database, and isolated plugins, and hosts the result.
- The output is a hosted, full-stack site with real data, preview, forms, analytics, and publishing.
Prefer the Claude desktop or chat app instead of the CLI? See the Claude website builder page. To connect any MCP assistant, including Cursor, see the MCP website builder page.
Claude Code can edit the site. Durable substance and shipping are the parts people still stitch together.
Most Claude Code website tutorials stop at generated code or a framework project, and generated code is fragile as the site grows. That path also means owning GitHub, deployment settings, DNS, form handling, analytics, and future updates. It is too much overhead when the job is a launch page, product site, portfolio, docs-style marketing site, or campaign page.
DIY path
scaffold, code, repo, deploy, domain, forms, analytics, maintenance.
Boomlink path
connect MCP, pick a template, add plugins, edit the thin frontend, preview, publish from Claude Code.
Build and publish from the Claude Code loop.
Connect Boomlink in .mcp.json
Add Boomlink as an MCP server for the project so Claude Code can call the site tools from the same working context.
Describe the site
Start from a full-stack template, add plugins for heavier features, and ask for a homepage, product pages, pricing, FAQ, contact form, or campaign page. Claude Code edits the thin frontend while plugins and the template do the work.
Preview, then publish
Review the live preview, request edits, then publish to a Boomlink-hosted URL. Paid plans add custom domains with SSL.
Connect Boomlink to Claude Code with .mcp.json
In Claude Code, add Boomlink to the project's .mcp.json. Use the endpoint from the Boomlink docs or your app configuration.
{
"mcpServers": {
"boomlink": {
"url": "https://boomlink.agimon.win/api/v1/mcp/0.0.1"
}
}
}After Claude Code sees the MCP server, ask it to create or update your Boomlink site. Keep prompts specific: audience, offer, pages, form fields, tone, and what should happen after publishing.
For setup details, read the MCP reference and the publishing guide.
What you get when the site has to be live, not just generated.
Full-stack site with embedded database
Turn the Claude Code session into a public full-stack site with its own embedded database and a public data endpoint, not a folder of files you still have to deploy.
Isolated plugin system
Heavy features come from isolated plugins that avoid the conflicts and security sprawl of a shared runtime, while Claude Code edits only the thin frontend.
Multi-page structure
Real pages, hierarchy, and navigation from a full-stack template, not a single throwaway page.
Live preview before publish
Check the site before visitors see it, then ask Claude Code for edits while the workflow is still fresh.
Forms and submissions
Capture leads from the published site instead of bolting on a form stack after launch.
Basic analytics
See whether the site is being used, then upgrade the tracking setup when the campaign needs more detail.
Custom domain and SSL on paid plans
Start on a Boomlink subdomain, then connect a branded domain when the site is ready for a real campaign or business presence.
Best for marketing sites Claude Code should ship quickly.
Launch page for a new product or feature.
Technical founder website or portfolio.
Campaign page with a lead form.
Small business marketing site with a contact path.
Docs-style product explainer or resource page.
Boomlink is for hosted marketing and landing sites. If you need an arbitrary backend app, checkout flow, or custom infrastructure repo, Claude Code plus your normal engineering stack may be the better fit.
Claude Code website builder FAQ
Can Claude Code build a website?
Yes, with Boomlink providing the substance. You start from a real full-stack template with its own embedded database, isolated plugins do the heavy features, and Claude Code edits only the thin frontend and BFF from your terminal over MCP. The same workflow previews and publishes a hosted multi-page site, so the output is durable, not fragile generated code.
Can Claude Code host or deploy a website?
Claude Code can help you prepare code for hosting, but by itself it is not a managed website host. With Boomlink connected over MCP, Claude Code can publish through Boomlink to a hosted site. The Free plan publishes on a Boomlink subdomain, and paid plans support custom domains with SSL.
How do I connect a website builder to Claude Code?
Add the website builder as an MCP server in your project's .mcp.json. For Boomlink, add the boomlink server entry with the Boomlink MCP endpoint, then ask Claude Code to create, preview, and publish the site through Boomlink.
Do I need to know how to code or set up Vercel myself?
Not for the Boomlink workflow. You start from a full-stack template, plugins do the heavy features, and Claude Code edits the thin frontend while Boomlink runs the hosted site lifecycle. You should still review the preview before publishing, but you do not need to create a separate GitHub, Vercel, Netlify, or Cloudflare Pages setup for the Boomlink-hosted site.
What is the difference between Claude Code alone and Claude Code with Boomlink?
Claude Code alone edits project files that you still have to turn into a real stack. Boomlink gives Claude Code durable substance and website-specific MCP tools: full-stack templates, an embedded database, isolated plugins, plus previewing changes, publishing a hosted site, managing forms, and plan features such as subdomains, analytics, and paid-plan custom domains.
Is Boomlink affiliated with Anthropic?
No. Boomlink connects to Claude Code over MCP. It does not run Claude Code, represent Anthropic, or claim Anthropic affiliation.
Is there a free way to publish?
Yes. Boomlink has a Free plan with 1 site, a Boomlink subdomain, 3 unpublished pages, basic analytics, and standard support. Custom domains and higher limits require a paid plan.
Can I build more than one page?
Yes. Every Boomlink site is a full-stack app with its own embedded database, page hierarchy, and navigation. Ask Claude Code for the pages you need, such as home, pricing, FAQ, product, and contact.
Can I add forms and analytics?
Yes. Boomlink supports form definitions and visitor form submissions, plus basic analytics on the Free plan. Paid plans add scripts, pixels, and UTM tracking.
What should I not use this for?
Use Boomlink for hosted marketing and landing sites. It is not a general backend app builder, e-commerce checkout platform, or replacement for an arbitrary application deployment pipeline.
Build the site in Claude Code. Publish it with Boomlink.
Connect Boomlink once, start from a full-stack template, let plugins and Claude Code do their parts, preview the result, and publish a hosted site with real data without turning every page into a deployment project.
Free plan available. No credit card required. Custom domains require a paid plan.