Documentation

Everything you need to connect your WordPress sites to AI.

On this page

Getting Started Tools Reference Connecting a WordPress Site Common Workflows WordPress Abilities API Safety & Security FAQ

Getting Started

WPVibe is a remote MCP server that lets AI assistants manage your WordPress sites. Add the server URL to your AI client, sign in with your email, and start managing WordPress through conversation.

Server URL

https://mcp.wpvibe.ai/mcp

Setup by Client

Claude.ai -- Settings → Connectors → Add → paste the server URL.

Claude Desktop -- Settings → MCP → Add remote server → paste the server URL.

ChatGPT -- Settings → Connectors → Developer Mode → Add → paste the server URL.

Cursor -- Settings → MCP → Add remote server → paste the server URL.

Claude Code --

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

After adding the server, you'll be prompted to sign in with your email via a magic link. No passwords needed.

Tools Reference

WPVibe provides 14 tools. All tools include MCP annotations (readOnlyHint / destructiveHint).

Plugin not required for basic use. The REST API and Abilities API tools work with any WordPress site out of the box -- no plugin needed. Install the Vibe AI plugin to unlock file management, media uploads, WP-CLI, live reload, and theme editing.

Site Management

ToolDescriptionType
connect_site Connect a WordPress site. Returns a one-click authorization link the user opens in wp-admin. Write
list_sites List all WordPress sites registered to your account. Read
remove_site Remove a WordPress site from your account. Soft delete -- can be restored within 30 days. Write
site_info Get metadata about a connected site: name, URL, WP version, active theme, installed plugins. Read

WordPress REST API

ToolDescriptionType
rest_api Call any WordPress REST API endpoint. Supports GET, POST, PUT, DELETE. Smart defaults: content excluded from list responses, DELETE goes to trash, new posts default to draft. Read/Write
upload_media Upload an image to the WordPress media library from a URL. Handles download, SSRF protection, and returns the attachment details. Write

Abilities API (WP 6.9+)

ToolDescriptionType
discover_abilities List all abilities registered by plugins on a connected site. Returns names, descriptions, schemas, and annotations. Read
get_ability_info Get full details for a single ability: input/output schemas, description, annotations, and metadata. Read
run_ability Execute a WordPress Abilities API ability by name. HTTP method determined automatically from ability metadata. Read/Write

Theme Files

ToolDescriptionType
list_files List theme files on a connected site. Returns file paths and sizes. Requires the Vibe AI plugin. Read
search_files Search theme file contents for a pattern. Returns matching file paths with line numbers. Requires the Vibe AI plugin. Read
get_file_outline Get a structural map of a theme file: functions, hooks, HTML sections. Requires the Vibe AI plugin. Read

Utilities

ToolDescriptionType
navigate Navigate the browser on a connected site. Useful for triggering page loads and live reload previews. Write
load_skill Load detailed instructions for a task. Available skills: setup-guide (connecting a site) and workflows (content management, plugin operations, REST API reference). Read

Connecting a WordPress Site

Once you've added the MCP server to your AI client, connecting a WordPress site takes about 30 seconds:

  1. Ask your AI to connect your site: "Connect my site at example.com"
  2. Click the authorization link the AI provides. It opens your WordPress admin.
  3. Approve access in WordPress. Credentials are stored automatically -- no passwords in the chat.
  4. Done. Ask the AI to run site_info to verify the connection.

Requirements: Any self-hosted WordPress site with REST API enabled (on by default since WP 4.7). Works with WordPress.org sites on any hosting provider. Not available for WordPress.com hosted sites -- use the official WordPress.com connector instead.

Optional: Install the Vibe AI plugin for file management, media uploads, WP-CLI, and live reload. Content management via the REST API and Abilities API works without the plugin.

Common Workflows

Content Management

Use rest_api for all content operations -- posts, pages, media, categories, tags, and settings.

# Create a draft post
rest_api(site_url, "POST", "/wp/v2/posts", '{"title":"My Post","content":"Hello world"}'

# List recent pages
rest_api(site_url, "GET", "/wp/v2/pages")

# Update site settings
rest_api(site_url, "PUT", "/wp/v2/settings", '{"blogname":"My Site"}')

Discover What's Available

Always discover before guessing. Different sites have different plugins and endpoints.

# See all REST API namespaces
rest_api(site_url, "GET", "/", fields="namespaces")

# See all post types
rest_api(site_url, "GET", "/wp/v2/types")

# See all plugin abilities (WP 6.9+)
discover_abilities(site_url)

Plugin Operations

For plugins with the Abilities API (WP 6.9+), discover abilities first, inspect the schema, then execute:

# Find what a plugin can do
discover_abilities(site_url, category="seedprod")

# Get details for a specific ability
get_ability_info(site_url, "seedprod/toggle-coming-soon")

# Run it
run_ability(site_url, "seedprod/toggle-coming-soon", '{"enabled":true}')

For plugins without abilities, check if they expose REST API endpoints via GET /.

WordPress Abilities API

WordPress 6.9+ introduces the Abilities API -- a way for plugins to declare self-describing operations with input schemas and annotations. This is the preferred way to interact with plugin-specific functionality.

Each ability includes:

When to use Abilities vs REST API: Use Abilities for plugin-specific actions (toggle features, run operations). Use REST API for standard content operations (posts, pages, media, settings). If a plugin has neither abilities nor REST endpoints, its data isn't accessible via MCP.

Safety & Security

Credentials encrypted. WordPress passwords are AES-256-GCM encrypted at rest and never exposed in AI conversations.

Delete goes to trash. Permanent deletion is blocked. The force=true parameter is stripped from all DELETE requests.

Posts default to draft. New content is saved as a draft unless you explicitly set the status to publish.

Your permissions apply. The AI respects your WordPress user role -- same access controls as wp-admin.

Authentication

WPVibe uses OAuth 2.0 for MCP client authentication and magic link email for user sign-in. No passwords are used or stored in the MCP flow. WordPress site credentials use application passwords authorized via a one-click link in wp-admin.

Data Handling

FAQ

What WordPress versions are supported?

Any self-hosted WordPress site with REST API enabled (WordPress 4.7+). The Abilities API features require WordPress 6.9+.

Does it work with WordPress.com?

No. WPVibe is for self-hosted WordPress sites (WordPress.org). For WordPress.com hosted sites, use the official WordPress.com connector in Claude's Connectors Directory.

What AI clients are supported?

Any MCP-compatible client: Claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, and others that support remote MCP servers with OAuth.

Is it free?

Yes. WPVibe is free to use. No credit card required.

How do I disconnect a site?

Ask your AI assistant to run remove_site with the site URL. The site is soft-deleted and can be re-connected at any time.

What plugins are supported?

Any plugin that exposes REST API endpoints or registers WordPress Abilities (WP 6.9+). This includes WooCommerce, Yoast SEO, AIOSEO, SeedProd, WPForms, and many others. Use discover_abilities and GET / to see what's available on a specific site.

Need help?

Contact us at john@wpvibe.ai.