TH SeedWebs
Documentation

Connect an AI assistant (MCP)

Connect Claude, ChatGPT, Cursor, GitHub Copilot in VS Code or n8n to your site over MCP, or use an API token, and how to disconnect.

Last updated 2026-11-20

An MCP AI app acts with your role. A change it makes that visitors would see waits for a person’s approval, except stock counts, files it uploads (public at their URL), moving files to the Trash and images’ alt text.

  • Saved at once: drafts (new items come with preview and edit links), its edits of a published post or page, which are saved as Pending changes, stock counts and images’ alt text.
  • Needs a person’s approval: anything else visitors would see, which the app asks for with a Publish request: publishing or unpublishing an item, a live product’s price or other fields, a menu, the site name, tagline, logo or favicon, switching the Store on (admin; trial, Pro, Business), the active theme or its fonts, a Theme Publish or Rollback, an undo of a live change.
  • Can also: make and edit themes that are not live (header/footer/CSS; admin), read menus (editors), add images (from a link, a ChatGPT attachment when passed on, or an upload link), set their alt text (update_media; Themes pages show it within a day) or move them to the media Trash (writers: own files only), clear the site cache (admin, 10/hour) and screenshot pages with visual checks (preview, 100/day, no link; editor+), but not change other settings.

Content and menu edits can be undone for 30 days (undo_change_set, Settings → Theme versions), except Pending changes; a write of them that sets a slug, date or byline has no undo on a live item (see History), and on one not live its undo puts back all but those three; theme, image, site name/logo, stock edits can’t. All plans and trials. Full guide.

On a site on Themes, Settings → Theme versions (admins) lists each published Theme version, newest first, with its screenshots, who approved it and which app asked; Live marks the one visitors see, and Rollback makes an earlier one live again. It deletes nothing and leaves the Theme draft and content as they are. The page also shows the draft’s unpublished changes; to throw them away, ask your AI app to reset the draft (reset_draft, back to the live version or one you name).

Approve what your AI app asks

A Publish request comes as a link to its page in your admin; Tools → Publish requests lists them, with a count of those waiting for you. The page shows what would change, screenshots for a Theme, and a 24 h preview link where it shows the change (a draft going live, Pending changes, a Theme Publish). Press Approve and publish or Decline. Whoever may make that change in the admin may approve it (an editor content, an admin anything); whoever asked may decline it. Nothing is live before that. A request whose page, menu or theme changed since is stale: ask the app to prepare it again. A request expires after 7 days, and Logs → Activity names each one, who decided it and which app asked.

Sign in (OAuth)

Add https://mcp.seedwebs.app/mcp to your app, sign in with the Google account you use in the admin, pick your site (or type its slug) and press Authorize.

  • Claude: Customize → Connectors → + Add → Add custom connector (Team/Enterprise: an Owner adds it, members Connect).
  • ChatGPT: if Plugins lists SeedWebs (the Plugins Directory, or your workspace), install it there. Otherwise (web; Business, Enterprise, Edu): Plugins → + → Add custom MCP server → Create as a plugin.
  • Cursor: "url" in ~/.cursor/mcp.json, sign in under Customize.
  • VS Code + Copilot: MCP: Add Server → HTTP, Agent mode (Business/Enterprise: org policy).
  • n8n: MCP Client Tool, MCP OAuth2 (not plain http:// on a LAN).

Other MCP apps may work. Every app that signs in gets the same tools: form entries and the member signup form are read only with an API token (below).

API token instead

For Claude Code, scripts, n8n: create one at Tools → API Tokens (admins) and send Authorization: Bearer sw_pat_… to https://{slug}.seedwebs.app/api/mcp (n8n: Bearer Auth). Its role is at most yours and drops if yours does; at editor or admin it also reads form entries and the member signup form. It follows the same rule, with the same four exceptions (stock counts, uploaded files, moving files to the Trash, images’ alt text): over MCP it makes Publish requests; over the REST API a change visitors would see is refused (403 confirmation_required), and so is sending a newsletter or email. An admin, signed in, can turn on Publishes without confirmation for a token they trust; it then publishes at once (over MCP, its edits of a published post or page still arrive as Pending changes it may publish). AI apps and tokens without this ask a person to confirm each change visitors would see, except stock counts, uploaded files, moving files to the Trash and images’ alt text. Restoring a backup brings back the tokens and marks it holds — check this list after a restore. An address any token adds to Subscribers waits as Pending until an admin activates it. If such an app or token edits an item you scheduled to publish, the schedule is cancelled, you get an email, and the item’s Schedule publish box names the app or token.

Disconnect

Tools → Connected Apps for sign-ins, Tools → API Tokens for tokens. After a trial both pause until a plan is chosen. What the app reads goes to its maker.