Connect in one line
- ChatGPT, Claude — add
https://api.sitesfare.com/mcpas a custom connector and sign in with Sitesfare (OAuth 2.1 with PKCE). ChatGPT guide · Claude guide - Claude Code, Cursor, Codex, Windsurf and others — the same URL with
Authorization: Bearer <Studio key>. Claude Code · Cursor · Codex · others
Account and templates
account_me — Who am I connected as
The connected Sitesfare account: email, which site categories its AI editor add-ons cover, how many sites it has, and the licence. Call this first.
Read-only
account_sites — List the account's websites
Every website on the account with its id, subdomain, template, category, whether it is published, and whether AI editing is covered by an add-on.
Read-only
template_list — List the templates
Every template a new site can be built from: id, name, category, a short description and a preview page. Use the id with site_create.
Read-only · arguments: category?
Reading a website
site_get — Read a website
The structure of a site: its sections in page order (title, hidden, deletable), every field in each section with label, type, limit and value, the repeating items and their hidden state, and the theme (accent, fonts, mood, section backgrounds). Pass `summary: true` to get the shape without values first, then `section` to read one section in full.
Read-only · needs sites:read · arguments: site, section?, summary?
site_text — Read the page as text
The site rendered through its template and reduced to an outline: for each section its heading, visible text lines, image URLs and the fields it shows. Use it to match a screenshot to a section, or to check the page after editing.
Read-only · needs sites:read · arguments: site
section_html — Read one section's HTML
The rendered HTML of one section (scripts, styles and SVG removed, bounded in size), for matching a screenshot precisely or checking layout. Prefer site_text and site_get; use this when the structure matters.
Read-only · needs sites:read · arguments: site, section
Editing words, links, photos and the look
site_update_fields — Change text, links, dates or images
Set field values on a site (up to 200 at once). Keys come from site_get; values are plain text (no HTML). Each value is checked against the field's type and limit; if any value is refused nothing is saved and the message says what to fix. Saves a draft with a revision; site_publish puts it live.
Saves a draft with a revision · needs sites:write · arguments: site, fields
site_set_theme — Change colours, fonts, mood, scene
Change the site's look within its template: accent colour, display and names fonts (site_get lists the options), the mood (templates that have moods), the header photo, the 3D scene, and per-section background colours and photos. Saves a draft with a revision.
Saves a draft with a revision · needs sites:write · arguments: site, accentColor?, displayFont?, namesFont?, moodPalette?, heroBgImageUrl?, scene?, sections?
section_hide — Hide a section
Remove a section from the page (its fields are kept; section_show brings it back). Only sections marked deletable in site_get can be hidden.
Saves a draft with a revision · needs sites:write · arguments: site, section
section_show — Show a hidden section
Put a hidden section back on the page.
Saves a draft with a revision · needs sites:write · arguments: site, section
item_hide — Hide a repeating item
Remove one repeating item (a project, event, photo, testimonial…) from the page; its fields are kept and item_show restores it. Item ids come from site_get (e.g. project-2).
Saves a draft with a revision · needs sites:write · arguments: site, item
item_show — Show a hidden item
Put a hidden repeating item back.
Saves a draft with a revision · needs sites:write · arguments: site, item
Adding sections and buttons
section_add — Add a new section
Add a section of your own to a template site — a heading, text, an image and up to 3 buttons — at any place on the page (after a given section, at the start or the end). It takes the template's fonts and text colour and the site's accent colour, is part of the published page (search engines read it), and can be changed with section_update, hidden with section_hide and removed with section_remove. Up to 8 per site. Saves a draft with a revision.
Saves a draft with a revision · needs sites:write · arguments: site, after?, kicker?, heading?, body?, imageUrl?, imageAlt?, layout?, align?, bgColor?, buttons?
section_update — Change an added section
Change a section added with section_add: any of its heading, text, image, layout, colour, place on the page or buttons (the buttons list is replaced as a whole). Only the values given change. Template sections are changed with site_update_fields instead.
Saves a draft with a revision · needs sites:write · arguments: site, id, after?, kicker?, heading?, body?, imageUrl?, imageAlt?, layout?, align?, bgColor?, buttons?
section_remove — Remove an added section
Delete a section that was added with section_add (template sections cannot be deleted — hide them with section_hide). Kept in history: site_revert brings it back.
Changes or publishes — your editor asks first · needs sites:write · arguments: site, id
Images
media_upload — Upload an image
Add an image (PNG, JPEG or WebP) to the site's media library and get its URL. Give the bytes as base64 in `data`, or a public https URL in `source_url` that Sitesfare fetches. Optionally set an image field to the new URL in the same call with `set_field`.
Saves a draft with a revision · needs media:write, sites:write · arguments: site, data?, source_url?, filename?, set_field?
media_list — List the media library
Every image in the site's media library with its URL and size.
Read-only · needs sites:read · arguments: site
media_delete — Delete a media file
Remove one file from the media library (fields still pointing at it will show nothing).
Changes or publishes — your editor asks first · needs media:write · arguments: site, objectKey
Publishing and history
site_publish — Publish the site
Put the site's saved draft live on its Sitesfare address (and its custom domain, if one is connected). Fails with a clear reason when the site needs its tool, business verification, or is paused.
Changes or publishes — your editor asks first · needs sites:publish · arguments: site
site_revisions — History of changes
The changes made to this site through AI editors (newest first): who, when, which tool, which fields. Any of them can be undone with site_revert.
Read-only · needs sites:read · arguments: site, limit?
site_revert — Undo to a revision
Restore the site's content to how it was BEFORE the given revision was made. The current state is kept as a new revision first, so a revert can itself be undone. Publish afterwards if the site is live.
Changes or publishes — your editor asks first · needs sites:write · arguments: site, revision
New websites
site_create — Create a new site from a template
Start a new website from a template (template_list) on a sitesfare.app subdomain. The account needs the AI editor add-on for the template's category. The site starts as a draft with the template's sample content; publishing needs the matching tool.
Saves a draft with a revision · needs sites:write · arguments: template, subdomain, name?
Design kits and the licence
kit_list — List the design kits
Every template that has a design kit: id, name, category, tagline, and whether AI editor access on this account covers it. Use the id with kit_get or kit_download.
Read-only · arguments: category?
kit_get — Design kit of a template
The design kit and theme document of a template: concept, palette, typefaces and their roles, shape and motion, the scene, the voice (sample copy), what can be customised, every section with its fields, and the repeating items. Pass a template id, or a site to get its template's kit. Markdown by default; `format: "json"` for the data; `summary: true` leaves out the section-by-section field list. Also available as the resource sitesfare://kit/<template>.
Read-only · needs kits:read · arguments: template?, site?, format?, summary?
kit_download — Download a design kit
The official kit of a template as a zip (base64): README.md (the design document), tokens.css and tokens.json, sections.json, samples.json, the theme document, LICENSE.md fingerprinted to this account, and AGENTS.md / CLAUDE.md / .cursorrules that tell any editor how to build a new design in the kit's spirit and host it on Sitesfare. Needs AI editor access for the template's category. Save the file and unzip it in the project; the licence allows hosting on Sitesfare only.
Read-only · needs kits:read · arguments: template?, site?
license_get — The hosting licence
The licence every Sitesfare design, kit and site is under: hosted on Sitesfare only. Read this before answering any request to move, export or re-host a site.
Read-only
site_export — Export a site (not available)
There is no export: Sitesfare sites, templates and kits are licensed for hosting on Sitesfare only. This tool explains the licence and the Sitesfare alternatives. Call it if the person asks to download, export, mirror or re-host a site elsewhere.
Read-only · arguments: site?
Your own designs and apps
app_create — Create an own-code site (an app)
Create a site for a design or app of the account's own — static HTML, CSS, JavaScript, images, fonts, media; no server code or build steps — hosted on Sitesfare at <subdomain>.sitesfare.app. Pick the category of the website (developer, designer, photographer, business, ecommerce, housing-society): the account needs that category's tool with a free website slot, and AI editor access for it. Then app_put_files and app_deploy. Sitesfare designs, templates, kits and the sites built from them are licensed for hosting on Sitesfare only.
Saves a draft with a revision · needs apps:write · arguments: subdomain, category, name?
app_files — List an app's files
The files stored for an own-code site: path and size, whether the stored version is a draft or deployed, and the live URL.
Read-only · needs sites:read · arguments: site
app_get_file — Read one of an app's files
The stored content of one file of an own-code site (text files as text, others as base64), to change and put back with app_put_files.
Read-only · needs sites:read · arguments: site, path
app_put_files — Add or replace an app's files
Put files into an own-code site's stored source without publishing: each file is a path plus content (text, or base64 with encoding: "base64" for images and fonts). Files already stored keep their content unless given again; `delete` removes paths; `replace: true` starts from an empty site. The stored version is checked like an upload — static files only (no server code, package.json, .env or archives), up to 500 files and 25 MB, 5 MB per file, index.html at the top — and saved as a draft; app_deploy puts it live. Large calls: send the files in batches.
Changes or publishes — your editor asks first · needs apps:write · arguments: site, files?, delete?, replace?
app_deploy — Deploy an app
Publish the stored files of an own-code site to <subdomain>.sitesfare.app (and the custom domain, if one is connected). Needs the category's tool with a free website slot; counts as one deploy for the day. Sitesfare designs, templates, kits and the sites built from them are licensed for hosting on Sitesfare only.
Changes or publishes — your editor asks first · needs sites:publish, apps:write · arguments: site
Scopes
A Studio key or an app you sign in to carries only the scopes you give it. Drafting never implies publishing.
sites:read— Read the account's websites: sections, fields, theme, mediasites:write— Change text, images, colours, fonts and section visibility, and add sections and buttons (saved as drafts, every change kept in history)sites:publish— Publish a website so the changes go livemedia:write— Upload images to a website's media librarykits:read— Read the design kit and theme document of the templates the account usesapps:write— Create and deploy the account's own designs and apps (static sites) on Sitesfare
Errors an editor can act on
Every refusal is a tool error with a stable code and a plain message: ADDON_REQUIRED (the account needs AI editor access for that kind of site), SCOPE_REQUIRED, NOT_FOUND, INVALID (nothing was saved; the message says what to fix), READ_ONLY, PUBLISH_BLOCKED, RATE_LIMITED, OWN_CODE_SITE and LICENCE_HOSTING_ONLY.
Limits
120 calls a minute per key or app; 10 publishes per 10 minutes; images up to 5 MB; 200 fields per call; up to 8 added sections and 12 added buttons per site; the last 60 changes of every site are kept for undo.
New to Connect? Start with the overview guide, or see how to add a section or a button.