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 reading what visitors send through your forms. 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:

Your app opens a SeedWebs page

It opens in your browser, or in a window inside the app.
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.
Choose the site

Type the site’s slug — the part before .seedwebs.app. For mysite.seedwebs.app the slug is mysite. It stays the same even if your public site uses your own domain. Sites on your account are suggested as you type, but you can type any slug.
Click Authorize

Your app 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, at the last step, with “That site’s trial has ended.” 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
ChatGPT
Cursor
VS Code with GitHub Copilot
n8n
Use an API token instead

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.

In Claude, go to Customize → Connectors, click + Add and choose Add custom connector.
Give it a name (SeedWebs, say), paste the address as the URL and click Continue.
```
https://mcp.seedwebs.app/mcp
```
Click Continue again on the sign-in settings Claude found, choose Sign in now under Authentication, then click Add.
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.

Open ChatGPT on the web, go to Plugins, click + and choose Add custom MCP server.
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
```
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.
In a new chat, type @ and choose SeedWebs.
If others in your workspace need it, publish it to the workspace.

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.

Add SeedWebs to ~/.cursor/mcp.json (every project) or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "seedwebs": {
      "url": "https://mcp.seedwebs.app/mcp"
    }
  }
}

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.

Open the Command Palette and run MCP: Add Server. Choose HTTP, paste the address, and name it seedwebs.
```
https://mcp.seedwebs.app/mcp
```

Or add it to .vscode/mcp.json in your project:

{
  "servers": {
    "seedwebs": {
      "type": "http",
      "url": "https://mcp.seedwebs.app/mcp"
    }
  }
}

VS Code opens your browser to sign in. Choose the site and click Authorize.
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.

In your AI Agent node, add the tool MCP Client Tool.
Set Server Transport to HTTP Streamable, and Endpoint to your site’s own address:
```
https://{slug}.seedwebs.app/api/mcp
```
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, or the trial ends, 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.

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.
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 does handle media uploads. Email us for the full API reference.

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.
“That site’s trial has ended.”: The 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. With an API token, the app gets the role chosen for that token.

Admin: Content, themes and form submissions. 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, and form submissions. No theme changes.
Writer: Their own drafts, matching the writer rules in the admin. No publishing, no theme changes, no form submissions.

What a connected app can do

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, write its headers, footers, templates and cards, then make it live. It works in a theme of its own, so the default one stays intact as a fallback.

Write and update content in batches

Posts, pages, events, books, docs and staff profiles. Products and translations need Pro or Business, where the store and extra languages are part of the plan — translations link up by tagging items with a language and a shared translation group.

Read the site before changing it

The app can read your site name, plan, default language, active theme, the list of posts and pages, your forms, and the markup of a template it is about to edit.

Read form submissions

If you connect as an editor or admin, 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. File contents aren’t sent over MCP; an app using an API token can still download them over the REST API. A writer’s connection can’t read submissions.

Moving a whole WordPress site? Export a WXR file and use Tools → Import / Export in the admin instead — that 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.

Upload images or files.
Delete posts and pages, empty the trash, or reset a site.
Change settings, users, menus, or redirects.
Create categories, tags or authors. It can file content under ones that already exist, so set those up first.
Read products, events, books or docs back. It can write them in batches, but only posts and pages 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. The tools refuse it and tell the app to make a theme of its own first.

Security

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. Each renewal re-checks that you still have access to the site, so removing someone from the site’s users stops their connection renewing.
You can disconnect at any time: Revoke from Tools → Connected Apps. Renewal stops at once, but work already in flight can run until its token expires, up to an hour. 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 and form answers the app reads are sent to the company that runs the app and to the AI model it uses, under that company’s terms. Choose the role you connect with, 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

The address every app uses

Your app opens a SeedWebs page

Sign in with Google

Choose the site

Click Authorize

Before you start

Set up your app

Claude

ChatGPT

Cursor

With an API token instead

VS Code with GitHub Copilot

With an API token instead

n8n

With sign-in (OAuth) instead

Other apps

Use an API token instead

If it doesn’t work

Your AI app works with your permissions

What a connected app can do

Bring content over from an old site

Build or port a theme

Write and update content in batches

Read the site before changing it

Read form submissions

What it can’t do

Security

Need help