Connect Claude and ChatGPT

Connect Claude or ChatGPT to your WordPress site through the Aimogen Pro connector, so they can write, edit and manage your site with the tools you allow.

Claude and ChatGPT can work directly on your WordPress site: draft and publish posts, organise the media library, answer comments or manage a WooCommerce store. They use the tools your site's MCP server offers, only the ones you switch on, and only after an administrator approves the connection on the site itself.

Advanced Tools › AI MCP Integration › Create Your MCP Server

Two ways to connect#

Both reach the same tools with the same limits. The Aimogen Pro connector is the one listed in Claude's connector directory, and the simplest for anyone who should not handle URLs or tokens. Your site's own URL keeps a third party out of the path and works with any client. The connector URL for your site is shown, with a Copy button, in the Connect Claude or ChatGPT box on the MCP screen.

Requirements#

• Aimogen Pro and the MCP Server extension (aiomatic-extension-mcp-server), both up to date. See Official extensions.
• A public HTTPS site. Claude and ChatGPT connect from their own servers, so a site on a local machine or behind HTTP authentication cannot be connected. The Aimogen Pro connector also needs the standard HTTPS port, 443.
• A WordPress administrator account. Only administrators can approve a connection.
• A Claude or ChatGPT account that can add connectors. In ChatGPT that means developer mode, which is available on paid plans. On business and enterprise plans an administrator may have to allow custom connectors first.

Set up your site#

On your WordPress site, open Advanced Tools › AI MCP Integration › Create Your MCP Server.

1. Tick Enable MCP server.
2. Set Transport to Both - legacy SSE and Streamable HTTP (recommended) or Streamable HTTP only. Claude and ChatGPT speak Streamable HTTP; a site set to Legacy SSE only cannot be connected.
3. Tick Sign-in (OAuth). Without it the Aimogen Pro connector cannot sign in, and clients have to be given the Bearer Token instead.

4. Choose an Access Level. It limits every connected app, whichever way it connected:

   Access Level	A connected app can
   Administrator - every tool	Use every tool in the packs you enable, including deleting content and managing users, options, plugins, themes and orders
   Read & write	Read and create or change content. No deletions, users, options, plugins, themes or orders
   Read only	Read, and change nothing

   Tools outside the chosen level are hidden from the app and refused if it calls them anyway.

5. Under Enabled Tool Packs, switch on what the apps may use. See What Claude and ChatGPT can do.
6. Save the settings.
7. Under Connection Self-Test, click Run Self-Test. It calls your site the way Claude and ChatGPT do, and reports a firewall, CDN rule or security plugin getting in the way. Fix every failure before you connect anything.

Connect Claude#

Connectors you add on claude.ai are also available in Claude Desktop and the Claude mobile apps.

1. In Claude, open Customize › Connectors (https://claude.ai/customize/connectors).
2. If Aimogen Pro appears when you browse or search the connector directory, select it and click Connect. Otherwise click Add custom connector, enter a name such as Aimogen Pro and the URL https://coderevolution.ro/wp-json/aimogen-relay/v1/mcp, and on the next step keep the detected options: Sign in now, Use Claude's published identity, no request headers, Streamable HTTP.
3. Claude opens the Aimogen Pro sign-in page. Enter your WordPress site address, for example https://example.com, and click Continue.
4. Your site's approval screen opens. Sign in as an administrator if asked, check that it names Aimogen Relay for Claude and ChatGPT (coderevolution.ro), and click Approve.
5. You are sent back to Claude and the connector shows as connected. In a chat, switch it on from the tools menu if it is not on already.

To connect without the relay, use your site's own URL in step 2. Step 3 is then skipped, and your site's approval screen names Claude.

Connect ChatGPT#

If Aimogen Pro is not listed in ChatGPT's app directory, add it as a connector in developer mode. The exact labels change between ChatGPT versions.

1. In ChatGPT, open Settings › Connectors › Advanced and turn on Developer mode.
2. Back in Connectors, click Create.
3. Enter a name such as Aimogen Pro, the URL https://coderevolution.ro/wp-json/aimogen-relay/v1/mcp (or your site's own URL), and choose OAuth as the authentication. Leave any client ID and secret fields empty: ChatGPT identifies itself.
4. Accept the custom-connector notice and click Create. ChatGPT opens the sign-in: enter your site address, then approve on your site, as for Claude.
5. In a new chat, pick the connector from the tools menu.

Claude Code and other clients#

For Cursor, scripts and other developer tools, connect to your site's own URL. The MCP screen has ready-made setup for each; see MCP integration.

Claude Code can use either URL. With the Aimogen Pro connector:

claude mcp add --transport http aimogen-pro https://coderevolution.ro/wp-json/aimogen-relay/v1/mcp

Then run /mcp inside Claude Code and select the server to sign in. The sign-in opens in your browser.

What you approve#

A connection through the Aimogen Pro connector shows two screens. Read both.

1. The Aimogen Pro sign-in page, on coderevolution.ro, names the app that asked (Claude or ChatGPT) and asks for your site address.
2. Your site's approval screen names the relay and the address it returns to. It warns that the app will be able to use every MCP tool you have switched on, which can include reading, creating, changing and deleting content. Approve only if you started the connection yourself.

The connection acts as the administrator who approved it. Posts it creates are authored by that account, the activity log records that account, and if the account stops being an administrator, the connection stops working at its next request.

What Claude and ChatGPT can do#

The tools come from the packs you enable under Enabled Tool Packs, narrowed by the Access Level.

Every tool tells the app whether it only reads or also changes your site, and whether a change is destructive. Claude and ChatGPT use this to decide what to show you and when to ask before acting.

With Activity Log on, every call is listed under Recent AI Activity on the MCP screen: when, which tool, the result, how long it took, how the app signed in, and as which user.

How the Aimogen Pro connector works#

A listing in Claude's or ChatGPT's directory has one fixed address, but every Aimogen Pro site has its own. The connector address belongs to a relay that CodeRevolution runs on coderevolution.ro.

1. Claude or ChatGPT connects to the relay and is asked to sign in.
2. You enter your site address. The relay finds your MCP server and checks that sign-in is on.
3. The relay signs in to your site as an ordinary OAuth client, and your site asks you to approve it.
4. Your site gives the relay its own tokens. The relay gives Claude or ChatGPT separate tokens of its own.
5. From then on, each request from Claude or ChatGPT is forwarded unchanged to your site, and your site's answer is passed back.

Your site needs nothing extra for this: the relay is one more client of the sign-in your MCP server already has.

What the relay stores#

• Stored: your site address, the app's name, when the connection was made and last used, and your site's tokens, encrypted. The tokens it gives Claude and ChatGPT are kept only as hashes.
• Not stored: the requests and the answers. What Claude or ChatGPT reads from or writes to your site passes through without being stored or logged.
• Retention: a connection that goes unused for 30 days ends, and its tokens are deleted.

Security#

• Every sign-in is tied to the browser that started it, so a link to someone else's sign-in cannot be finished anywhere else.
• The relay only sends sign-in codes back to Claude's and ChatGPT's own addresses, or to an app on your own computer. A sign-in link sent to you by someone else cannot give them access to your site.
• The relay only contacts the address you entered, over HTTPS, and never private network addresses.
• The tokens it holds only work against your site's MCP endpoint, within the Access Level and tool packs you set.

If nothing should pass through a third party, connect with your site's own URL instead. See also Data, GDPR and retention.

Disconnect#

• In Claude: Customize › Connectors, open Aimogen Pro, and disconnect or remove it.
• In ChatGPT: remove the connector under Settings › Connectors.
• On your site: untick Sign-in (OAuth) and save. Every app connected by sign-in, including through the Aimogen Pro connector, stops working at once. Apps using the Bearer Token are not affected; change the token to cut those off too.
• Per account: removing the administrator role from the account that approved a connection stops that connection.

Removing the connector in an app stops that app from using your site. If the app does not tell the relay, the relay ends the unused connection after 30 days. To have a relay connection deleted immediately, open a support ticket.

Troubleshooting#

Messages on the Aimogen Pro sign-in page#

"No Aimogen MCP server answered at …" The extension is not active, Enable MCP server is off, or Transport is set to Legacy SSE only.

"… has the MCP server on, but OAuth sign-in is off." Tick Sign-in (OAuth) and save. If the option is missing, update the MCP Server extension.

"… refused the connection (HTTP 403)." A firewall, CDN rule or security plugin is blocking /wp-json/aiomatic-mcp/. Allowlist /wp-json/aiomatic-mcp/v1/*; see Plugin and server conflicts.

"Could not reach …" The address is wrong, the site is down, or it is not reachable from the internet over HTTPS on port 443.

"Use your site's https:// address." Connections are made over HTTPS only.

"… answered, but its OAuth details are missing or invalid." Update Aimogen Pro and the MCP Server extension, and make sure no security rule or redirect touches /wp-json/aiomatic-mcp/ or /.well-known/.

"… cannot register the relay" or "… did not let the relay register." Update the MCP Server extension.

"This sign-in was started in a different browser…" Finish the sign-in in the browser it opened in, and allow cookies for coderevolution.ro.

"This sign-in expired…" A sign-in has to be finished within 15 minutes. Start again from Claude or ChatGPT.

"This relay only connects Claude, ChatGPT and apps on your own computer." The app is something else. Connect it to your site's own URL instead.

Messages on your site's approval screen#

"Unknown application. Please reconnect from your AI client so it can register again." Your site could not read the relay's identity from coderevolution.ro. Your host or a firewall may be blocking outgoing HTTPS requests from the site; allow requests to coderevolution.ro.

"Your account is not allowed to connect an AI client to this site." Sign in with an administrator account.

"This approval form expired." Start again from Claude or ChatGPT.

ModSecurity blocks the approval screen#

Symptom. Instead of the approval screen, your site shows "Not Acceptable! An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security." or a plain 403 page.

Cause. A sign-in request carries web addresses as parameters (client_id, redirect_uri), and ModSecurity's remote-file-inclusion rules, such as OWASP CRS rule 931130, treat any parameter holding another site's address as an attack. The token request carries one in its body too.

Fix. Do not switch ModSecurity off for the whole site. Exempt only the rule that fires, and only for /wp-json/aiomatic-mcp/. With root or WHM access, find the rule ID in the ModSecurity log, then add:

SecRule REQUEST_URI "@beginsWith /wp-json/aiomatic-mcp/" "id:1000931,phase:1,pass,nolog,ctl:ruleRemoveById=RULE_ID"

Replace RULE_ID with the ID from the log, add one ctl:ruleRemoveById= per extra rule, and restart Apache. On shared hosting, send your host the blocked URL from the address bar and ask them to exempt the triggered rule IDs for that path only.

Messages from Claude or ChatGPT#

"The relay could not reach … The site may be down or too slow to answer." The site did not answer in time. Tools that write long content can take minutes; if this happens on every long task, check your site's PHP time limit and any proxy timeouts.

"… refused the relay even after renewing its sign-in (HTTP 401)." Update the MCP Server extension. Older versions only accept sign-in when a Bearer Token is also set.

"The MCP server on … is gone (HTTP 404)." The extension was deactivated, the MCP server was switched off, or Transport was changed to Legacy SSE only.

"… ended this connection. Connect again." The site stopped accepting the connection, for example because the approving account lost its administrator role. Connect again.

"The relay is busy with other requests." Try again in a moment.

"Access denied: tool '…' requires '…' access." The Access Level does not allow that tool.

A tool is missing. Its pack is off, or the Access Level hides it. After changing packs, start a new chat; if the old tool list remains, disconnect and connect again.

Related#

• MCP integration
• Official extensions
• Plugin and server conflicts
• Data, GDPR and retention
• Security hardening