TH SeedWebs
Help

Connect an AI assistant to your SeedWebs site (MCP)

SeedWebs runs an MCP server, the open standard AI apps use to work with other services. Connect your AI app to it and the app can read and manage your site for you: writing pages, importing content in batches, building themes and adding images. You sign in once and approve the site it may reach.

Works with Claude, ChatGPT, Cursor, GitHub Copilot in VS Code and n8n. Setup takes a few minutes and nothing is installed on your site.

The address every app uses

Every SeedWebs site connects through this one address. Which site you connect is decided later, when you sign in.

https://mcp.seedwebs.app/mcp

Once you have added the address to your app, signing in looks the same in every app:

  1. Your app opens a SeedWebs page

    It opens in your browser, or in a window inside the app.

  2. Sign in with Google

    Use the Google account you sign in to your site’s admin with. Google handles this step, so no password is typed on our page and your AI app never sees one.

  3. Choose the site

    Pick it from the sites on your account — the search box narrows the list. If a site isn’t listed, type its slug in the same box: the part before .seedwebs.app, so mysite for mysite.seedwebs.app. It stays the same even if your public site uses your own domain.

  4. Check the summary and click Authorize

    The last step shows the app, the site, your role on it, your account, what the app may do there and where you’ll be sent back. Your app then finishes the connection and lists the SeedWebs tools. Ask it “what pages does my site have?” to confirm it works.

Don’t leave the sign-in open too long: about five minutes on the Google screen, ten minutes overall. Past that the page says “Connection request expired” or “Sign-in expired” (“Login link already used” if the Google screen sat too long), and you start again from your app.

Connections are listed under Tools → Connected Apps in your site admin, where you can also disconnect them. That page is admin-only — if you connected as an editor or writer, ask an admin to manage it for you.

To connect a second site, add the same address again under another name and pick the other slug. Each connection covers one site.

Apps and automations that can’t sign in this way can use an API token with your site’s own address instead. See Use an API token instead.

Before you start

Three things have to be true, or the connection will fail partway through.

The site’s trial has not run out
The trial and all three paid plans can connect. Only a site whose trial has ended is refused, when you choose it, with “AI app access is not active on that site.” Choosing a plan lifts the block: SeedWebs does not revoke the connection itself, so nothing is lost on our side, though your app may still ask you to connect again.
You have an account on that site
The connector checks the Google address you sign in with against the site’s own users. Quickest way to be sure: sign in at {slug}.seedwebs.app/admin with that account first. If that works, the connector will accept you.
Your app can add a remote MCP server
This is decided by the app, and by your plan with it. Each app’s section below says which plans can.

Set up your app

Pick your app. Each section shows where the address goes; the sign-in after that is the one described above.

Claude

Every Claude plan can add custom connectors; Free can add one. On Team and Enterprise, only an Owner can add it, for the whole organization, and each member then connects it.

  1. In Claude, go to Customize → Connectors, click + Add and choose Add custom connector.
  2. Give it a name (SeedWebs, say), paste the address as the URL and click Continue.
    https://mcp.seedwebs.app/mcp
  3. Click Continue again on the sign-in settings Claude found, choose Sign in now under Authentication, then click Add.
  4. In the page Claude opens, sign in, choose the site and click Authorize.

On Team or Enterprise, an Owner adds it under Organization settings → Connectors (Add → Custom → Web) with the same name and address. Each member then goes to Customize → Connectors, finds SeedWebs and clicks Connect.

Claude Code and scripts can use an API token instead. See Use an API token instead.

ChatGPT

Adding a custom MCP server that can change your site needs ChatGPT Business, Enterprise or Edu, on the web. On Business, only workspace admins and owners can add one; on Enterprise and Edu, so can members an admin has given “Create plugins with MCPs”. ChatGPT Pro is limited to reading and fetching, and we have not tested it with SeedWebs. OpenAI does not list Plus or Free as able to add one.

  1. Open ChatGPT on the web, go to Plugins, click + and choose Add custom MCP server.
  2. Give it a name (SeedWebs, say), paste the address as the URL, and set Authentication to OAuth. No client ID is needed.
    https://mcp.seedwebs.app/mcp
  3. Confirm the warning with I understand and want to continue and click Create as a plugin. Then sign in, choose the site and click Authorize.
  4. In a new chat, type @ and choose SeedWebs.
  5. If others in your workspace need it, publish it to the workspace.

From the Plugins list instead

If ChatGPT lists SeedWebs under Plugins, in the Plugins Directory or because a workspace admin published it to your workspace, install it from there. The first time you use it, the SeedWebs sign-in opens: sign in, choose the site and click Authorize. It is the same connection as the custom server above, with the same tools.

ChatGPT asks you to confirm before it runs a tool that changes your site.

Cursor

If your company manages Cursor for you, an admin may need to allow the server first.

  1. Add SeedWebs to ~/.cursor/mcp.json (every project) or to .cursor/mcp.json in one project:
    {
      "mcpServers": {
        "seedwebs": {
          "url": "https://mcp.seedwebs.app/mcp"
        }
      }
    }
  2. Open Customize in Cursor’s sidebar (Settings → Tools & MCP in older versions), find seedwebs and sign in; Cursor opens your browser. Choose the site and click Authorize.

With an API token instead

Point it at your site’s own address and send the token in a header. Cursor fills in ${env:SEEDWEBS_TOKEN} from your environment, so set a SEEDWEBS_TOKEN environment variable to the token rather than writing the token into the file:

{
  "mcpServers": {
    "seedwebs": {
      "url": "https://{slug}.seedwebs.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:SEEDWEBS_TOKEN}"
      }
    }
  }
}

VS Code with GitHub Copilot

Copilot Free, Pro and Pro+ can use it straight away. On Copilot Business or Enterprise, an organization or enterprise owner first has to turn on the “MCP servers in Copilot” policy.

  1. Open the Command Palette and run MCP: Add Server. Choose HTTP, paste the address, and name it seedwebs.
    https://mcp.seedwebs.app/mcp
  2. Or add it to .vscode/mcp.json in your project:
    {
      "servers": {
        "seedwebs": {
          "type": "http",
          "url": "https://mcp.seedwebs.app/mcp"
        }
      }
    }
  3. VS Code opens your browser to sign in. Choose the site and click Authorize.
  4. Open Copilot Chat in Agent mode to use the SeedWebs tools.

With an API token instead

VS Code asks for the token the first time it connects and stores it securely, so the token is never written into the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "seedwebs-token",
      "description": "SeedWebs API token",
      "password": true
    }
  ],
  "servers": {
    "seedwebs": {
      "type": "http",
      "url": "https://{slug}.seedwebs.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:seedwebs-token}"
      }
    }
  }
}

n8n

For AI Agent workflows. Needs the MCP Client Tool node at version 1.2 or later.

  1. In your AI Agent node, add the tool MCP Client Tool.
  2. Set Server Transport to HTTP Streamable, and Endpoint to your site’s own address:
    https://{slug}.seedwebs.app/api/mcp
  3. Set Authentication to Bearer Auth and create a credential holding an API token from your site (the sw_pat_… value on its own). A token suits automations best: it keeps working until it expires, you revoke it, the trial ends, or the person who created it is removed from the site or deactivated, with nobody signing in again.

With sign-in (OAuth) instead

Set Endpoint to the shared address, set Authentication to MCP OAuth2 with Dynamic Client Registration on, then sign in, choose the site and click Authorize.

https://mcp.seedwebs.app/mcp

A self-hosted n8n that you open over plain http:// on a local network address cannot use the sign-in option. Use the API token.

Other apps

Other apps that can add a remote MCP server with OAuth, or with an Authorization header, will probably work too, but we have not tested them. Give them the shared address above to sign in, or your site’s own address with an API token.

Use an API token instead

For scripts, CI, automations such as n8n, Claude Code, or any app that takes a header instead of signing in, skip the sign-in and point a personal access token at your site’s own address. The plan rules are the same.

  1. In the site admin, go to Tools → API Tokens and create one, choosing its role. This is admin-only, and a token can’t be given a higher role than your own. The sw_pat_… value is shown once.
  2. Use your site’s own MCP address and send the token in the Authorization header:
URL:     https://{slug}.seedwebs.app/api/mcp
Header:  Authorization: Bearer sw_pat_xxxxxxxx

For example, in Claude Code:

claude mcp add --transport http seedwebs \
  https://{slug}.seedwebs.app/api/mcp \
  --header "Authorization: Bearer sw_pat_xxxxxxxx"

A token lasts up to a year; revoke it on the same page if it leaks. The same token works against the REST API at https://{slug}.seedwebs.app/api, which also takes file uploads straight from a script. Email us for the full API reference. A token follows the same rule, with the same four exceptions (stock counts, files it uploads, moving files to the Trash and images’ alt text): over MCP it makes Publish requests like a connected app, and over the REST API a change visitors would see answers 403 confirmation_required, as do sending a newsletter and an email. For a script you trust, an admin, signed in, can turn on Publishes without confirmation for that token on the same page: its writes then go live at once. An address any token adds to Subscribers waits as Pending until an admin activates it.

If it doesn’t work

“your@email is not a member of "yoursite".”
That Google address isn’t a user on that site. Either you signed in with the wrong account, or an admin needs to add you under Settings → Users.
“AI app access is not active on that site.”
The site’s trial ran out. Pick a plan at seedwebs.com and try again — the trial itself can connect, so this only appears once it is over.
“No site found with slug …”
The slug is wrong. Check the address you use for the admin — that is the slug, even when the public site runs on your own domain.
“Connection request expired”, “Sign-in expired” or “Login link already used”
The sign-in sat open too long. Start it again from your app.

Your AI app works with your permissions

Whoever connects gives the app their own role on that site. It cannot do anything you couldn’t do yourself in the admin. A change it makes that visitors would see waits for a person to approve it (see Ask you before a change goes live, below), except stock counts, files it uploads (anyone can open them at their URL), moving files to the Trash and images’ alt text, which take effect at once. With an API token, the app gets the role chosen for that token, never more than its creator’s current role. Every app that signs in gets the same tools, whichever app it is; form submissions and the member signup form are read only with an API token.

Admin
Content, themes, menus, the site name, tagline, logo and favicon. The app prepares and you approve: drafts, Pending changes and themes visitors don’t see yet are written at once, and anything else visitors would see — publishing a draft, an edit of a published product, a menu, the site name or logo, the live theme — comes back as a Publish request you approve in the admin. Super admins are stepped down to admin for the connection, and there is no tool for site-level actions like Reset in any case.
Editor
Content across the site. Drafts are written at once and edits to a published post or page wait as Pending changes; publishing a draft, an edit of a published product (or event, book, doc or staff profile), or a move of a published item to draft or to the trash comes back as a Publish request an editor or admin approves in the admin. It can read your menus. No theme or menu changes, and no change to the site name, logo or favicon.
Writer
Their own drafts, and Pending changes on their own published posts and pages, matching the writer rules in the admin. Publishing their own draft comes back as a Publish request an editor or admin approves. No theme changes.

What a connected app can do

Ask you before a change goes live

When the app prepares a change visitors would see, it answers with a link to a Publish request in your admin; Tools → Publish requests lists them, with a count of those waiting for you. The page shows what would change: the text before and after, screenshots for a Theme, and a link that shows your site with the change for 24 hours where it can (a draft going live, Pending changes, a Theme Publish). Press Approve and publish to make it, or Decline. Whoever may make that change in the admin may approve it — an editor approves content, an admin anything — and whoever asked may decline it. If the page, menu or theme changed after the app asked, the request is stale and nothing is written: ask the app to prepare it again. A request expires after 7 days, and Logs → Activity records each request, who decided it and which app asked. Drafts, Pending changes and stock counts need no approval, and neither do files it uploads (anyone can open them at their URL), moving files to the Trash or images’ alt text.

Bring content over from an old site

Give the app the address of a WordPress site and it can rebuild the posts and pages here, up to 50 at a time. Re-running a batch that stopped halfway won’t duplicate anything.

Build or port a theme

The app can create a theme and write its headers, footers, templates and cards at once, in a theme of its own that visitors don’t see yet, so the default one stays intact as a fallback. Making it live is a Publish request you approve.

Change your header, footer and CSS

Ask for a new logo in the header, a matching footer, or a style tweak for mobile, and the app reads your theme’s header, footer and CSS and prepares the edit. On the theme your visitors see, it asks you with a Publish request; once you approve it, the change shows on your live site within about a minute, and Logs → Activity lists which parts it changed. The default theme is never edited: on a site still using it, the app first makes its own copy and asks you to activate it. Admin connections only.

Change the site name, tagline, logo and favicon

With an admin connection, the app can ask to rename the site, change the tagline, and set the logo and the browser-tab icon to an image it added to your media library (the update_site_identity tool); the change is made when you approve its Publish request. If your theme’s header shows the site logo, the new logo appears there within about a minute, with no HTML edit. These are the same settings as Settings → General in the admin; the app changes only the ones you ask for.

Switch your Store on

With an admin connection, on the free trial, Pro or Business, the app can ask to switch your Store on (the open_store tool), so your published products show on your site. The Store comes on when you approve its Publish request; a product the app added that is still waiting on its own Publish request shows once you approve that one too. Checkout and payments stay as they are, and only you switch checkout on in the admin. While the Store is on, the site cannot move to the Seed plan, which has no Store.

Read and change your menus

With an editor or admin connection, the app can read your menus and tell you which items the public menu hides and why — a link to a page that isn’t published yet, for one. With an admin connection it can also prepare a new version of a menu — its items, their order and their links — which you approve as a Publish request. Once approved, the change shows on your live site within about a minute, and it can be undone for 30 days like a content change.

See a page before anyone else does

With an editor or admin connection, the app can preview any page of your site: a screenshot at desktop width and one at phone width, plus a short check for problems you might miss — a page that scrolls sideways on a phone, images that do not load, styles that are missing, text that is hard to read. It shows drafts too, marked with a “Draft” label so you can tell them apart, and works while your site is in maintenance mode or coming soon. Visitors never see a draft. The app gets screenshots only, never a link: a link you can share for 24 hours is on a Publish request’s page, where it shows that change. Each site has 100 previews a day (Thai time).

Write and update content in batches

Posts, pages, products, events, books, docs and staff profiles. Products and translations work on the free trial, Pro and Business (not Seed). Products show on your site once they are published and the Store is on (Settings → General → Features, or approve the app’s open_store request): a product still waiting on its Publish request shows once you approve that too. Translations link up by tagging items with a language and a shared translation group.

  • Write in batches What the app creates in a batch is a draft, with a preview link and an edit link so you can review it; asked to publish, it sends you a Publish request as well.
  • Change existing items A batch can also update an item it created earlier: if that item has been published since, a change to a post or page waits as Pending changes, and any other change visitors would see goes into the Publish request. The app can also change an existing post, page or product in place: a stock count at once, a published product’s price or other fields through a Publish request.
  • Undo Every content change can be undone for 30 days (the undo_change_set tool, or Settings → Theme versions in the admin), except stock counts and Pending changes (discard those in the admin); the app’s undo of a change visitors see is itself a Publish request. A Publish of Pending changes, or a move to draft or trash that applies them, has no undo when it writes a slug, a date or a byline: the page’s History in the admin brings the earlier content back. An edit of a draft that still holds Pending changes applies them too, and its undo puts back everything but the slug, date or byline they wrote.

Read the site before changing it

The app can read your site name, tagline, logo and favicon, plan, default language, active theme, your posts, pages and products (one at a time by id, slug or SKU, with the time it last changed, which a change sends back), your forms, your theme’s header, footer and CSS, and the markup of a template it is about to edit.

Read form submissions and the member signup form, with an API token

Form submissions and the member signup form are read only with an API token: an app that signs in gets neither, because what visitors send is their own words and the sign-in page does not ask to share it. With an editor or admin token, the app can list and read what visitors sent through your forms (the answers, whether the emails went out, and the names of any uploaded files, whose contents it downloads over the REST API), and read the form members fill in once after their first sign-in. That form is changed in Members → Signup form in the admin, or by a token an admin marked Publishes without confirmation. Members are on the Trial and Business plans.

Add an image from a link, or from your computer

The app can copy a file into your media library from a public link, and ChatGPT can often pass on a file you attached to the chat. For a picture on your computer, or an attachment your app doesn’t pass on (Claude doesn’t), the app gives you an upload link instead: open it, pick the files in your site’s admin (signed in as yourself), and tell the app you’re done, it then finds them. Up to 20 MB per copy, the same file types as the Media page, counted against your storage plan. It can also search the library for images you already uploaded, and move files you no longer use to the media Trash: a file stays online until the Trash is emptied, and Media → Trash in the admin restores it. It can set an image’s alt text too (what the image shows, for search engines and screen readers), which takes effect at once: on a site on Themes, pages show it within a day. A writer’s connection changes and moves only files that person uploaded.

Clear the site cache

With an admin connection the app can clear your site’s cache, as Clear cache / Rebuild site on Settings → General: every page renders fresh on its next visit. Its own edits already show within about a minute, so it needs this only for a page that keeps showing old content, and it can do it up to 10 times an hour.

Moving a whole WordPress site? Use the Move to SeedWebs plugin (beta), see Move from WordPress, or export a WXR file and use Tools → Import / Export in the admin instead — either brings images, categories, tags and authors across as well. An AI app is the better tool when you want the content reshaped on the way in rather than copied as-is.

What it can’t do

These stay in the admin.

  • Make a change visitors would see without a person’s approval (above), except a live product’s stock count, a file it uploads, moving a file to the Trash and an image’s alt text, which take effect at once; or send a newsletter or email, which are sent from the admin. Scheduling a publish is yours too: the app asks you to set the time in the item’s Schedule box in the admin, and if it later edits an item you scheduled, the schedule is cancelled and you get an email.
  • Take a file you attached to the chat when your app doesn’t pass it on — Claude doesn’t, and ChatGPT sometimes doesn’t: you pick the file again on the upload link the app gives you.
  • Delete content or media for good, empty the trash, or reset a site. With an editor or admin connection it can move a draft to the trash, and ask with a Publish request to move a published post, page or product there; an undo brings it back (a row that was published comes back live through a Publish request), except a published post or page whose move to the trash applied Pending changes that wrote a date or a byline: restore it from the Trash tab in the admin (it comes back as a draft), and its History brings the earlier content back. An admin connection can still delete a theme part, or remove a font from a theme (on the live theme, once you approve it), and that has no undo.
  • Change settings other than the site name, tagline, logo and favicon, switching the Store on, the theme and the menus (each through a Publish request) — users, redirects and checkout included.
  • Create categories, tags or authors. It can file content under ones that already exist, so set those up first.
  • Read events, books, docs or staff profiles back. It can write them in batches, but only posts, pages, products and form definitions can be listed and read.
  • Reach another site, even one you own. Each connection is bound to the site you approved.
  • Edit the default theme, or delete its built-in parts. The tools refuse and tell the app to make a theme of its own first.

Security

What an AI app or token prepares waits for a person, with four exceptions
A change an AI app or token prepares goes live only when someone who may make it in the admin approves it there, signed in, on the request’s own page. A connected AI app can never skip that. An API token can only once an admin, signed in, marks it Publishes without confirmation on Tools → API Tokens. Four things take effect at once either way: stock counts on live products, files it uploads (anyone can open them at their URL), moving files to the Trash and images’ alt text.
Your AI app doesn’t see your password
Signing in happens on Google’s own page. The app ends up with an access token and nothing else, and SeedWebs never handles your Google password either.
Standard OAuth 2.1, with PKCE
The authorization standard MCP apps use for remote servers. Nothing about the sign-in step is specific to us.
Access is short-lived
Tokens last an hour, and the app renews them in the background. Every request re-checks that you still have access to the site and that the connection is still on, so removing someone from the site’s users stops their connection at its next request.
You can disconnect at any time
Revoke from Tools → Connected Apps. The app is cut off at its next request; connect it again to keep using it. An API token is revoked on Tools → API Tokens and stops working at once.
Bound to one site
Each token is tied to the site it was approved for and cannot be pointed at another, yours or anyone else’s.
What the app reads goes to its provider
Content the app reads, and form answers an app reads with an API token, are sent to the company that runs the app and to the AI model it uses, under that company’s terms. Choose who connects (the app gets their role), or the role of the token, with that in mind.
Connections can lapse
One left unused for 90 days stops working, and occasionally an app will report a connection as revoked. Nothing on your site changes — connect again from your app.

Need help

Write to us at [email protected]

Read the Terms of Service and Privacy Policy