Skip to main content
Start free →

Product

Features How it works The Agent Safety & security About

Resources

Cookbook Blog Docs Support Alternatives
Pricing Account
Docs Getting Started

AI Client Setup

Add WPVibe to Claude, ChatGPT, Cursor, Claude Code, or any MCP-compatible client.

Use the same server URL everywhere

https://mcp.wpvibe.ai/mcp

Different AI clients label MCP servers in different ways, but the URL stays the same.

Signing in

Every client uses the same sign-in. Your AI client opens a WPVibe page, you enter your email, and WPVibe emails you a 6-digit code. The code is right in the subject line. Type it on the WPVibe page you left open, and sign-in finishes in that same tab. There is no sign-in link to click, so it works the same whether you read the email on your phone or your computer.

A note on models

Any model that can use MCP can use WPVibe, and connecting your site works on all of them. Once your AI starts doing real work on the site, the model matters more. Building pages, auditing plugins, and multi-step recipes are agentic tasks: the AI has to plan steps, call tools, check results, and keep going. Fast default models are tuned for quick conversation, and on longer jobs they can lose the thread or invent a reason to stop.

If your client lets you pick a model, pick a reasoning model (often labeled “thinking”) for site work:

  • ChatGPT: choose a Thinking model from the model picker instead of Auto. On the free plan ChatGPT picks the model for you, which is fine for connecting and everyday edits.
  • Claude: the default models handle agentic work well. Turn on extended thinking for large builds.
  • Cursor, Windsurf, and other IDE clients: pick the strongest model your plan offers for site-wide operations.

If your AI stalls mid-task or talks itself out of continuing, retry in a fresh chat on a thinking model before assuming something is broken.

Claude.ai

Open Settings, go to Connectors, add a custom connector, and paste the WPVibe MCP server URL. When Claude prompts you to authorize, sign in with your WPVibe account.

Claude Desktop

Open Settings, go to MCP, add a remote server, and paste the WPVibe MCP server URL. Restart Claude Desktop if it does not immediately show the server.

Claude Code

claude mcp add --transport http wpvibe https://mcp.wpvibe.ai/mcp

ChatGPT

The easiest path is the official WPVibe app in the ChatGPT app directory: add WPVibe to ChatGPT, click Connect, and complete the sign-in step.

WPVibe app page in the ChatGPT app directory showing the Try in chat button and Connected status

One thing to know: in ChatGPT, apps attach per conversation. The link above opens a chat with WPVibe already attached. For any other chat, tap the + button in the message box and choose WPVibe before you start; if you skip that step, ChatGPT answers from web search instead of your site. This is what an attached chat looks like:

ChatGPT message box with the WPVibe app attached, shown as a WPVibe chip next to the plus button

You can also add WPVibe manually: use the connector or developer-mode MCP flow available in your ChatGPT workspace, paste the WPVibe MCP server URL, and complete the sign-in step.

Cursor

Open Cursor settings, find MCP servers, add a remote server, and paste the WPVibe MCP server URL.

Gemini CLI

gemini mcp add --transport http --scope user wpvibe https://mcp.wpvibe.ai/mcp

No token or client ID is needed. The first time Gemini uses a WPVibe tool, a browser window opens for the normal WPVibe sign-in.

One caveat: Google is moving individual (free and Google One) Gemini CLI accounts to Antigravity, and the CLI now refuses to sign in on those plans with a message about migrating. If you see it, follow the Google Antigravity steps below instead. Paid Code Assist and API-key setups keep working.

Google Antigravity

Antigravity reads MCP servers from ~/.gemini/config/mcp_config.json (you can also open this file from the MCP settings in the Antigravity editor). Add WPVibe as a remote server:

{
  "mcpServers": {
    "wpvibe": {
      "serverUrl": "https://mcp.wpvibe.ai/mcp"
    }
  }
}

No token, client ID, or secret is needed. WPVibe supports dynamic client registration, which Antigravity handles automatically: the first time the agent uses a WPVibe tool, a browser window opens for the normal WPVibe sign-in. If no sign-in window appears, update Antigravity to the latest version, reload your MCP servers, and try again.

Perplexity

Perplexity supports custom remote MCP connectors on Enterprise plans, with rollout to individual paid plans under way. If your plan has them: open Account settings, go to Connectors, click + Custom connector, and select Remote. Name it WPVibe, paste the WPVibe MCP server URL, choose Streamable HTTP as the transport, and set authentication to OAuth 2.0 with client ID and secret left empty. After adding it, click the connector card to run the WPVibe sign-in. The local connectors in the Perplexity Mac app are a separate feature and not the path for WPVibe.

Goose, Trae, Windsurf, and other MCP clients

Any client that supports remote MCP servers over HTTP works with WPVibe. Wherever the client asks for a server URL or endpoint, paste the WPVibe MCP server URL, leave token and client ID fields empty, and complete the WPVibe sign-in when the browser window opens. If your client only supports local command-based MCP servers, or a sign-in window never opens, check its documentation for “remote MCP” or “streamable HTTP” support.

After setup

Ask your AI: “Use WPVibe to list my connected sites. If no sites are connected, help me connect one.” That confirms the client can reach WPVibe before you start editing WordPress.