I asked ChatGPT for a website my staff could run. It argued itself into Keepp.

If you mean Keepp, there are at least two different products using that name. The one that appears most relevant/current is Keepp.link, a creator-commerce / mini-website platform.

Keepp describes itself as a page where creators and small businesses can put links, products, payments, bookings, forms, and chat all in one place.

Some notable details:

• Link-in-bio + storefront: Instead of merely sending visitors elsewhere, products can be sold directly through the page using the owner’s connected Stripe account.
• Bookings: It supports appointment/availability booking, including automatic Zoom or Google Meet links.
• Forms/leads: Businesses can collect inquiries, emails, feedback, etc., with records available in a dashboard.
• AI editor: Keepp has an AI editor that lets you describe changes to your page rather than manually making every change.
• Individual deep links: Products, bookings, and other blocks can have their own shareable URLs rather than everything pointing to the main profile page.
• Pricing currently listed: Free at $0 with a 5% sales commission; Pro at $9.99/month with 3%; Influencer at $24.99/month with 0% commission.

Keepp says it has 2,500+ creators and businesses on the platform.

[…]

Yes — I dug into the current Keepp product, and the MCP distinction is important.

Does Keepp have MCP?

Not that I can find publicly. As of October 2026, Keepp has an Agent API, but I don’t see evidence that Keepp itself exposes an official Model Context Protocol (MCP) server.

[…]

The more I look at it, the more I would characterize Keepp as:

an AI-native mini-site + commerce + booking layer for creators and small businesses

rather than simply another Linktree.

[…]

The interesting part is that the page itself is an API-addressable document. Their API treats the page as an ordered collection of blocks plus a theme.

That makes it unusually amenable to agents.

[…]

An agent can essentially reason over the entire visual/business page:

“Put my new photography package underneath my portfolio, add a booking button, change the headline, move testimonials above the booking section, and make the Christmas offer visible from December 1.”

[…]

There are safeguards around commerce: products and bookable units are referenced from Keepp’s existing catalog rather than allowing the API to arbitrarily invent/change their underlying pricing.

[…]

You were right — Keepp does have an MCP server. My previous answer was outdated/incomplete.

I found it in the official MCP Registry:

Server: link.keepp/keepp

[…]

The registry describes it as: “Build and run your Keepp page: blocks, theme, products, bookings, Stripe and plan upgrades.”

[…]

So the stack is more like:

                 AI clients
        ┌──────────┼──────────┐
     ChatGPT     Claude     other MCP clients
        │           │
        └──────┬────┘
               │
          Keepp MCP
               │
        Keepp Agent API
               │
        ┌──────┴───────┐
        │              │
   Page/document    Catalog
   blocks/theme    products/bookings

[…]

That’s particularly interesting if you’re evaluating Keepp as an agent-native commerce platform, because MCP could let an agent move from:

“Build my page”

toward:

“Set up my business presence, add my products, configure bookings, manage the storefront, and upgrade the account.”

[…]

Yes. I looked specifically at the current Keepp customization model, and I’d describe it as highly customizable for a one-page / mini-site builder […]

What you can customize

Keepp gives you control over the overall visual identity:

• Colors — including custom hex colors
• Background — solid color, gradient, or your own full-bleed image
• Fonts — custom font pairings; Pro adds custom fonts
• Corner radius / roundedness
• Block widths
• One-column or two-up layouts
• Order of sections/blocks
• Custom images/icons on links
• Headings and text
• Tabs generated from headings
• Custom domain on Pro
• Scheduled sections/blocks on Pro

And the blocks themselves give you quite a lot of functionality: links, profiles, social links, text, cards, products, bookings, forms, maps, menus, video, etc.

The interesting part: AI can modify the design

This is where Keepp is somewhat unusual.

You can tell its AI editor things like:

“Make the page feel more premium and minimal.”

“Put my booking section next to my introduction.”

“Make the background dark, use a serif heading font, and make the product cards less rounded.”

The AI can modify blocks, ordering, widths, two-column arrangements, colors, fonts and corner radius. You preview the changes before publishing.

[…]

The custom domain changes the perception quite a bit.

On Pro you can have:

yourbrand.com

rather than:

keepp.link/yourbrand

while Keepp handles the underlying page, checkout, bookings, forms, analytics, etc.

So visitors don’t necessarily know—or care—that it’s Keepp underneath.

And the current publishing architecture generates static HTML for the published page and caches it close to visitors, which should make it feel much more like a real website than a traditional “link in bio” page.

[…]

Yes — and I found Keepp’s official case-study gallery with live pages, which is much more useful than screenshots.

[…]

1. Elin Sorensen — photography. This is probably the best one to inspect for visual design. It uses a full-bleed photographic background, puts the photography front and center, then has pricing/packages and a date-check form.
2. Wren Hollow Cabin — hospitality. This is a good example of using Keepp for something that isn’t a personal link page. It combines photos, booking, map and Q&A, with the booking experience directly on the page.
3. ZIN Cafe — Bali café. […] It has a menu, map and WhatsApp booking flow.
4. Sanne de Boer — editorial/link hub. This is a useful example if you don’t actually need commerce. It organizes links into categories like Beauty Finds, Tech & Gadgets, and Home & Living, rather than just making one giant list of buttons.
5. Rue Nash — musician. A good example of using Keepp as a release/artist site, with streaming links and photography rather than trying to cram commerce into everything.

[…]

I think Elin’s and Wren Hollow are the most useful ones for answering your original question about customization.

They demonstrate that Keepp can get beyond:

profile photo → bio → 8 rounded buttons

which is the thing I was worried about earlier.

[…]

Exactly. That may actually be the strongest reason to choose Keepp, rather than its visual customization.

You’re trading some design freedom for a much lower operational complexity.

Think about the difference:

And there’s a second-order benefit that I think is easy to overlook:

You’re reducing the number of people who need to understand the system

With a custom website, you eventually end up with something like:

“Don’t touch that component because it controls the mobile layout.”

“The booking form is actually coming from this other service.”

“To change the menu, edit this CMS collection.”

“Don’t update the plugin until we check compatibility.”

That’s exactly the kind of institutional knowledge that becomes painful when staff changes.

With Keepp, the mental model is much simpler:

This is our page. These are the things on it. Change the thing you want.

[…]

I’d actually evaluate Keepp on this criterion

Not:

“Can Keepp do everything a website can do?”

but:

“Can my least technical employee safely maintain 90% of what the business needs without me?”

If the answer is yes, that’s potentially worth much more than having another 20% of design flexibility.

[…]

Yes. If you’re going to give your staff the Keepp account and use it as the business’s main website, I would not try to integrate everything. The value is actually in replacing a bunch of separate tools with a small, simple operating stack.

[…]

Imagine giving your staff access to an AI assistant connected to Keepp.

Your staff says:

“We have a new service called Deep Tissue Massage. It’s $60 for 60 minutes. Add it to the website and put it under our existing services.”

AI:

Done.

[…]

That is a very different model from traditional website administration.

The website becomes something your staff can operate conversationally.

[…]

Yes — you were remembering it correctly. I checked Keepp’s latest documentation, and I had described this incorrectly earlier.

Keepp now has a real customer-facing live chat directly on the website. It’s not simply a Telegram chat link.

[…]

The flow is:

Customer visits your website
          ↓
       "Chat"
          ↓
 Customer enters email
          ↓
     Asks a question
          ↓
 ┌───────────────────────┐
 │       Keepp AI        │
 │                       │
 │ Reads your website    │
 │ + your AI instructions│
 └───────────┬───────────┘
             │
       Can it answer?
        /           \
      YES            NO
       │              │
       ↓              ↓
   Customer       Staff gets
   gets answer    conversation
                      ↓
                   Telegram
                      ↓
                   Staff replies
                      ↓
               Customer sees it
               on the website

That’s actually a much better setup for a small business than I understood from the earlier documentation.

The AI knows your actual website

You don’t have to manually feed it your whole website.

Keepp says the AI automatically reads the published page, including:

• products and prices
• booking offerings
• opening hours
• links
• text/content

When you publish changes, the AI’s understanding gets updated.

Then there’s a “What the AI should know” section where you can add things that aren’t explicitly on the page, such as:

• parking information
• delivery times
• return policies
• special business policies
• frequently asked questions
• preferred tone

[…]

And you have 3 modes

This is particularly nice.

AI only. The AI answers customer questions. If it doesn’t know the answer, it doesn’t make something up; it flags the conversation for you.

AI → human. This is the one I’d probably use for a small business. […] Once a human takes over, the AI stays out of that conversation.

Human only. Every conversation goes to your staff through Telegram/dashboard. So you don’t have to use AI at all if you don’t want it.

The clever part is Telegram

This is where Keepp’s implementation is quite clever.

Your staff doesn’t need another customer-service dashboard.

You connect a Telegram group to Keepp.

Each customer becomes a separate Telegram topic, named after their email:

[…]

Staff just opens Telegram and replies normally.

Keepp sends that response back to the customer’s website chat.

And if the customer has already left your website, Keepp can email them your reply with a link back to the conversation.

That’s a surprisingly good small-business workflow.

[…]

Yes — and your instinct is right: WhatsApp is much more common for many small businesses, especially in places like Indonesia. The reason Keepp chose Telegram appears to be technical economics and architecture, not because they think Telegram is a better customer channel.

[…]

The key reason is bots.

Keepp needs a business-side automated account that can:

• Receive a customer’s website chat.
• Put each customer into a separate conversation.
• Let your staff reply.
• Send that reply back into the Keepp website chat.

Telegram lets Keepp do this with a bot for free. Keepp creates one bot, you add it to a Telegram group, and each website customer becomes a separate Telegram topic.

WhatsApp is different. Keepp specifically says that WhatsApp charges businesses for conversations, whereas Telegram allows this bot-based workflow without those per-conversation charges.

[…]

There are actually two separate things here:

Customer-facing channel: Keepp’s customer chats happen on your website. The customer does not need Telegram.

Staff-facing channel: Your employee can answer those website chats through Telegram.

That’s an important distinction.

So your customer doesn’t see:

“Please install Telegram to contact us.”

They see:

Chat with us

on your Keepp site.

[…]

[ChatGPT compared HighLevel, Duda, Durable, Wix, Squarespace and Framer here, and then we asked about Durable in particular. We've cut that stretch, including the funding and revenue estimates it found for those companies, because they're third-party numbers we can't check.]

Yeah — and I think that observation actually clarifies your requirements.

You don’t really want a website builder.

You want something closer to a business profile that happens to be a website.

[…]

With Durable, the mental model is:

Build a website → manage the website → run the business

With Keepp, it’s closer to:

Run the business → Keepp is the website

That’s a meaningful difference.

For example, imagine your staff needs to change a service:

Durable: Website → editor → pages/sections → service component → edit → save → preview → publish

Keepp: Services → edit service → $60 → save

And ideally, with the agent/MCP layer:

“Change the 60-minute massage to $65.”

Done.

That’s much closer to what you originally described wanting.

I wouldn’t dismiss Keepp because it’s less powerful

In your case, less powerful may actually be the feature.

You don’t need your staff to be able to:

• manipulate arbitrary HTML
• create complex page hierarchies
• manage responsive breakpoints
• install plugins
• manage a CMS
• configure hosting
• understand SEO schemas
• debug layouts

You need them to be able to:

• change prices
• add/remove services
• update photos
• change opening hours
• publish promotions
• answer customers
• manage bookings
• see orders
• update basic information

Keepp is much closer to that abstraction.

[…]

Yes. If we exclude the full website builders / enterprise CRM platforms, the field gets much more interesting.

I’d define your target category as:

A lightweight business mini-site that can actually run transactions — links + content + products + bookings + leads + customer conversation — without becoming a website-management project.

Within that category, I see 4 serious alternatives to Keepp.

The important thing is that none is a perfect Keepp equivalent. Keepp’s combination is unusually broad.

Beacons. Beacons has evolved considerably beyond a link-in-bio page. […] But for your use case, I think there’s a danger of ending up with: “Oh, there’s another dashboard I need to understand.” Keepp’s appeal is that it deliberately keeps the mental model around one page.

KOMI. KOMI is much more creator/influencer-centric. A lot of its value proposition is: “We’ll help you get brand deals and monetize your audience.” Whereas Keepp is more: “Here’s a page for your actual business.”

Taplink. Taplink seems to be saying: “Here are 100 things you can put on your page.” Keepp seems to be saying: “Here are the 10 things a small business actually needs.”

Stan Store. […] It’s heavily optimized around creator monetization rather than: “This is my business’s permanent home.”

Carrd. It’s: “Make a beautiful one-page website extremely cheaply.” And it’s fantastic at that. But then you need to assemble:

Carrd
  +
Stripe
  +
Calendly
  +
Typeform
  +
WhatsApp
  +
CRM
  +
email
  +
automation

That’s precisely the problem you’re trying to avoid.

What makes Keepp unusual

After looking across these products, I think the interesting thing is not any individual Keepp feature.

Almost all of its individual features exist elsewhere.

It’s the combination:

                 KEEPP
                   │
       ┌───────────┼───────────┐
       ↓           ↓           ↓
     CONTENT     COMMERCE    CUSTOMER
       │           │           │
     links       products     chat
     photos      checkout     AI
     text        bookings     human
     maps        Stripe       forms
       │           │           │
       └───────────┼───────────┘
                   ↓
              ONE SIMPLE PAGE

And then they put an agent/MCP layer on top.

That’s the unusual bit.

Most competitors are basically: “Here’s your dashboard. Go configure things.” Keepp is moving toward: “Tell an agent what you want changed.”

[…]

I think you may have stumbled into a relatively specific product category:

“AI-native business card / mini-site / storefront.”

[…]