Connect Claude to your SeedWebs site

Before you start

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

The site is on a paid plan

Seed, Pro, or Business. A site still on its trial, or on an expired plan, is refused at the last step with “That site is on a plan without API access.”

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 Claude plan includes custom connectors

This is on Claude’s side, not ours. If there is no “Add custom connector” option in step 1, that is the reason.

How to connect

Steps 1 to 3 happen in Claude. Steps 4 to 6 happen in a browser tab that Claude opens.

1. 1

   Open the connector settings

   In Claude, go to Settings → Connectors and choose Add custom connector.

2. 2

   Paste the SeedWebs URL

   Every SeedWebs site uses this same address. Which site you connect is decided later, when you sign in.

   https://mcp.seedwebs.app/mcp
3. 3

   Click Connect

   Claude opens a SeedWebs page in your browser.

4. 4

   Sign in with Google

   Use the Google account you sign in to your site’s admin with. SeedWebs passes this step to Google, so no password is typed on our page, and Claude does not see one either.

5. 5

   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.

6. 6

   Click Authorize

   Claude finishes the connection and lists the SeedWebs tools. Ask it “what pages does my site have?” to confirm it works.

Don’t leave the flow open too long: about five minutes on the Google screen, ten minutes overall. Past that the page says the login or session expired, and you start again from Claude.

Connections are listed under Tools → Connected Apps in your site admin. 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, run steps 1 to 6 again with the same URL and pick the other slug. Each connection covers one site.

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 is on a plan without API access.”

The site is on a trial or expired plan. Pick a paid plan and try again.

“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.

“Session expired” or “Login expired”

The flow sat open too long. Start it again from Claude.

Claude works with your permissions

Whoever connects gives Claude their own role on that site. It cannot do anything you couldn’t do yourself in the admin.

Admin

Content and themes. 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. No theme changes.

Writer

Their own drafts, matching the writer rules in the admin. No publishing, no theme changes.

What Claude can do

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. Claude 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 Claude to make a theme of its own first.

Security

Claude doesn’t see your password

Signing in happens on Google’s own page. Claude ends up with an access token and nothing else, and SeedWebs never handles your Google password either.

Standard OAuth 2.1, with PKCE

The same authorization standard the other connectors in Claude use. Nothing about the sign-in step is specific to us.

Access is short-lived

Tokens last an hour, and Claude 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.

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.

Connections can lapse

One left unused for 90 days stops working, and occasionally Claude will report a connection as revoked. Nothing on your site changes — run the six steps again to reconnect.

For developers

For Claude Code, scripts or CI, skip OAuth and point a personal access token at your site’s own endpoint. The paid-plan requirement is the same.

1. In the site admin, go to Tools → API Tokens and create one. 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. Register the site’s MCP endpoint with it:

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

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.