Which ChatGPT plans can do what
Plan limits come first, so nobody gets stuck at step 5.
| Plan | Connect a custom MCP server | Write actions (changes) |
|---|---|---|
| Business | Yes admins and owners | Yes beta |
| Enterprise, Edu | Yes admins and owners, plus members given permission | Yes beta |
| Pro | Yes | Read only read and fetch only |
| Plus, Free | Not stated by OpenAI | Not stated |
From OpenAI’s help center, 30 October 2026.
I’d rather you read this table now than find out at step 5. If your plan is read-only, ChatGPT is still a good auditor, and Claude, Cursor or Codex can make the changes.
01Before you start
- AgentedSEO is active (WordPress 6.9 or later, PHP 8.1 or later), and you are an administrator.
- The site is on public HTTPS. ChatGPT connects from OpenAI’s side, so localhost, VPN-only and password-protected staging sites won’t connect.
- The site answers
/.well-known/oauth-authorization-serverand/.well-known/oauth-protected-resourceat the domain root. - Run AgentedSEO › Agents › Connections › Test the connection › Run test. Both OAuth discovery checks and “MCP endpoint asks clients to sign in” must pass.
02Copy your connector URL
- Open AgentedSEO › Agents › Connections.
- Under Connect an agent choose Claude.ai or ChatGPT.
- Copy the URL under Copy your site’s connector URL.
https://your-site.com/wp-json/agentedseo/mcp03Add the ChatGPT WordPress MCP connection
Current path: Plugins
- In ChatGPT on the web, go to Plugins.
- Select the plus button, then Add custom MCP server.
- Name:
AgentedSEO. - Under Connection, paste your connector URL.
- Choose OAuth for authentication.
- Read the risk warning, tick I understand and want to continue.
- Select Create as a plugin. ChatGPT sends you to your site to sign in, then shows the tools it found.
Older path: Apps
If your account still shows it: turn on developer mode in Settings › Apps › Advanced settings, then Apps › Create, give the endpoint, pick OAuth, Scan Tools, sign in when asked, Create. The app shows with a Dev label.
On Business, Enterprise and Edu an admin can publish the connection for the workspace after testing. Each person still signs in on their own.
04Approve it on your site
- If you are not signed in, WordPress asks you to sign in first.
- The page asks “Connect ChatGPT to AgentedSEO?” and says the client signs in as an SEO Agent user that works through AgentedSEO only, under your approval rules.
- Click Approve. Deny sends it back with nothing created.
ChatGPT’s user shows under Connected agents with its own Revoke. Access tokens last one hour, refresh tokens 30 days, and they rotate.
05Use it in a chat
Start a new conversation, type @ and pick AgentedSEO. ChatGPT may ask you to confirm before a tool that changes something. That is ChatGPT’s own check, separate from AgentedSEO’s approval queue.
06Your first safe task
On a plan with write actions
Use AgentedSEO. Start with get-capabilities. Find one published post with no meta description, write one, do a dry run first and show me the before and after, then submit it with a note. Change nothing else.
- The agent calls
set-meta. Meta titles and descriptions ask first by default, so the answer isproposed. The live page has not changed. - Open AgentedSEO › Dashboard › Approvals. Check Before and After, the checks it passed and the agent’s note. Click Approve.
- Open AgentedSEO › Dashboard › Change log, open the change’s Details and click Undo. The Before value is back, and the undo is logged.
The live page has not changed.
Undo restores the Before value, and the undo is logged.
On a read-only plan
Use AgentedSEO. List the open SEO issues on this site, grouped by severity, and tell me which three to fix first and why. Don’t change anything.
Then open AgentedSEO › Agents › Activity: every request ChatGPT made is there, reads included.
07What ChatGPT can and can’t change
- New drafts
- Edits to drafts
- Meta, schema, redirects, sitemaps, keywords, alt text
- Edits to published content, publishing
- Bulk changes over 20 pages
- robots.txt edits
- Noindex on a page with traffic
- Deleting redirects or schema
- Trashing or unpublishing
- Permanent deletes
- Header and footer code
- Users, plugins, themes, settings outside AgentedSEO
Change the per-area defaults in AgentedSEO › Agents › Approval rules. Approving and rejecting are not tools: only a person can do them, in WordPress. Full table: what your agent can and can’t change.
08Troubleshooting
| Symptom | Fix |
|---|---|
| ChatGPT can’t find the sign-in | A security plugin, the host or a cache blocks /.well-known/. Subdirectory installs need the host to forward the root paths. |
| “This connection request is not valid” | The client or its return address is unknown. Start again from ChatGPT. |
| “Only an administrator can connect an agent to AgentedSEO.” | Sign in to WordPress as an administrator, then retry. |
| ChatGPT can read but every change fails | Your plan is read-only for custom MCP servers. See which plans can do what. |
| ChatGPT asks you to sign in again | Refresh tokens last 30 days. Approve again on your site. |
| Calls fail after an AgentedSEO update | Workspaces keep a frozen snapshot of tools. An admin refreshes the tool list in workspace app settings. |
09Questions about ChatGPT and WordPress
For your own WordPress site, you add the site as a custom MCP server. With AgentedSEO, that server is part of the plugin, so there is nothing else to install on WordPress.
Yes, for SEO and content: 72 abilities from meta and schema to redirects, sitemaps and drafts. ChatGPT sees the tools its agent user may call.
No. It signs in with OAuth and gets a token for its own SEO Agent user.
Only through approval by default. Publishing asks first unless you switch that area to Automatic, and new posts are always drafts.
The OpenAPI 3.1 description of every route is at /wp-json/agentedseo/v1/openapi.json.
Click Revoke in AgentedSEO › Agents › Connections. The user and its sign-in are deleted; its change log stays.