webbysol.fun

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. You stay signed in as you: a client only ever sees the sites on your own account, and only after you approve it.

The address

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

Server URL
https://www.webbysol.fun/api/mcp

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.

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.

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.

What it can do

Reading, which cannot change anything:

  • List sites · list_sites
  • Get a site · get_site
  • List a site's blocks · list_blocks
  • List the kinds of section available · list_block_types
  • Describe one kind of section · describe_block_type

And changing:

  • 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
  • Change the site's look · update_theme
  • Set the coin's details · update_token
  • Set the title, description and share images · update_seo
  • Take a site on or off line · set_visibility
  • Put a picture into the site's storage · upload_image

What it cannot do

Nothing here spends money or puts anything on the internet by itself. Publishing a site and launching a coin are deliberately absent from the list above, and no amount of asking will make a connected client do either: they are not tools it has. Those stay with you, in the editor.

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.