How to deploy a landing page from Claude Code

You asked Claude Code for a landing page and have a good index.html. Your next hour usually goes to plumbing: a repo, a host, a form backend, an analytics snippet, and DNS. This guide compares that route with deploying through Convika's MCP server, where each step is one sentence to Claude Code.

Two ways to deploy from Claude Code

Claude Code runs on your machine and edits files. It can publish a page as an artifact on claude.ai. That page has no backend to keep signups and stays on a claude.ai address. A landing page on your own domain must go to a host.

If the landing page is part of an app you already deploy, keep it in that repo. If it is a standalone page for a launch, a waitlist, or an ad campaign, the second column is less to maintain.

Deploying without handing Claude Code your hosting keys

Deploying with a host's command-line tool often runs on a token you saved in a file or an environment variable. The access that deploys can also delete. Convika connects through a sign-in in your browser, so you never copy a key into a file or the chat. The bigger difference is scope. Once connected, Claude Code gets Convika's page tools: saving, previewing, publishing, rolling back, forms, analytics, and domain setup.

What the agent can reach on each route

Vercel's MCP server also signs in through your browser, so the sign-in alone does not set Convika apart. What differs is how much the agent can reach once it gets in.

When the agent holds the key

In each of these incidents, an AI agent could reach credentials on the machine where it ran.

• LiteLLM, October 21, 2026. LiteLLM's Agent Platform, an experimental project whose cloud agents file pull requests, held the GitHub token of one of its two organization owners, a token that "was not associated with a service account and was not scoped down." A master key committed to a public repository let an attacker read that token through the platform's API, then release litellm 1.107.0 and four LiteLLM Docker tags with a credential stealer (LiteLLM). The stealer collects the tokens and configs of Claude Code and other AI coding tools, along with cloud credentials and SSH keys (SafeDep). What to check and rotate: LiteLLM 1.107.0 compromised on PyPI and Docker: what to do.
• PocketOS, April 25, 2026. A Cursor agent hit a credential mismatch in staging. It found a Railway token that had been “created for managing custom domains,” and used it to delete the production volume and the backups stored in it. The deletion took 9 seconds (Zenity). Railway later restored the data (Tom's Hardware).
• DataTalks.Club, February 26, 2026. The owner was moving a static website from GitHub Pages to AWS. A Claude Code agent ran terraform destroy against an outdated Terraform state. It removed the course platform's VPC, load balancers, database, and automated snapshots. AWS support later restored the database (AI Incident Database, Alexey Grigorev).
• s1ngularity, August 26, 2025. Malicious versions of the Nx build tool stayed on npm for 4 hours. They scanned developers' machines for sensitive data, tried to use the AI command-line tools installed there, such as Claude and Gemini, and uploaded what they found to public GitHub repositories (Nx). GitGuardian counted 2,349 leaked secrets; the most common were GitHub, npm, AWS, and OpenAI (GitGuardian).

Keys also leak through ordinary commits. GitGuardian's 2026 report shows that commits made with Claude Code's help leaked a secret about 3.2% of the time, 2× the baseline. The report notes these leaks “may ultimately reflect human mistakes, not just AI failures” (GitGuardian, March 17, 2026).

What Claude Code can do in Convika

Connecting opens a Convika sign-in in your browser, followed by a screen asking whether to let the AI client into your Convika account, with Allow and Deny. Claude Code keeps the sign-in itself in macOS Keychain, or ~/.claude/.credentials.json on Linux. Running claude mcp remove convika deletes it. Then Claude Code has Convika's 37 tools.

• Pages: create a page, save a new version, make a preview link, publish, roll back, unpublish
• Forms: add a form, read its entries, export them
• Analytics and goals: visits, traffic sources, devices, button clicks, conversion goals
• Domains: connect a subdomain and check its status; Convika shows a CNAME and a TXT record, and you add them at your DNS provider
• Sharing: your referral link, and a claim link that hands a page you built to someone else

None of them changes your plan or payment details, signs in to your DNS provider, or deletes a page. There are no environment variables or databases to reach: each Convika page is one HTML document.

What happens before a page goes live

Each change is saved as a new version. By default, Claude Code makes a private preview link for you to check. The link uses a random 64-character token, tells search engines not to index it, and stops working after 1 hour. Your live page changes only when Claude Code publishes, which Convika's tool tells it to do only when you ask. Publishing, rolling back, and unpublishing are marked as tools that change a live page. Claude Code's permission settings can require your approval before each.

How to undo

Ask Claude Code to roll back to an earlier version, or click Roll back to this version under Version History in the dashboard. To take the page offline, ask it to unpublish, or click Unpublish. The content stays, so you can publish again later. Free keeps 10 saved versions, and Pro keeps 50. The live version and the one behind the current preview are always kept.

If you deploy with a CLI anyway

Deny .env reads in Claude Code's settings with Read(./.env) and Read(./.env.*), the example in Claude Code's settings docs. Give the deploy a token scoped to one project, not your whole account, following Vercel's advice to “pick the narrowest scope that covers the work.” If you share a Claude artifact rather than deploying a page, check links and search engines in who can see your Claude artifact. For other servers that publish pages, see Landing page MCP servers compared.

Deploy with Convika in 5 steps

Create a free Convika account

Sign up at app.convika.com. Convika is free, and you do not need a credit card.

Add the Convika MCP server to Claude Code

Run this in your terminal:

claude mcp add --transport http convika https://mcp.convika.com

Add --scope user so the server is available in every project. Next, run /mcp inside Claude Code, or run claude mcp login convika from your shell. Both options let you sign in to Convika in your browser. See Claude Code's MCP docs for flags and the full login flow.

Save the page and open the preview

Tell Claude Code: “Save landing/index.html to Convika as a new site and give me the preview link.” Claude Code reads the file and sends the HTML. Convika stores each page as one HTML document. Its tools ask for Tailwind CSS v3 from the CDN. If your page comes from a build step like Vite or Next.js, ask Claude Code for a single static HTML file first. Use public URLs for images, or embed them directly in the file.

Add a form and publish

Say to Claude Code: “Add a waitlist form with name and email under the hero, then publish.” Your page goes live at an address like yourproduct.convika.page. Convika checks form entries sent from the preview. It does not store them, so test signups do not pollute your list.

Connect your domain and read the results

Say: “Connect launch.yourproduct.com.” Convika returns a CNAME record for your DNS provider and issues the SSL certificate. This automatic setup configures subdomains. It does not configure a bare yourproduct.com. A few days later, ask Claude Code: “Which sources sent signups this week, and which button got clicked most?” Claude Code reads visits, UTM sources, devices, button clicks, and form submissions from Convika.

Coming from Claude Design

Claude Design exports a design as standalone HTML or hands it off to Claude Code, per Anthropic's help center. Send the design to Claude Code on your machine, ask it to turn the design into a single HTML page, and move to step 3 above. If you only need the page online, skip Claude Code. Upload the standalone HTML export as is: how to publish a Claude Design website.

Using Codex or another MCP client

The same server works in any client that supports remote MCP servers. Add https://mcp.convika.com in your client's MCP settings and finish the sign-in. The prompts in this guide work the same way.

If you want a subagent to build the page and only give that subagent Convika's tools, see Codex vs Claude Code subagents for how to configure mcpServers or disallowedTools in Claude Code and disabled_tools in Codex.

To have Claude Code ask you before it publishes or unpublishes a live page, see Claude Code hooks: how to block a command before it runs, which puts a hook on the 4 Convika tools that change a live URL.

Frequently asked questions

Can Claude Code deploy a website by itself?

For a single page without a backend, yes. Claude Code publishes an artifact to claude.ai, and its docs say the public link opens for anyone without signing in. On Team and Enterprise plans, an Owner must turn public sharing on first. That artifact is one page with no backend, so it cannot save form entries, and it stays on a claude.ai address. If you want your own domain, have Claude Code run a host's CLI (such as Vercel's or Netlify's) if installed and logged in, or connect Convika using this guide. If you want to send a report or slides to someone without a Claude account, read how to share an HTML file from Claude. For a deck you plan to present, see how to share an HTML slide deck as a link.

Can Claude Code read my .env file?

Yes, unless you deny it access. Claude Code's settings docs give Read(./.env) and Read(./.env.*) as the deny rules to “stop it reading .env files.” According to its permissions docs, these rules cover Claude Code's file tools and commands such as cat. They do not block a script that opens the file itself, and they point to the sandbox for that protection. Deploying to Convika puts nothing in .env, because Claude Code connects through a sign-in in your browser.

Is it safe to give Claude Code my Vercel token?

The token can do whatever its scope allows. Vercel scopes a token to your full account, one team, or one project. Its advice is to “pick the narrowest scope that covers the work.” Vercel's own MCP server signs in through your browser, which Vercel says “grants the AI system you're using the same access as your Vercel user account.” Convika's connection reaches only Convika's page tools. It cannot access your plan, payment details, environment variables, or DNS records, and it includes no tool that deletes a page.

What can Claude Code do in my Convika account?

Claude Code can run Convika's 37 tools on your landing pages. It can create pages, save new versions, make preview links, publish, roll back, and unpublish. It can add forms, read and export form entries, set conversion goals, read analytics, and connect a subdomain. It can also generate a referral link or a claim link to hand a page to someone else. It cannot change your plan, edit payment details, delete a page, or sign in to your DNS provider.

Can Claude Code publish my page without asking?

Not by default. Convika saves each change as a new version, and its tools tell Claude Code to show you a private preview first. Your live page changes only when Claude Code publishes, which Convika's tool tells it to run only when you ask. Publishing also has a tag as a tool that changes a live page, so your Claude Code permission settings can require your approval before it runs.

How do I undo a change Claude Code made?

Ask Claude Code to roll back to an earlier version, or click Roll back to this version under Version History in the Convika dashboard. To take a page offline, ask Claude Code to unpublish it, or click Unpublish. Your content stays in your account so you can publish it again later. Free accounts keep 10 saved versions, and Pro keeps 50.

Do I need a Git repo?

No, you do not need one. Convika saves every update as a version, so you can preview, publish, and roll back without Git. You can still store your HTML in a Git repository if you want your commit history there too.

What kind of page can I deploy?

You can deploy one HTML page per site, with CSS and scripts written inline or loaded from a CDN. Convika hosts landing pages. If your software needs a user login, a database, or several routes, deploy it to a general-purpose host instead.

Does it use Convika's AI credits?

No, it spends zero credits. Claude Code writes the page code, so Convika charges no credits for the deployment. Convika credits pay only for Convika's built-in AI when it writes pages inside the dashboard.

Can Claude Code read the page's analytics?

Yes, Claude Code reads your stats through the same connection. It can check visitor counts, traffic sources, UTM tags, devices, button clicks, and form submissions. You can also export those submissions as a CSV file.

What does it cost?

The Free plan costs nothing and requires no credit card. It includes 1 published page with a small Convika bar at the bottom, 50 form entries a month shown (entries past that are kept and show on Pro), and 1 custom domain. The Pro plan gives you 50 sites, removes the Convika bar, and shows every form entry, with no cap on domains. Pro costs $12 a month.