Skip to content

Troubleshooting

The AI Actions screen isn't showing my key/URL correctly, or shows a warning

Check for a notice on your Plugins screen or the AI Actions screen naming what's missing. The WordPress MCP Adapter is a plugin, not installed automatically - install it from GitHub, then refresh. The WordPress Abilities API is built into WordPress core; if it's named as missing, update WordPress rather than installing a plugin for it.

My AI client can't see any tools/actions

  • Confirm both required plugins (see above) are installed and activated.
  • Confirm you used the exact MCP Server URL and API key shown on the AI Actions screen - a typo in either will fail silently in some clients rather than showing a clear error.
  • Most AI clients only fetch the list of available actions once, when the connection is first made. If you connected before this extension (or DMS itself) was updated with new actions, disconnect and reconnect the server in your AI client to pick up the current list.

The AI says a request isn't allowed / permission denied

The AI can only do what your WordPress user account can do. If you can't perform an action from the DMS admin yourself, the AI can't either. Check your account type's permissions under Dealer.ms → Settings → Account Types, or use a key created from an account with the access you need.

The AI made a change I didn't expect

Check Dealer.ms → AI Actions for a full record of what ran, when, and with what input. Most actions are reversible from the normal DMS admin (a price or status change can be changed back; a deleted listing goes to the WordPress trash first, not straight to permanent deletion). A few actions are marked permanent in What the AI Can Do - undoing those means recreating the data by hand.

Photo optimization, conversion, or background removal seems stuck

These photo actions are processed in the background by Dealer.Pics, not instantly - the AI queues the job and has to check back. Give it a little time and ask again ("did that background removal finish?"). If it's been more than a few minutes, check your Dealer.Pics credit balance - a job can't complete without enough credits available.

I don't have a DMS API key to use

Create one from your WordPress user profile page. You can create as many as you like, one per person or per AI client, and delete any of them at any time.

One-click Connect (OAuth) doesn't start, or the app says it can't find an authorization server

  • Make sure One-click Connect is turned on under Dealer.ms > AI Actions.
  • Permalinks must not be set to "Plain" (Settings > Permalinks).
  • Paste the MCP Server URL exactly as shown, including https://.
  • Security or firewall plugins, and some hosts, block addresses starting with /.well-known/ or /dms-oauth/. Open yoursite.com/.well-known/oauth-protected-resource in a browser. You should see a short block of text starting with {"resource". If you get a block page or an error instead, allow those two paths in your security plugin or ask your host.
  • If your site uses a full-page cache or CDN, exclude /.well-known/* and /dms-oauth/* from caching.

"This app is not registered with this site"

The app's registration was cleared, usually because it registered but never finished connecting. Remove the connector from your AI app and add it again.

An app I connected stopped working

It was disconnected. That happens when someone clicks Disconnect on the AI Actions screen, when the approving user's password is changed or reset, or after 90 days without use. Reconnect it from the AI app.

Gemini Enterprise

"Failed to reload custom actions" with a schema validation error. One of the tools published a schema Gemini can't read. Update the AI Actions extension to the latest version and click Reload custom actions again. If it still fails, send the full error to support, since Gemini only reports the first bad tool it finds.

A GET ... HTTP 405 line in the error details. Ignore it. Gemini tries to open an optional streaming connection that the server doesn't offer, and carries on without it. It isn't the cause of a failure.

Verify Auth fails or says the redirect doesn't match. The redirect URI you entered when creating credentials must match what Gemini sends, character for character. The usual value is https://vertexaisearch.cloud.google.com/oauth-redirect. If Gemini shows a different callback URL, create new credentials with that one.

"This app is not registered with this site" after clicking Verify Auth. The Client ID is wrong. Check that Client ID holds the dms_... value from the AI Actions screen and not the MCP Server URL Gemini may have pre-filled.

Token step fails with an invalid client error. The secret is wrong or was never copied. Create a new set of credentials and paste the new secret. Leave Use HTTP Basic Authentication ticked.

Verify Auth does nothing, or fails right after Allow. Allow pop-ups for the Google Cloud console. If that isn't it, a firewall (Cloudflare, your host, a security plugin) may be blocking Google from reaching /dms-oauth/token or the MCP Server URL. Allow both and try again.

The Custom MCP server option is missing or errors in Google Cloud. The organization policy constraints/discoveryengine.managed.disableCustomMcpServerConnector is still enforced. See Part 2 of Connecting Gemini Enterprise.

Still stuck?

Check Dealer.ms → AI Actions for the specific error recorded against the action that failed - the message there is usually the most direct answer.