Skip to main content
Start free

Product

Features WordPress MCP server Manage multiple sites WooCommerce WP-CLI for AI For agencies How it works The Agent Safety & security About

Resources

Cookbook Works with Blog Docs Changelog Support Alternatives
Pricing Account
Docs Reference

Tools Reference

A practical map of the public WPVibe tool categories and what each group is for.

Site connection tools

  • connect_site connects a self-hosted WordPress site through application-password authorization.
  • list_sites shows the sites connected to your WPVibe account, and your usage for the last 24 hours.
  • site_info summarizes a connected site’s WordPress version, active theme, plugins, and WPVibe plugin capabilities.
  • remove_site disconnects a site from your WPVibe account.
  • get_profile returns the WPVibe account your AI is signed in to.
  • use_usage_reset spends one of your banked usage resets when you ask it to. See How to Check Your WPVibe Usage.

Content and media tools

  • rest_api calls WordPress REST API routes for posts, pages, media, users, settings, and plugin endpoints. When WPVibe is added from Claude’s Connectors Directory, reads use rest_api and writes use rest_api_write. Everywhere else rest_api does both. Deletes and other risky writes wait for your approval.
  • upload_media uploads an image from a URL into the WordPress media library.
  • request_upload and check_upload let you upload images from your own device: your AI gives you an upload panel, you pick the files, and they go to the media library with their original file names.
  • search_images searches Unsplash for stock photos to use in content.

Plugin and abilities tools

  • discover_abilities lists WordPress Abilities registered by plugins.
  • get_ability_info explains a specific ability’s schema, description, and annotations.
  • run_ability runs an ability after the AI has inspected what it does. An ability waits for your approval only when its plugin marks it destructive and it deletes something or runs code. See Safety, Limits, and FAQ.
  • code_snippet creates, edits, turns off and deletes code snippets through the free WPCode plugin, which you install yourself. New snippets are always saved switched off. You turn one on in wp-admin after reading the code; your AI can’t turn a snippet on. With plugin 1.20.4 and later it can turn off a snippet it created, and delete one after your approval (the snippet goes to WPCode’s trash). It never turns off or deletes a snippet you created.

Theme and file tools

  • create_draft_theme, get_preview_url, publish_draft_theme, and delete_draft_theme manage draft-first theme work. See The Draft Preview Sandbox.
  • create_classic_theme creates a new classic theme as a draft.
  • edit_file, write_file, and delete_file change draft theme files.
  • read_file, list_files, search_files, and get_file_outline read the draft theme, or the active theme when there is no draft (plugin 1.16.2 and later). For an administrator connection (a network administrator on multisite), read_file and list_files can also read plugin source and log files in wp-content, such as debug.log, read-only. Uploads and wp-config.php are never read, and known secrets are hidden before anything leaves your site.

Bulk and multi-site tools

  • show_fleet_dashboard shows the plugin, theme, and WordPress updates available across all your connected sites. On apps that show panels inline, it includes an Update button.
  • start_fleet_job runs a background job: updates across one or many sites, large bulk deletes, or clearing spam and trashed comments. The job keeps running after your chat moves on, checks each site before and after every update, and stops on a site that fails without stopping the others.

Inspection and workflow tools

  • run_wp_cli runs supported WP-CLI-style commands through PHP APIs. Risky commands wait for your approval. Database read queries run without one (inside a read-only transaction on plugin 1.20.0 and later).
  • get_page_html retrieves rendered page HTML for inspection.
  • audit_page runs a Google PageSpeed Insights audit on a public page: performance, accessibility, best practices, or SEO.
  • navigate moves a browser tab where you’re logged in to your site to the page you asked your AI to show you.
  • load_skill loads task-specific WPVibe instructions for Gutenberg, Elementor, SeedProd, classic and block themes, SEO, and more.
  • show_approval_panel and check_approval_status show an approval in the chat, on apps that can display one, and check whether you approved it.

Start with skills

For most real tasks, ask the AI to load the relevant skill first. Skills give the AI the rules, schemas, and workflow details it needs before it starts changing your site.

Saved skills

You can also save your own skills. Ask your AI to save one and save_skill stores it on your WPVibe account: a name, a one-line description, the instructions, and any reference files. It saves instructions you chose to keep, not your conversation.

A saved skill can be loaded from any AI app connected to the same WPVibe account, so one you save in Claude is there in ChatGPT or Cursor too. To see what you have saved, ask your AI to list your saved WPVibe skills. To remove one, ask it to delete that skill by name. Deleting your WPVibe account removes them all.

Approvals

Tools that change something risky wait for your approval, whichever tool runs them. On sites where an administrator has turned on Dangerously bypass approvals, they run right away and are recorded in the Approval Log. Turning on white label mode still asks, even then.