GeneratePress AI

Connect this AI client to my WordPress site using GeneratePress AI.

MCP server URL:
https://example.com/wp-json/generatepress-ai/mcp

OAuth authorization-server metadata URL:
https://example.com/wp-json/generatepress-ai/oauth/metadata/authorization-server

Use this client’s native remote HTTP MCP support with OAuth sign-in. If these URLs use https:// and the client supports an explicit authorization-server metadata URL, configure that URL directly; otherwise use standard discovery. If they use http://, this is a local development site: don’t set the metadata URL, and keep the http:// addresses as they are.

If this site runs on my computer, for example at a .local or localhost address, only a session running on this computer can reach it. If you are running in the cloud or on another machine, tell me to start a local session instead.

If you can make HTTP requests, first send one to the MCP server URL. A 401 response with a JSON body means the site is reachable. If you get an HTML page, a security challenge or a firewall block page instead, stop: tell me my site’s firewall is blocking the connection, and point me to https://learn.generatepress.com/ai#firewall.

Complete every setup step you can perform yourself. If you can start browser sign-in, do it; I will approve access on a WordPress page.

When you reach a step only I can do, such as signing in from your app’s settings, reloading your tools, or starting a new chat, stop there. Check this app’s current steps with your own tools, the installed client’s help, or its official documentation, then tell me in short numbered steps exactly what to do. If I need to continue in a new chat, give me one sentence to paste there that includes this site’s MCP server URL and asks you to verify the connection through that server with a read-only GeneratePress AI tool call. Do not report success yet.

Once the connection is available to you, verify it with a read-only GeneratePress AI tool call. Only report success once that works. If setup fails, investigate supported configuration fixes before asking me to troubleshoot.

Or follow the steps for your app:

• Claude Code (recommended)
• Codex and the ChatGPT desktop app (recommended)
• Claude app and claude.ai
• ChatGPT on the web
• Grok
• Cursor
• VS Code
• Another app

Claude Code

Works in the terminal and in the Code tab of the Claude app. For a site on your computer, start a local session.

The easiest way is the setup prompt above: paste it into a Claude Code chat and follow the steps it gives you.

Or ask Claude to run this command, with your own server URL and name:

claude mcp add-json --scope user generatepress-ai-example-com '{"type":"http","url":"https://example.com/wp-json/generatepress-ai/mcp","oauth":{"authServerMetadataUrl":"https://example.com/wp-json/generatepress-ai/oauth/metadata/authorization-server"}}'

Then:

1. Type /mcp, select the server, and choose Authenticate.
2. Approve access on the page that opens on your site.
3. If the tools don’t appear, start a new chat, or quit and reopen the app and return to your chat. Then check the connection.

On a local site served over plain http://, use this command instead. It leaves out the sign-in address, which Claude Code accepts only over HTTPS:

claude mcp add --transport http --scope user generatepress-ai-example-local http://example.local/wp-json/generatepress-ai/mcp

Ask Claude to run these commands for you: their quoting works in bash and zsh, but not in Windows PowerShell. To sign in from a terminal instead of /mcp, run:

claude mcp login generatepress-ai-example-com

Claude Code’s MCP documentation

Codex and the ChatGPT desktop app

The ChatGPT desktop app, the Codex CLI and the Codex IDE extension share one set of MCP settings, so adding the server once covers all three.

The easiest way is the setup prompt above, pasted into a Codex chat.

Or add the server in the app, without a terminal:

1. Open the app’s settings, go to MCP servers, and add a server.
2. Enter a name, such as generatepress-ai-example-com, choose Streamable HTTP, and paste your server URL.
3. Save, then restart when the app asks.
4. Choose Authenticate, then approve access on your site.

Or from a terminal:

codex mcp add generatepress-ai-example-com --url https://example.com/wp-json/generatepress-ai/mcp
codex mcp login generatepress-ai-example-com

Codex finds your site’s sign-in on its own. If your host blocks that, see The app can’t find how to sign in.

OpenAI’s MCP instructions

Claude app and claude.ai

This adds GeneratePress AI as a custom connector on your Claude account. It then works in Claude on the web, desktop and mobile, in Cowork, and in Claude Code when you’re signed in with the same account.

1. Open Claude’s Add custom connector dialog. Sign in to Claude if it asks.
2. Paste your server URL, then choose Add.
3. Choose Connect, then approve access on your site.

• Claude connects from Anthropic’s servers, so your site must be reachable from the internet. A site on your computer needs Claude Code instead.
• If a firewall protects your site, Claude’s requests come from Anthropic’s address range, 160.79.104.0/21. See A firewall blocks the connection.
• The Free plan allows one custom connector. On Team and Enterprise plans, an Owner adds the connector for the organization first.

Claude’s custom connector instructions

{
  "mcpServers": {
    "generatepress-ai-example-com": {
      "url": "https://example.com/wp-json/generatepress-ai/mcp"
    }
  }
}

{
  "servers": {
    "generatepress-ai-example-com": {
      "type": "http",
      "url": "https://example.com/wp-json/generatepress-ai/mcp"
    }
  }
}

Another app

Any app that supports remote MCP servers with OAuth sign-in can connect. Enter the values from Settings → GeneratePress AI → Other AI apps:

Server URL, your site’s MCP server:

https://example.com/wp-json/generatepress-ai/mcp

Transport: Streamable HTTP. If the app asks for a server type, choose HTTP or Streamable HTTP.

Sign-in: OAuth. The app opens your site so you can approve access.

Authorization server metadata URL, only if the app asks for it:

https://example.com/wp-json/generatepress-ai/oauth/metadata/authorization-server

Name, anything you like, but different for each site. For example:

generatepress-ai-example-com

If the app asks for a Client ID or OAuth credentials, open Client ID and OAuth details on the same screen and choose Generate connection details. Copy the Client ID, authorization endpoint, token endpoint and mcp scope. Leave the client secret empty, and choose none (PKCE only) for token authentication. If the app gives you its own OAuth callback URL, choose Use a different client and paste that exact URL.

Check the connection

After you approve access, ask your AI:

Check your connection to my WordPress site.

It should answer by calling a read-only GeneratePress AI tool.

Try these first

Inspect this site’s GeneratePress AI capabilities, then propose one improvement to the homepage and stage it as a draft or preview for my approval. Do not publish anything.

Build a landing page for our spring sale as a draft, using my Global Styles.

Find a pricing table pattern and add it to a new draft page.

Shorten the hero text on the About page, and show me the change before you save it.

What has GeneratePress AI changed on this site today?

How changes work

• New pages, posts, forms, overlays, headers, footers and templates arrive as drafts. Review them and publish them in WordPress.
• Changes to existing content, Global Styles, Design Tokens and site settings are staged first. Your AI shows you what will change, and content changes include a private preview link you can open in WordPress.
• Nothing is saved until you approve in your AI app. A staged change expires after two hours, and it’s refused if the page changed in the meantime.
• Every tool checks your WordPress permissions, so the AI can only do what your account can do.

A firewall blocks the connection

Your app reports an error such as 403 or “blocked”, or a page titled “Just a moment…” or “Sorry, you have been blocked”, often with a Ray ID. The request never reached WordPress, so GeneratePress AI can’t see it or fix it. It can also happen partway through a build, because some firewall rules inspect request content, and page designs contain HTML.

Allow requests to addresses that start with /wp-json/generatepress-ai/. Everything your AI app requests lives there. The approval page opens in your own browser, so it isn’t affected.

On Cloudflare:

Add a custom rule under Security rules with this expression. Choose the Skip action, and skip the managed rules, Super Bot Fight Mode and rate limiting.

starts_with(http.request.uri.path, "/wp-json/generatepress-ai/")

Bot Fight Mode, on the Free plan, can’t be skipped by a rule. If it’s on, turning it off for the site is the only fix.

If you only connect from the Claude app or claude.ai, you can allow Anthropic’s address range instead of the path:

160.79.104.0/21

For other firewalls and security plugins, allow the same path.

If your host runs the firewall, send them this:

Please let my AI app reach my WordPress site’s GeneratePress AI addresses. They are every address on my site that starts with one of these:

/wp-json/generatepress-ai/
/.well-known/oauth-protected-resource
/.well-known/oauth-authorization-server
/.well-known/openid-configuration

Please make sure requests to them aren’t cached, redirected or shown a bot challenge, and that the Authorization request header reaches PHP.

To check: a request to https://example.com/wp-json/generatepress-ai/mcp without signing in should get HTTP 401 with a JSON body. An HTML page, a redirect, a 403 or a challenge means something is still in the way.

These rules let requests to those addresses skip the firewall’s checks. Anything that reads or changes your site still needs an approved connection.

Don’t:

• Skip the firewall for a header or user agent. Anyone can send those.
• Make WordPress REST routes public or turn off your security plugin.
• Ask your AI to rewrite or encode content to get past the firewall.

RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]