Overview
If you've already connected a site through AI Management and your AI assistant still reports that it can't see the site, or shows sites you don't recognize, the client is almost always signed in to a different WPVibe account than the one holding your sites.
This is a different problem from a site losing its connection after a restore or migration, which AI Management's Repair connection button fixes on its own. This article covers the client-side case: the site is connected correctly, but the AI client you're talking to is bound to the wrong WPVibe account. If you haven't connected a site yet, start with Understanding AI Management first.
In this article, you will find how account binding works, why a mismatch happens silently, and step-by-step instructions for checking and rebinding your AI client to the correct WPVibe account.
The three accounts involved
Account | What identifies it | Where it lives |
Levamo account | Your Levamo login email | my.levamo.com |
WPVibe account | An email address, no password | mcp.wpvibe.ai |
AI client account | Your Claude, ChatGPT, or Cursor login | The AI provider |
Your Levamo sites are attached to your WPVibe account. Your AI client talks to WPVibe on behalf of one WPVibe account at a time. If the AI client is signed in to a different WPVibe account than the one holding your sites, it will report that nothing is connected, even though everything looks fine on the Levamo side.
A fourth piece, your Platform API key, controls the connection between Levamo and WPVibe itself and is covered in Understanding AI Management. It doesn't affect which WPVibe account your AI client is signed in to, so it isn't part of the mismatch problem this article solves.
Your WPVibe account is your Levamo email
As covered in Understanding AI Management, your WPVibe account is created automatically using your Levamo primary email, with no password required.
What's specific to AI clients is that this binding is per person. On a team, each member who connects a site does so with their own WordPress admin, their own Platform API key, and their own WPVibe account, tied to their own Levamo email. A teammate's Claude connection does not see your sites, and yours does not see theirs.
Tip:
To see exactly which email your WPVibe account uses, check the primary email under your Levamo account settings. That is the address to use whenever WPVibe asks you to sign in.
How an AI client connects to WPVibe
Connecting an AI client happens once, during the sign-in step covered in Understanding AI Management's connection flow. You add the WPVibe server URL to the client, type an email address, and enter the 6-digit code WPVibe sends to it. That email is the binding moment: it decides which WPVibe account the client is attached to, and the client keeps that authorization until you explicitly remove it.
Where each client stores the binding
AI client | Where the sign-in is stored | Scope |
Claude.ai / Claude Desktop | In your Claude account, under Customize → Connectors | Shared between claude.ai and the desktop app for the same Claude login |
Claude Code | In your local Claude Code configuration | Per machine and user profile |
ChatGPT | In your ChatGPT account, under the WPVibe app | Per ChatGPT login. The app attaches per chat, but the account link persists |
Cursor, Windsurf, Gemini CLI, and other local clients | In the client's local MCP configuration, often an | Per machine |
The practical consequence: a Claude account that signed in to WPVibe last month with [email protected] is still bound to [email protected] today, in every chat, on both web and desktop. It has no way of knowing your Levamo sites live under [email protected].
Important:
Do not work around a mismatch by adding a second WPVibe connector to the same AI client. Keep exactly one WPVibe connector per client. Duplicate connectors cause the client to reuse stale tokens and tool lists, and one connector already manages every site in the account.
Why a mismatch breaks things
Levamo primary email | Email used at WPVibe sign-in | Result |
Sites appear, everything works | ||
Assistant reports no connected sites, site operations fail | ||
A teammate's email | Assistant sees the teammate's sites, not yours |
The mismatch is silent. The Levamo dashboard shows the site as connected, the AI client shows WPVibe as connected, and the assistant simply cannot find the site. Nothing in either interface tells you the two sides are pointing at different WPVibe accounts.
Common ways this happens:
You tried WPVibe on your own before Levamo's AI Management existed and signed in with a personal email
You share a Claude or ChatGPT login with someone else who connected WPVibe first
Your Levamo account uses a different email than the one you normally reach for on sign-in screens
How to fix a WPVibe connection mismatch
Check which email your AI client is bound to
Step 1: Note your Levamo primary email
Check the primary email listed under your Levamo account settings. This is the email your WPVibe account should be using.
Step 2: Ask your AI client to list connected sites
In your AI client, start a new chat and ask it to use WPVibe to list your connected sites.
Step 3: Compare the results
If your Levamo site appears, the binding is correct and you can stop here. If the list is empty or shows sites you don't recognize, the client is signed in to a different WPVibe account. Continue with the rebinding steps below for your client.
Rebind Claude.ai and Claude Desktop
Step 1: Open Connectors
In Claude, open Customize → Connectors.
Step 2: Remove the WPVibe connector
On the WPVibe row, choose Disconnect, or remove the connector entirely.
Step 3: Add WPVibe back
Select Add → Add custom connector. Name it WPVibe, set the server URL to https://mcp.wpvibe.ai/mcp, and leave the OAuth client fields empty.
Step 4: Sign in with the correct email
Click Connect, enter your Levamo primary email, and enter the 6-digit code.
Note:
Claude Desktop shares connectors with your Claude account, so doing this once on claude.ai fixes the desktop app as well. Restart the desktop app if it does not pick up the change.
Rebind Claude Code
Step 1: Remove and re-add the WPVibe server
claude mcp remove wpvibe claude mcp add --transport http wpvibe https://mcp.wpvibe.ai/mcp
Step 2: Authenticate
Type /mcp in Claude Code, select wpvibe, choose Authenticate, and sign in with your Levamo primary email.
Rebind ChatGPT
Step 1: Open Apps & Connectors
Open ChatGPT settings → Apps & Connectors, or go to the WPVibe app page.
Step 2: Disconnect WPVibe
Disconnect or remove the WPVibe app.
Step 3: Reconnect with the correct email
Add WPVibe again from the app directory, click Connect, and sign in with your Levamo primary email.
Note:
Remember to attach WPVibe to each new chat with the + button.
Rebind Cursor and other local clients
Step 1: Remove the WPVibe server
Remove the WPVibe server from the client's MCP settings.
Step 2: Clear cached sign-in
If the client uses mcp-remote, delete the .mcp-auth folder in your home directory to clear the cached sign-in.
Step 3: Reconnect with the correct email
Add the server again with https://mcp.wpvibe.ai/mcp and complete the sign-in with your Levamo primary email.
If the sign-in page does not ask for an email
Occasionally a client reconnects without showing the email screen, or the WPVibe page opens already signed in as the old address. This happens when the client still holds a cached token, or your browser still has an active WPVibe session from an earlier sign-in.
Use a private browser window for the sign-in step, so no existing WPVibe session is reused. You can also visit
https://mcp.wpvibe.ai/accountand sign out there first.Use WPVibe's backup endpoint. Add the connector with
https://mcp2.wpvibe.ai/mcpinstead of the primary URL. It is the same service, but most AI clients treat it as a new connector and run a fresh sign-in. Remove the oldmcp.wpvibe.aiconnector first so you don't end up with two.
FAQ
Which email is my WPVibe account?
Always the primary email on your Levamo account.
Can I choose a different WPVibe email from the AI Management tab?
No. The WPVibe account is created automatically using your Levamo primary email.
Does the binding follow my AI account across devices?
For Claude.ai and Claude Desktop, yes. For Claude Code, Cursor, and other local clients, the binding is per machine.
Do teammates share my WPVibe connection?
No. Each team member connects with their own Levamo email and gets their own WPVibe account.
How many WPVibe connectors should one AI client have?
Exactly one.
Conclusion
A WPVibe connection mismatch is silent but easy to fix once you know what to look for: check whether your AI client is signed in with your Levamo primary email, and rebind it if not. If your assistant still can't see your site after rebinding, contact our support team, available 24/7, with your Levamo primary email, the site URL, the AI client you're using, and what the assistant returns when asked to list connected sites.