Skip to main content
Start free →

Product

Features How it works The Agent Safety & security About

Resources

Cookbook Blog Docs Support Alternatives
Pricing Sign in
Docs Troubleshooting

Troubleshoot MCP Auth, oAuth, Connection, and Tool Errors

Fix common WPVibe MCP connector problems, including authorization failures, session terminated errors, missing tools, stale tool lists, and connectors that only show the code tool.

When to use this guide

Use this guide when WPVibe sign-in works, but your AI client still cannot use WPVibe correctly. These symptoms usually mean the client has stale connector state, an expired token, or an outdated tool list.

Common errors this fixes

  • Authorization with the MCP server failed
  • Session terminated
  • MCP error 32600
  • invalid_token, invalid access token, or invalid refresh token appears in connector or support logs.
  • The connector says it is connected, but tools do not load.
  • The tool list is missing WordPress tools like list_sites, site_info, rest_api, or connect_site.
  • The connector only shows a single code tool.
  • Your AI client says the connector is not connected immediately after successful WPVibe sign-in.

Start with a clean reconnect

Important: Do not create a separate WPVibe MCP connector for each WordPress site. One WPVibe MCP connector can manage multiple connected WordPress sites. After WPVibe is connected, use the connect_site and list_sites tools to add or switch between sites.

If you have created multiple WPVibe connectors or apps in ChatGPT, Claude, or another AI client, remove all duplicate WPVibe entries first. Duplicate connectors can cause the client to reuse stale OAuth tokens, stale tool lists, or the wrong MCP server URL.

  1. Remove every duplicate WPVibe connector or app from your AI client.
  2. Start a fresh conversation or reload the client.
  3. Add WPVibe once with the primary MCP server URL:
https://mcp.wpvibe.ai/mcp

After signing in, ask your AI to list your WPVibe sites. A good test prompt is:

Use WPVibe to list my connected sites.

Refresh the tool list

Some AI clients cache the MCP tool list separately from the sign-in session. If sign-in succeeds but tools are missing, refresh the connector tools if your client provides that option. If there is no refresh button, remove and re-add the connector, then start a new chat.

If only the code tool appears

If the connector only shows code, the client may still be using an older cached tool manifest. Refresh tools, reload the client, and start a new conversation. If the issue continues, remove and re-add the connector.

Use the backup endpoint if the original connector stays stuck

If the primary URL still appears stuck after a clean reconnect, add WPVibe as a new connector using the backup endpoint:

https://mcp2.wpvibe.ai/mcp

This points to the same WPVibe service, but many AI clients treat it as a fresh connector identity. It can help when the client has cached old authorization or tool state for the primary URL.

What to send support

If the connector still fails, email [email protected] with:

  • Your WPVibe account email.
  • The WordPress site URL.
  • The AI client you are using, such as Claude, ChatGPT, Cursor, or Claude Desktop.
  • The MCP URL you added.
  • The exact error message and any reference code shown by the client.
  • The approximate time of the failed attempt, including your time zone.