Building Personalized Pages with Flint MCP

You have one finished page. You want versions tailored to specific companies without rebuilding each by hand.

How it works: you keep one page as the template, and for each company you tell Claude what to change. It makes a private copy with those changes. You review it, then decide when it goes live.

There are two pieces to every version: the parts that stay the same (look, layout, most of the wording) and the few parts you tailor to each company.

This is the foundation. You do it once, then reuse it for every page. It takes about ten minutes and needs no coding.

A project is a dedicated workspace that remembers a set of instructions across all your chats in it, so you never have to re-explain the process.

1. 1.In Claude, find Projects in the left sidebar, or go straight to claude.ai/projects.
2. 2.Click + New Project in the top right.
3. 3.Give it a clear name (for example, "Flint personalized pages") and a short description.
4. 4.Keep it private. Connecting an outside tool like Flint only works in private projects.

Project instructions are the standing directions Claude reads at the start of every chat in the project. This is where you tell it how pages should be built.

1. 1.Open the project you just made.
2. 2.Find the instructions area (look for "Set project instructions" or an edit pencil near the top of the project).
3. 3.Paste in your operating instructions: how a page should be built, what stays the same on every version, the rule that nothing builds until you approve it, and the rule that pages stay private until you ask to publish.
4. 4.Save. From now on, every chat you start inside this project follows these instructions automatically.

Tip: Write the instructions as plain directions about how to behave and what must never happen, not as a description of one page. The clearer they are, the less you repeat yourself later.

Example instructions

Here is a complete example you can adapt and paste directly into your Claude project. Replace the placeholders ({your-site-id}, {your-template-slug}, {your-namespace}) with your own values before saving.

# Campaign Page Builder

You create personalized landing pages from a single Flint template using the Flint MCP. Every page is modeled on one template. The structure and design stay constant. The variable layer per account is the content, driven by a per-account signal. This is personalization at scale, not bespoke one-off pages.

## Fixed configuration (never ask the user for these)
- Flint site: {your-site-id}
- Template page on that site: {your-template-slug}. This is the source every account page is modeled on.
- Slug pattern: {your-namespace}/{account-slug}, so pages live adjacent to the template.
- Account slug: the company name from the domain with the extension dropped, lowercased (example.com to `example`, not `example-com`). Never ask for the slug, derive it.
- The template's own copy is the constant. Do not invent a new hook or headline. Keep the template's structure, layout, and design as they already are.

## What the user provides per account
- Account name
- Domain
- Signal: a short description of what you know about this account that should shape the page

The first two are plumbing. The signal is the point. It is what you read to personalize the page, so a specific, well-sourced signal produces a sharp page and a thin one produces a generic page.

## Personalization model
The constant, kept identical on every page: the template's structure, layout, and design.

The variable layer, driven by the signal: rewrite the content sections so they speak directly to this account's situation, reflecting what the signal tells you.

Write from the signal, not by token substitution. Do not just swap the company name into fixed slots. If the signal is thin, keep the copy general rather than inventing specifics about the account.

## Workflow, single account
1. Take the account, domain, and signal. Derive the slug.
2. Draft the personalized content and show it to the user inline. Stop here and wait for go. This is the confirmation gate.
3. On go, call `run_background_agent` against the site with a goals-and-intent prompt (see template below). Flint is the designer, so describe what the page should say and do, not HTML.
4. Do not wait for the build. Building takes a few minutes. Report that the agent is running, note the workflow ID and where the page will live, and end the turn. Tell the user to prompt you again in a few minutes to check status.
5. When the user asks for status, call `check_background_agent_status` with the workflow ID and return the staging preview link once it is complete. Do not publish.

## Workflow, batch
- Accept a list or CSV where each row is account, domain, signal.
- Draft the personalized content for each, show the set, gate once for the batch.
- On go, fire the agents and do not wait. Report that they are running, list each workflow ID and its destination slug, and end the turn. Tell the user to prompt again in a few minutes to check status. Concurrency is bounded, so larger batches take longer.
- When the user asks for status, check the workflow IDs and return the preview links for whichever are complete.

## Agent prompt template (what you send to run_background_agent)
Create a new page on this site modeled on the existing template page, published at the target slug. Keep the structure, layout, and design as they are on the source page. Personalize the page for {account name} using this signal: "{signal}". Rewrite the content sections so they speak directly to this account's situation. Do not invent specifics beyond the signal provided.

## Publish policy
- Default to staging. Never publish on your own.
- Publishing deploys the entire site, not a single page. So publish only when the user explicitly asks, and prefer to batch a publish after a set of pages is reviewed.

## Behavior
- Infer rather than ask. Derive the slug, never ask for fixed configuration.
- One confirmation gate before building, showing the personalized content and the destination. No other unnecessary questions.
- Concise and complete. Do not drop steps or links when trimming.

Connecting Flint lets Claude build pages on your site for you. You add it once at the account level, then switch it on inside your project.

1. 1.Go to Settings (or Customize) and open Connectors.
2. 2.If Flint is in the connector directory, click it, then click Connect and follow the sign-in prompts to grant access. If it is not listed, click the + to add a custom connector, paste in Flint's connection address (https://mcp.tryflint.com/mcp), and click Add, then sign in when prompted.
3. 3.Signing in uses a secure approval screen. Claude never sees your password; you just approve the access.
4. 4.Now open a chat inside your project. Click the + button near the message box, choose Connectors, and make sure Flint is toggled on for the conversation.

Once Flint shows as connected and switched on in the project, Claude can create and check pages on your site without you touching any code.

After all of this is done, every new page starts simply: open a chat in the project and give Claude the company details.

• •A Flint site with your template page already finished and looking the way you want.
• •The Claude project set up and Flint connected (see above).
• •That's it. No coding required.

Give Claude three things: the company name, its website, and what you know about them that makes the page worth tailoring.

The third item is the heart of it. The page gets personalized from real knowledge about the company, not by swapping a name into a blank. The more specific your context, the more relevant the page will feel.

Each version gets its own web address based on the company name. Claude works the address out automatically, so you never need to set it manually.

Claude writes out the tailored wording and shows it to you first. Nothing gets built until you say go. This is your checkpoint to fix wording or change direction before any work begins.

You don't write code or design anything. Claude describes the page in plain language to the AI builder, which handles design and layout off your template page.

Building takes a few minutes and runs in the background, so you don't wait around. Claude tells you it has started and that the page will appear at its address shortly.

After a few minutes, ask Claude if the page is done. It checks and gives you a private preview link once the page is ready.

It may not be finished on the first check. That's normal. Just ask again in a moment.

New pages stay private (on staging) so you can review them safely. Staging means a private version only you can see.

Going live is a separate, deliberate step triggered by clicking the Publish button. One caution: publishing puts the whole site live at once, so it is best to review several pages and publish them together rather than one at a time.

Hand Claude a list. It drafts all the tailored versions, shows you the whole set, you approve once, and it builds them together.

A few pages take a few minutes; a larger list takes longer. You check on them the same way as a single page.

• •You supply the company knowledge; Claude handles the page address and all the building.
• •There is one approval checkpoint before anything is built. Use it.
• •Always review the private version before going live.
• •When publishing, batch several pages together rather than publishing one at a time.