MCP App Store
by KeenEthics
WPVibe icon

WPVibe MCP Server for ChatGPT

By SeedProd, LLC

Overview

WPVibe connects ChatGPT to self-hosted WordPress sites so users can manage content, inspect plugins and themes, upload media, run safe WordPress admin commands, use plugin abilities, and build draft themes through conversation. It includes tested WordPress skills and playbooks for Gutenberg, Elementor, SeedProd, classic themes, editable fields, design, and SEO audits, plus one-click authorization, permission-checked tools, and draft-preview-publish workflows so changes are visible and reviewable before risky actions.

How to connect

  1. ChatGPT: Open the WPVibe listing in the ChatGPT app directory and choose Connect. ChatGPT listing WPVibe exposes 36 tools here.

Tools

audit_page

ChatGPT
Run a Google PageSpeed Insights (Lighthouse) audit on a public URL. Covers four categories — you choose which to run: performance (default), accessibility, best-practices, seo. Returns each category's score plus the actionable items to fix. Pick categories based on what the user asked: - "why is my site slow / speed check" → performance (Core Web Vitals, field data, opportunities + diagnostics). - "accessibility / a11y / WCAG / screen-reader" → accessibility (missing alt text, form labels, contrast, heading order — all fixable via edit_file / rest_api_write / content edits). - "best practices / security / console errors" → best-practices. - "on-page SEO basics" → seo (for a deep SEO audit, use the seo-audit skill instead — this is only Lighthouse's shallow checks). - General "audit / health check my site" → run all four. Then ACT on the results: each item carries a stable audit id. Performance → theme <head> edits (render-blocking/preload), image re-upload, culprit plugin via site_info, caching. Accessibility → alt text, labels, contrast, headings. Server-level items (gzip/Brotli, CDN, HTTP/2) you can only advise on — say so. Notes: - The URL must be publicly reachable. Staging, password-protected, localhost, or firewall/challenge-gated sites can't be audited (clear error, not a fake score). - Lab performance scores vary ±5-15 pts run-to-run; don't chase small deltas. Prefer field data when present. - Running all four is only marginally slower than one; a very heavy site may still time out — try a lighter page_url. - Audit a page ONCE per task and work from that result. Results are cached for 3 hours; do not re-audit after each edit. Pass refresh=true only when the user asks to re-measure after changes are live. If an audit fails, do not retry it; the message says what to do instead.

check_approval_status

ChatGPT
Check the status of a pending destructive operation by its op id (returned as approvalOpId when an operation needs approval), OR of a background fleet job by its job id (fj_..., returned by start_fleet_job). Operations return one of pending, approved, executing, executed, failed, declined, or expired, plus the result once executed; execution_status preserves the execution lifecycle when the outcome is failed; fleet jobs return working, input_required, completed, failed, or cancelled with per-site progress. Use this to learn the outcome after a user approves in the inline panel, or to poll until the status changes.

check_upload

ChatGPT
Check whether the user has finished uploading the image(s) they were asked to pick via request_upload. Returns one of: - still waiting — the user hasn't uploaded anything yet. Wait a few seconds and call again. - ready — returns a staging URL for each uploaded image. Pass each URL to upload_media to add it to the WordPress media library. - expired — the link expired before the user uploaded. Call request_upload again for a fresh link. The user may add more images over time, so the list can grow between polls. Poll this rather than asking the user repeatedly; stop once the user says they're done or the count matches what they intended.

code_snippet

ChatGPT
Create or update a code snippet on a connected WordPress site via the WPCode plugin (free; WPCode must be installed and active on the site — if it is not, ask the user to install it themselves; that installation is their opt-in to snippet-based code). WPVibe checks for WPCode before asking the user for approval, and a site without it gets a clear refusal here rather than a failed approval. The snippet is always written disabled, and only the user can enable it, in wp-admin (WPCode runs its own fatal-error check when they do); you cannot activate, re-activate, or deactivate snippets. On sites with WPVibe plugin 1.19.2+, a create (up to 10 per site per 30 minutes) and an edit to a disabled snippet WPVibe created (unchanged since, same code_type) are saved immediately with no approval prompt, because enabling is the user's review: the result includes an enable_url, and you must give it to the user and tell them to review and enable the snippet. Every other write (an enabled snippet, a snippet the user wrote or edited, a code_type change, older plugins) needs the user's explicit approval in a browser panel that shows the exact code, type, and location; nothing is written until they approve, and the approved result (via check_approval_status) includes the enable_url. code: exact snippet body. For code_type="php" do NOT include the <?php opening tag (WPCode adds the execution context); "universal" keeps its <?php ... ?> tags; html/js/css/text are raw markup (literal <script> tags are fine here, unlike run_wp_cli). location must be one of WPCode's registered location slugs — common Lite slugs: everywhere, frontend_only, admin_only, on_demand (shortcode-style), site_wide_header, site_wide_body, site_wide_footer, before_post, after_post, before_content, after_content, before_paragraph, after_paragraph, before_excerpt, after_excerpt, between_posts, archive_before_post, archive_after_post, admin_head, admin_footer. An invalid slug returns the site's valid list. insert_method="auto" runs the snippet at the location once enabled; "shortcode" returns a literal [wpcode id=N] to embed in content instead (pairs with location="on_demand"). action="update" edits an existing snippet (requires id) and can change code/title/type/location but never turns a snippet ON: html/js/css/text snippets keep their current on/off state, while an update to a php/universal snippet always lands disabled — the user must re-enable it via enable_url (WPCode re-checks the edited code then). code_type values blocks and scss require WPCode Pro and are not supported here.

connect_site

ChatGPT
Connect a WordPress site. Call with just site_url first — returns a one-click authorization link the user opens in their browser to approve (like Jetpack). Only pass auth if the user explicitly provides credentials. After connecting, the site stays linked to the user account.

create_classic_theme

ChatGPT
Create a new classic WordPress theme from scratch as a draft. The live site is unchanged until you publish. Scaffolds style.css, index.php, functions.php, header.php, and footer.php into a draft directory: a complete, previewable starting point. Refine these and add single.php, page.php, etc. as needed. Use write_file/edit_file to build the theme, get_preview_url to preview, and publish_draft_theme to go live.

create_draft_theme

ChatGPT
Clone the active theme into a sandboxed draft for safe editing. All file operations (read_file, edit_file, write_file, delete_file, search_files, list_files) are scoped to the draft. Usage: - You MUST call this before any file operations — they will fail without a draft. - The live site is never touched until you explicitly call publish_draft_theme. - Only one draft can exist at a time per site.

delete_draft_theme

ChatGPT
Delete the draft theme and discard all changes. The live theme is unaffected. Usage: - Use this to cancel an editing session or start over. - This is irreversible — all draft changes are lost.

delete_file

ChatGPT
Delete a file from the draft theme. Cannot delete files outside the draft theme directory. Usage: - This is destructive and cannot be undone within the draft session. - Only deletes files in the draft — the live theme is never touched until you publish. - If you're unsure, use read_file to inspect the file first.

discover_abilities

ChatGPT
Discover what a connected WordPress site can do via the Abilities API (WP 6.9+). Lists all abilities registered by plugins with names, descriptions, and schemas. Usage: - Run this before run_ability to see what's available. - Use category to filter by plugin or domain (e.g., "seedprod", "woocommerce"). - If the site has no abilities, the plugin may not support the Abilities API yet — use rest_api instead.

edit_file

ChatGPT
Replace exact text in a draft theme file. The plugin runs str_replace server-side: send old_content + new_content and the file content stays on the server. Usage: - If you already know the exact text to find (you wrote it this session, you're doing a known token swap, the user gave you the value), call edit_file directly. No read_file needed — the file content does not need to be in your context. - If you do not know the exact text, use search_files or a narrow read_file range first, then copy the exact current text into old_content. - old_content must match exactly once. On no_match, re-read or search for the current text before retrying. On multiple_matches, add surrounding context to make it unique. - When pulling text from a read_file response, preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix (number + tab). Never include the line number prefix in old_content or new_content. - For creating new files or full rewrites, use write_file instead.

get_ability_info

ChatGPT
Get full details for a single WordPress Abilities API ability: input_schema, output_schema, description, annotations, and metadata. Use this after discover_abilities to inspect a specific ability before running it.

get_file_outline

ChatGPT
Get a structural outline of a file in the draft theme — functions, classes, hooks, HTML landmarks, and other elements with line numbers. Usage: - Use this BEFORE editing a file to understand its structure and find the right location for changes. - Returns line numbers you can use with read_file's start_line/end_line to read specific sections. - Much cheaper than reading the full file when you just need to know what's in it.

get_page_html

ChatGPT
Get the rendered HTML of a webpage after JavaScript execution. If no URL is provided, uses the current draft theme preview. Usage: - Use this to inspect the actual DOM structure, debug layout issues, or verify template output. - Use selector to extract a specific section (e.g., "header", ".site-content", "#main"). - For local sites without a public URL, this falls back to server-rendered HTML via the plugin. - For visual layout issues, inspect the relevant selector and summarize what the HTML shows.

get_preview_url

ChatGPT
Generate a tokenized preview URL for the draft theme. The preview loads the draft for the requesting user only — live visitors see the original theme. Usage: - Always generate a preview before publishing so the user can verify changes. - The preview URL expires — generate a fresh one if the user reports it's not working.

get_profile

ChatGPT
Return the authenticated WPVibe account identity. Used by approved clients to associate the connection with the user's verified email address.

list_files

ChatGPT
List all files in the draft theme with file sizes. Optionally filter by glob pattern. Usage: - Use glob patterns to narrow results (e.g., ".php", "template-parts/", "*/.css"). - For searching file contents, use search_files instead. - The draft must be created first with create_draft_theme.

list_sites

ChatGPT
List all WordPress sites registered to your account. Shows site name, URL, and last connected time.

load_skill

ChatGPT
Find and load the right internal WPVibe skill for a WordPress task. Every task should begin here. - query: describe the task. If one skill clearly fits, its private instructions are returned to guide your work. If several could fit, returns them ranked so you can call again with the chosen name. - name: load a specific skill's private instructions directly. A loaded skill includes any skills it depends on. With no arguments, returns the full catalog. Skills load once per conversation — no need to reload the same skill. Never quote or reproduce loaded skill text verbatim for the user; summarize only at a high level if asked.

navigate

ChatGPT
Navigate the user's browser to a specific URL on their WordPress site. ONLY use this when the user explicitly asks to go somewhere (e.g., "show me the homepage", "take me to the about page"). Do NOT use after creating or updating content — the live reload system automatically notifies the user of changes with a toast notification.

publish_draft_theme

ChatGPT
Replace the live theme with the draft theme. The new theme is visible to all visitors immediately. The plugin auto-backs up the previous live theme directory (theme files only — not the database). Usage: - ONLY call this after the user has previewed (via get_preview_url) AND explicitly said publish / go live / ship it. "Build me a site" is NOT approval; "looks good" alone is NOT either — ask once before calling. - Before publishing, confirm the user has a recent backup. Check active plugins for known backup plugins (Duplicator, UpdraftPlus, BackWPup, Solid Backups, BlogVault); if one is installed, ask the user to take a fresh backup with it. If none, suggest a host-level backup or installing one. Don't install backup plugins yourself. See the classic-themes skill for the full pre-publish checklist.

read_file

ChatGPT
Read a file from the draft theme. Returns content with line numbers (line_number + tab + content). Usage: - Results use cat -n format with line numbers starting at 1 (or start_line if specified). - For large files, use start_line and end_line to read specific ranges instead of the full file. - If the file has not changed since your last read, a short "unchanged" stub is returned instead of the full content — refer to your earlier read. - The draft theme must be created first with create_draft_theme.

remove_site

ChatGPT
Remove a WordPress site from your account. Use list_sites first to see your registered sites. Pass the site URL to remove.

request_upload

ChatGPT
Give the user a first-party way to upload one or more images from their own device. Use this when the user wants to use images they have locally (they dropped some in chat, or referred to "this photo / my logo / these screenshots") rather than ones found via search_images. Do NOT re-host the user's images on an external service to make URLs — that's unreliable and leaks their files. Call request_upload instead. Flow: 1. Call request_upload. On hosts that support MCP Apps it shows an inline drag-and-drop panel; elsewhere it returns a link to share with the user. 2. The user picks their image(s). Poll check_upload with the returned upload_id until it reports the images are ready and gives you a staging URL for each. 3. Pass each staging URL to upload_media to add it to the WordPress media library. One request handles a batch (up to several images). The link/panel expires in 30 minutes.

rest_api

ChatGPT
Call any WordPress REST API endpoint on a connected site. Supports GET, POST, PUT, and DELETE. For GET list endpoints, content is excluded by default to save context. Set fields="all" to get the full response, or fields="id,title,content" to pick specific fields. Safety: DELETE always moves to trash (force=true is stripped). New posts/pages default to draft unless status is explicitly set. TIP: If unsure which endpoints exist, first GET / to see available namespaces, then GET /wp/v2/types to see registered post types.

run_ability

ChatGPT
Execute a WordPress Abilities API ability by name on a connected site. First use discover_abilities to see what is available, then run any ability. The HTTP method is derived from the ability's annotations: readonly => GET, destructive AND idempotent => DELETE, otherwise POST. If you omit the readonly/destructive/idempotent flags, the wrapper fetches the ability metadata inline and picks the correct method automatically. Pass the flags explicitly only if you already know them and want to skip the extra fetch.

run_wp_cli

ChatGPT
Run a WP-CLI command on a connected WordPress site via native PHP APIs (no wp-cli binary needed). This is not a shell: do not use pipes, redirects, &&, ;, backticks, or command substitution. Common commands: plugin/theme list, option get/update, user list, post list/create/update/delete, post meta get/update, taxonomy/term list, media list, comment count/list, rewrite list/flush, cache flush, cron event list, db query, search-replace. db query is SELECT-only; use {prefix} for the table prefix and --limit=N when needed (default 100, max 1000). All output is JSON. Write/destructive operations may ask for confirmation; retry the same command with confirm_write=true only after the user approves.

search_files

ChatGPT
Search file contents across the draft theme (grep-like). Returns matching lines with line numbers and surrounding context. Usage: - Pattern is a substring match (not regex). Use case_sensitive: false (default) for broader matches. - Results show 1 line of context above and below each match for orientation. - Use max_results to limit output when pattern is broad. - For finding files by name/path, use list_files with a glob pattern instead.

search_images

ChatGPT
Search Unsplash for high-quality stock photos. Returns hotlinkable image URLs with photographer attribution. Usage: - Use descriptive, specific queries for better results (e.g., "modern office workspace" not just "office"). - Images are hotlinked from Unsplash — use upload_media to add them permanently to the WordPress media library. - Always include photographer attribution when displaying images.

show_approval_panel

ChatGPT
Optionally render an inline Approve/Decline panel for a pending destructive operation (the op_id returned as approvalOpId). Only useful on hosts that render MCP Apps inline; on most clients it does nothing visible. The approval URL from the approval-required response is the one approval path that works on every client, so it belongs in the user-visible reply whether or not the panel renders. One call per operation is enough. Only the user can approve. check_approval_status (or the user's next message) reports the outcome.

show_fleet_dashboard

ChatGPT
THE tool for "what updates are available across my sites": one call surveys available plugin, theme, and WordPress core updates across ALL connected sites and renders them as an interactive panel (per-site rows, checkboxes, a working Update button that starts a real background job). Strongly prefer this over looping run_wp_cli plugin/theme list calls per site, which is slow and spends many metered calls. Pass job_id (fj_...) instead for live progress of a running fleet job with approve/cancel buttons. On hosts that do not render inline panels it returns per-site guidance instead; whether or not the panel renders, the plain URLs from tool responses are what reach the user in the reply. One call per job is enough or per conversation topic.

site_info

ChatGPT
Get metadata about a connected WordPress site: name, URL, WP version, active theme, installed plugins, WP-CLI availability, and performance timings when the WPVibe plugin is active. Usage: - Run this first when working with a new site to understand what's installed. - Check active_theme before content/theme work; missing templates can affect how new posts or pages render. - When the user complains about speed, quote the performance breakdown so they can see whether time is in the Worker, network, or WordPress host.

start_fleet_job

ChatGPT
THE tool for updating plugins, themes, or WordPress core across one or many connected sites, AND for large bulk deletions (more than ~25 users, posts, or comments) that would time out inline, AND for clearing all spam, trashed, or pending comments on one or many sites: it starts a background fleet job that runs server-side after this call returns (nothing blocks the chat). Strongly prefer this over looping run_wp_cli plugin/theme update per site, and over a single huge run_wp_cli user/post/comment delete - the job chunks the work, survives the relay timeout, and survives the conversation ending. Each site is processed one step at a time with a dry-run recheck before every update, a version verification after it, and per-site halt on failure so one broken site never stops the rest. Comment cleanup: {"kind":"bulk_cli","family":"comment_delete","status":"spam"} deletes every spam comment on each listed site (the job counts them itself with comment count, deletes oldest first, and shows the per-site count on the approval page); no ids needed, works across many sites in one job. Do not enumerate spam ids with comment list for this. Long mechanical write lists (meta updates, term assignments, option writes, flag-only post updates, product field updates; anything you have already fully authored): {"kind":"command_list","commands":["post meta update 12 _yoast_wpseo_title \"...\"", "..."]} runs them server-side one call each, survives the daily-cap pause and the conversation ending, and returns per-command receipts with the failed commands listed so you can retry those inline. One site per job, up to 2000 commands. Approval-gated commands (deletes with --force, mutating SQL, live search-replace, role changes) fail individually with needs_approval; run those inline instead, and never put five or more of them in a row: after 5 consecutive gated commands the rest of the list is skipped unrun. The same happens after 5 consecutive commands failing with the same error (including protected-meta refusals for different keys): fix the shape, then re-run the remainder. Lists also stop after 10 consecutive unsuccessful commands or 15 unsuccessful commands among the last 20 completed commands. Completed changes and receipts are preserved; review failures and verify unknown outcomes before submitting the remaining work as a new job. Not for authoring content one post at a time: write the content first, then list the commands. Two-phase: call once to get the plan + estimated call cost (each background step spends from the account's normal daily call allowance), then repeat with confirm=true to start. Jobs containing core_update steps pause for a browser approval before touching core; the job's status URL is where the user approves. Poll progress with check_approval_status({ op_id: "<fleet job id starting with fj_>" }), and the returned status URL belongs in the user-visible reply: it is the live progress page and works on every client. Sites already covered by an active fleet job are refused (per-site lock). Steps default to everything with an available update; pass explicit target slugs to update only those.

upload_media

ChatGPT
Upload an image from a URL to the WordPress media library. Downloads the image server-side and adds it as a media attachment. Usage: - Use this after search_images to permanently add images to WordPress (hotlinks may break). - Returns the attachment ID and local URL for use in posts, pages, or theme templates. - Set alt_text for accessibility — it's used in the img alt attribute. - If the host blocks outbound downloads, use the original image URL temporarily or ask the user to upload the image in wp-admin, then look up the attachment with rest_api.

use_usage_reset

ChatGPT
Spend one of the user's banked WPVibe usage resets, which clears their rolling 24-hour usage count right away. Call only when the user asks to use a reset (for example "use my reset"). It acts on the signed-in account only and takes no arguments.

write_file

ChatGPT
Create a new file or fully overwrite an existing file in the draft theme. For surgical edits to existing files, use edit_file instead — it is more token-efficient and less error-prone. Usage: - Allowed extensions: .php, .css, .js, .json, .html, .txt, .svg - PHP files are syntax-checked before saving — if syntax is invalid the write is rejected. - You MUST use read_file first before overwriting an existing file. This tool will send the entire file content, so prefer edit_file for small changes.

Capabilities

WritesInteractive

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/wpvibe"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/wpvibe)