Since we shipped the Eventify AI Agent, the request I hear most is some version of this: I do not want to learn a page builder, I just want a clean event website on my own domain, and I do not want to pay for hosting. That is a fair ask, and it is now a short afternoon of work. This is the workflow I use.
The trick is to let each tool do the one thing it is best at:
- Eventify is the source of truth. Your event details, agenda, speakers, sponsors, tickets, and the registration and payment flow all live here.
- Claude is the builder. It reads your event data through the Eventify MCP and writes a custom website from your description.
- Cloudflare is the host. Cloudflare Pages serves the static site for free and connects it to your own domain.
What you will need
- An Eventify account with your event in it. The event, agenda, speakers, and ticket types. If the event is not set up yet, the Eventify agent can help you create it.
- Claude, connected to the Eventify MCP. Any MCP compatible client works. Claude is the smoothest to start with.
- A Cloudflare account and a domain. The free plan is enough. If your domain is already on Cloudflare, the custom domain step takes seconds.
Step 1: Get your event into Eventify
The website is only as good as the data behind it, so start here. If your event already exists in Eventify, skip ahead. If not, the agent can set it up from plain English:
Create a new in-person event called the Asia FinTech Summit 2026 in Singapore, running 12 to 13 November, and set the timezone to Singapore.
Add these eight speakers and place them on the day one agenda, with the opening keynote at 9am.
Create three ticket types: early bird at 199, standard at 299, and VIP at 599, and close early bird on 30 September.
Registration and payments run inside Eventify, which is the point. Your attendee data stays in one place under one security framework. The agent can also show you the registration form and set whether it is open to the public or invite only.
Good to know. In the current beta, the agent views your registration form and updates form level settings such as the title, description, confirmation message, and visibility. Adding or changing the actual fields collected, for example a company or job title field, is done in the dashboard form builder.
Step 2: Connect Claude to Eventify
In Claude, add a connector pointing at the Eventify MCP server:
https://amcp.eventify.io/api/v2/mcpClaude opens an authorization screen. Sign in to Eventify and approve access. The connection uses OAuth 2.1, so you are granting scoped access to your own account and can revoke it at any time. The full setup, including the steps for ChatGPT and Gemini, is in the AI Agent knowledge base.
Step 3: Have Claude build the website
This is where it comes together. Ask Claude to read the event from Eventify and turn it into a site. Because it is pulling live data through the MCP, the agenda, speaker names, and ticket prices on the page are the real ones, not placeholders you have to keep in sync by hand.
Using the Eventify MCP, pull the details for the Asia FinTech Summit 2026: the description, the agenda, the speakers, and the ticket prices. Build a single page event website from that data with a hero section, an agenda, a speaker grid, and a pricing section. Put a Register button in the hero and the pricing section that links to the event's Eventify registration page. Keep the design clean and fast, in a single HTML file.
Claude returns a complete HTML file. Review it, ask for changes in the same plain language, for example make the hero darker, move VIP to the front of the pricing row, or add a sponsors strip below the agenda, and iterate until it looks right. The registration and ticket buttons point back to your Eventify event, so the site stays a marketing front while Eventify does the transactional work.
Step 4: Publish to Cloudflare Pages with your own domain
Now put it online. Cloudflare Pages hosts static sites on the free plan and connects them to a custom domain. The command line tool for this is Wrangler. If you have never used it, here is the one time setup.
Install Wrangler (one time)
Wrangler runs on Node.js, so install Node first. Use a current LTS version (Node 20 or newer).
On Mac. Option 1, with Homebrew:
brew install nodeOption 2, without Homebrew: download the LTS installer from nodejs.org and run it. Then confirm Node is ready:
node --version
npm --versionOn Windows. Option 1, with winget, which is built into Windows 10 and 11:
winget install OpenJS.NodeJS.LTSOption 2, without winget: download the LTS installer from nodejs.org and run it with the default options. Close and reopen your terminal, then confirm:
node --version
npm --versionGet Wrangler and sign in. You do not need a separate global install. Running npx wrangler downloads it on demand and keeps it current. Check it works, then log in:
npx wrangler --version
npx wrangler loginThe login command opens your browser and asks you to authorize access to your Cloudflare account. Approve it once, and you are set. If you prefer a permanent install, run npm install -g wrangler and use wrangler in place of npx wrangler everywhere below.
Deploy your site
Save Claude's file as index.html in an empty folder, then deploy:
mkdir my-event-site
cd my-event-site
npx wrangler pages deploy . --project-name=my-event-siteThe first run creates the project. It returns a live pages.dev link straight away. You can also do this without the terminal: in the Cloudflare dashboard, go to Workers and Pages, choose Create, then Pages, then Upload assets, and drag in the file renamed to index.html.
Connect your domain
Open the Pages project, go to Custom domains, and add the address you want, for example summit.yourdomain.com. If the domain is already on your Cloudflare account, the DNS record is created and the certificate is issued for you within a minute or two. The site is then live on your own domain, with hosting at no cost.
Doing it through MCP. If you use the Cloudflare connector with Claude, the agent is strong at the infrastructure side, creating DNS records and pointing your custom domain. Pages project deploys themselves are still cleanest through Wrangler or the dashboard today, so a good split is to deploy with the command above and let the Cloudflare agent handle the DNS and domain wiring.
Why this combination works
You get a site that is genuinely yours: your design, your domain, your content, with no monthly hosting bill and nothing to maintain. The data behind it never goes stale, because it is read from Eventify rather than copied into the page. And the sensitive part, your attendees and their payments, never leaves Eventify. The marketing site is just a fast, public face in front of it.
The skill that matters here is not knowing a page builder. It is knowing your event and being able to describe it. The tools do the assembly.
For the bigger picture on why we built the agent, see Introducing Eventify's MCP Agent, or explore the Eventify AI Agent in detail.
If you build something good with this, I would like to see it. Onwards.
Frequently asked questions
Do I need to know how to code to build an event website this way?
No. You describe the event in plain English, Claude reads your real event data from the Eventify MCP and writes the website, and publishing to Cloudflare is one command or a drag and drop in the dashboard.
Is the hosting really free?
Yes. Cloudflare Pages has a free plan that covers static site hosting and a custom domain when that domain is already on your Cloudflare account. You need an Eventify account for the event data, registration, and ticketing.
Where does my attendee data live?
In Eventify. Registration and payments run on your Eventify event page, and the Cloudflare site links to it. Claude reads event details through the Eventify MCP, which runs on Eventify's own infrastructure, so your data is not routed through third party agent hosts.
Can the Eventify agent change the registration form fields for me?
In the current beta, the agent can view your registration form and update form level settings such as the title, description, confirmation message, and whether the form is public or restricted. Adding or changing the actual fields collected is done in the dashboard form builder.
Can I publish the site to my own domain?
Yes. If your domain is on Cloudflare, attach it to the Pages project as a custom domain and the DNS record is created for you. The site is then live on your own address at no hosting cost.


.png)

.jpg)

