webbysol.fun
Model Context Protocol

Connect your AI to webbysol

webbysol speaks the Model Context Protocol, so Claude and other AI clients can build and edit your sites directly. Ask for a section, a colour change or a reorder, and it happens on your site. Or start from the Blank slate and have it write the whole site in code. You stay signed in as you: a client only ever sees the sites on your own account, and only after you approve it.

Paste this into your AI
I'd like to connect webbysol, a website builder for businesses and coins, to you as an MCP connector so you can build and edit my sites. It is a remote HTTP MCP server at https://www.webbysol.fun/api/mcp and it signs in with OAuth. Setup notes: https://www.webbysol.fun/agent-setup/prompt.md. If you can add it yourself, please do; otherwise tell me the exact steps for the app I'm using.

An assistant that can add connectors does it for you. One that cannot, like Claude on the web, tells you where to paste the address. Same thing the button on the front page copies.

Or, the server URL
https://www.webbysol.fun/api/mcp

Wherever a client asks for an MCP server URL, this is it.

Free, and included. Connecting costs nothing and there is no key to buy. Publishing a site is the same one-off payment it always was.

Three ways in
1

Claude, on the web or desktop

  1. Open Settings, then Connectors.
  2. Add custom connector.
  3. Paste the URL above. Leave the authentication settings as Claude detects them: sign in now, and Claude's published identity.
  4. Add, then Connect. Approve the request on the webbysol screen that opens.

Leave Request headers empty. That box is for servers that use an API key, and this one uses OAuth.

2

Claude Code

Terminal
claude mcp add --transport http webbysol https://www.webbysol.fun/api/mcp

It opens a browser to sign in the first time, then remembers.

3

Anything else

Any client that speaks MCP over HTTP works. Most take a block of JSON like this.

Configuration
{
  "mcpServers": {
    "webbysol": {
      "type": "http",
      "url": "https://www.webbysol.fun/api/mcp"
    }
  }
}

Authentication is OAuth 2.1 with PKCE. Clients discover it themselves from /.well-known/oauth-protected-resource; there is nothing to register and no key to paste. Client ID Metadata Documents are supported, and dynamic registration still works for clients that have not moved to them.

Things to say to it

  • “Start a new site with me. It is for my bakery in Austin”
  • “Add a menu page and put it in the nav”
  • “Write a blog post about our new oven”
  • “Make the whole thing darker and rounder”
  • “Move the reviews above the menu”
  • “Swap the hero picture for this one”
  • “Add an FAQ to my site and fill it in from the lore”
  • “What pages does my site have?”

It asks before it builds

Ask for a new site and it starts with a short conversation rather than a guess: what kind of site it is (a shop, a restaurant, a service people book, a portfolio, a band, a blog, a coin), then a few questions about what that kind of site needs. It suggests the pages you should have, sums it all up as a short brief, and waits for your yes before it builds. The brief is saved with the site, so the next conversation picks up where this one left off. While it works it tells you what it is doing and shows you how the site looks, and it finishes with whatever is left for you to do.

More pages, and a blog

A site can have up to 30 more pages and 500 blog posts inside the address it already has, at no extra cost. Your AI makes them the way it makes the home page: it adds a page, puts it in your menu, builds its sections and shows you a preview. A new page on a live site stays a draft only you can see until you say to make it public.

What it can do

Reading · 25

Cannot change anything. Reasonable to set to always allow.

  • Read the design guide · get_design_guide
  • See the site as a visitor does · preview_site
  • Check a site for design problems · review_site
  • Run a site's code and report what breaks · check_code
  • Study the design of a site the person likes · study_site
  • List sites · list_sites
  • Get a site · get_site
  • List a site's blocks · list_blocks
  • Read one section · get_block
  • See a site's visitors · get_site_stats
  • See the coin's live numbers · get_token_stats
  • List the kinds of section available · list_block_types
  • Describe one kind of section · describe_block_type
  • List a site's pages and posts · list_pages
  • List a site's checkpoints · list_checkpoints
  • See how the site does in search · get_search_report
  • See a site's shop · get_shop
  • List a shop's products · list_products
  • See the person's webbysol wallet · get_wallet
  • List the launchpads a coin can go on · list_launchpads
  • List what a coin can be priced in · list_launch_pairs
  • See files recently uploaded to a site · list_uploads
  • Look through a video · preview_video
  • See every file on a site · list_media
  • List the templates a site can start from · list_templates
Changing · 34

Edits your live site. Worth leaving on approval while you get a feel for it.

  • Add a section · add_block
  • Change a section's content · update_block
  • Move a section · move_block
  • Set the whole running order · reorder_blocks
  • Duplicate a section · duplicate_block
  • Show or hide a section · set_block_visibility
  • Delete a section · remove_block
  • Add a page or a blog post · create_page
  • Change a page's details · update_page
  • Delete a page or post · delete_page
  • Remember what was agreed · save_site_brief
  • Make many changes in one go · apply_changes
  • Save a checkpoint to come back to · save_checkpoint
  • Put a site back to a checkpoint · restore_checkpoint
  • Change the site's look · update_theme
  • Set the coin's details · update_token
  • Set the title, description and share images · update_seo
  • Set the business details search engines read · set_business_details
  • Put a Review us on Google button on the site · add_review_button
  • Add products to a shop · add_products
  • Change a product · update_product
  • Delete a product · remove_product
  • Set how a shop sells · set_shop_settings
  • Take a site on or off line · set_visibility
  • Publish a site · publish_site
  • Launch the site's coin · launch_coin
  • Put a picture or video into the site's storage · upload_image
  • Get a link for the person to upload their own files · request_upload
  • Cut the background out of a picture · remove_background
  • Crop, resize, round or tidy a picture · edit_image
  • Cut a clip out of a video · trim_video
  • Delete a file nothing uses · delete_media
  • Start a new site from a template · create_site
  • Change a site's web address · set_address

A whole site, written in code

Start from the Blank slate template and your AI can write the site itself: its own HTML, CSS and JavaScript, with any layout, animation or library it likes, filling the whole screen. The live price, market cap and a buy button that follows your coin are one attribute each, so a site written from scratch is still your coin's site. Show it a site you like and it can study the design (colours, type, motion) and build something in the same spirit, with your own words and pictures.

The code runs sealed off from webbysol, from your account and from your visitors' wallets. Code that reaches for a wallet, asks for a seed phrase or a password, mines, hides what it does, or sends the page somewhere else is refused when it is saved, with the reason.

What it cannot do

Nothing here spends money. Publishing a site, and launching its coin on pump.fun or StonkFun, are prepared for you rather than done: the client checks the site and your wallet and hands you a link, and nothing is paid for or created until you open it, check it and approve it with your own wallet. The one thing done straight away is putting a site you have already paid for back live, because that costs nothing.

A client also cannot reach a site that is not yours. Every call checks who owns the site it names, against the account that approved the connection.

Approving tools

Claude asks before every tool call until you say otherwise. Setting the read-only tools to always allow is reasonable, since they cannot change anything. Leaving the rest on approval means you see each change to your site before it happens, which is worth keeping while you get a feel for it.

If a connection fails

  • The approval screen is built fresh by your client each time and works once. Reloading that tab, or opening the address directly, cannot work: the request lives in the link. Start again from your client.
  • If the screen says a client could not be verified, it names the reason. That is about your client's own published identity, not your account.
  • If tools are refused after connecting, the connection was approved for reading only. Disconnect and connect again to grant changes.

Anything you have connected is listed on your profile, with a button to disconnect it.