SIRAPIX

<p>Snoodlr AI Assistant for WordPress and WooCommerce connects a WordPress or WooCommerce site to Snoodlr’s external AI assistant service to collect leads, take orders and more.</p>
<p>Version 2.8 provides the local plugin bootstrap, activation/deactivation handlers, settings defaults, permission-gated admin screens, nonce-protected admin view state, local admin assets, local database tables, local source detection and confirmation, signed query routes, optional WooCommerce commerce routes, pending-order idempotency safeguards, explicit cart capability metadata, idempotent same-session add-to-cart support, and optional frontend widget enablement.</p>
<p>Before an administrator connects Snoodlr, the plugin does not contact Snoodlr from WordPress, auto-inject a widget, require WooCommerce, copy full site content to Snoodlr, call AI/LLM APIs from WordPress, add analytics or tracking, or process online payments.</p>
<h3>External Services</h3>
<p>Snoodlr is an external AI assistant service. This plugin connects to Snoodlr only after an administrator explicitly clicks Connect to Snoodlr during setup.</p>
<p>Data shared with or exchanged with Snoodlr is limited to these categories:</p>
<ul>
<li>Connection onboarding. The hosted Snoodlr onboarding route at <code>https://app.snoodlr.com/en/app/integrations/wordpress/connect</code> receives the site URL, WordPress admin URL, callback URL, plugin version, WordPress version, PHP version, locale, timezone, site name, generated site public ID, WooCommerce active flag, connection state value, and source identifier. Because the administrator’s browser opens Snoodlr’s hosted onboarding page, Snoodlr may also receive standard browser request metadata such as IP address, user agent, and referrer.</li>
<li>Connection callback and credentials. Snoodlr returns a connection status, connection ID, connection secret when provided, and widget public key when provided. These values are stored locally in WordPress. The connection secret is used for HMAC request signing and is not exposed to frontend JavaScript.</li>
<li>Connection verification and disconnect. WordPress admin status screens may call <code>https://api.snoodlr.com/v1/public/wordpress/connection-verify</code>. Disconnecting may call <code>https://api.snoodlr.com/v1/public/wordpress/connection-disconnect</code>. These calls send the Snoodlr connection ID, timestamp, nonce, HMAC signature, and, for disconnect, a disconnect reason and source identifier.</li>
<li>Signed health and capability responses. After connection, Snoodlr may send signed requests to the local WordPress REST routes. WordPress may return plugin version, schema version, table verification status, indexed/dirty/failed object counts, last indexed time, enabled source-role counts, entity and mention counts, widget enabled/supported status, WooCommerce availability, commerce capability names, currency, and whether query routes are ready.</li>
<li>Signed content query responses. Snoodlr may send search queries, entity subjects, object IDs, WordPress object IDs, object kind/subtype filters, role filters, language, sort, limits, and an <code>include_body</code> flag. WordPress may return the echoed sanitized query parameters, relevant result IDs, WordPress object IDs, object kind/subtype, title, sanitized snippet or summary, URL, source role, published/modified dates, matched fields, evidence notes, relevance score, entity IDs, canonical entity names, entity type, confidence, source count, ambiguity candidates, primary context, latest updates, reference context, and, only when <code>include_body</code> is requested, a sanitized body excerpt limited by the plugin.</li>
<li>Signed WooCommerce product responses. If WooCommerce is active, Snoodlr may send product search text, filters, product ID, variation ID, quantity, requested attributes, order/sort values, and stock/category/tag filters. WordPress may return public product evidence including product ID, variation ID, product title, summary, URL, image URL, price, regular price, sale price, display price, currency, stock status, availability, published/modified dates, product attributes, categories, tags, matched fields, relevance score, and diagnostic counts for the product search.</li>
<li>Pending order and order status flows. If a visitor asks Snoodlr to create a pending order, Snoodlr sends the requested items, product IDs, variation IDs, quantities, attributes, customer name, customer email or phone, billing address fields, shipping address fields, and customer note to WordPress. WordPress creates a pending WooCommerce order and returns only the order ID, order number, status, total, currency, and created time. For order status, Snoodlr sends an order ID or order number plus an email or phone verification value; WordPress returns the same minimal order fields after verification.</li>
<li>Optional frontend widget. The frontend widget is disabled by default. If an administrator enables it after connecting Snoodlr, the plugin loads a local bootstrap script that loads Snoodlr’s hosted widget from <code>https://app.snoodlr.com/widget/loader.js</code> on public site pages. The local bootstrap exposes only widget URL, API base URL, widget public key, plugin version, locale, and widget position to frontend JavaScript. Widget API calls use <code>https://api.snoodlr.com</code>. Visitor conversations in the widget, and any information visitors type into the widget such as names, contact details, product requests, order requests, or order verification details, are processed by Snoodlr. Loading the hosted widget can also share standard browser request metadata with Snoodlr, such as IP address, user agent, and referrer/current page URL depending on browser policy.</li>
</ul>
<p>The plugin creates local indexing tables inside WordPress and lets administrators confirm which detected content sources may be indexed locally. Source choices start disabled and are enabled only after an administrator saves selected sources. Full site content, full product catalogs, posts, pages, custom post types, existing orders, customers, and coupons are not bulk-copied to Snoodlr by default.</p>
<p>When WooCommerce is installed, signed commerce routes can search locally indexed enabled product sources, check live product availability, create pending WooCommerce orders, and return minimal verified order status. Availability, price, stock, order creation, and order status use live WooCommerce APIs. The plugin does not process payment and does not return full customer profiles, full addresses for existing orders, private order notes, or payment metadata. Administrators can disconnect or revoke local access credentials without deleting local index tables or confirmed sources.</p>
<p>Administrators can disable the widget at any time. The plugin does not add hidden frontend credits, tracking pixels, analytics scripts, remote fonts, or unrelated third-party scripts.</p>
<p>Snoodlr Terms of Use: https://app.snoodlr.com/en/terms-of-use<br />
Snoodlr Privacy Policy: https://app.snoodlr.com/en/privacy-policy</p>
<h3>Privacy and Data Processing</h3>
<p>The plugin stores source confirmations, local index rows, entity mentions, connection status, signed API metadata, and widget settings inside WordPress.</p>
<p>Local indexing is limited to administrator-enabled, confirmed public sources. Drafts, private content, password-protected content, failed rows, not-indexable rows, orders, customers, and coupons are excluded from local content indexing.</p>
<p>Signed query routes return structured evidence only. They do not return full body text by default. Object requests with <code>include_body</code> return a limited sanitized excerpt, not unlimited raw content.</p>
<p>If the optional widget is enabled, visitor conversations occur through Snoodlr’s hosted widget and are processed by Snoodlr. The plugin exposes only non-secret widget configuration to the frontend: widget URL, API base URL, widget public key, plugin version, locale, and position.</p>
<h3>WooCommerce Support</h3>
<p>WooCommerce is optional. The plugin activates and its settings pages work without WooCommerce.</p>
<p>When WooCommerce is active and available, signed commerce routes can search locally indexed enabled product sources, check live availability and price, create pending orders, and return verified minimal order status. Product search may use local discovery snapshots, but availability, price, stock, pending-order creation, and order status are checked through live WooCommerce APIs.</p>
<p>The plugin does not process payments, mark orders paid, export the catalog, expose broad order search, return full customer profiles, or expose payment metadata/private order notes.</p>
<h3>Disconnect and Uninstall</h3>
<p>Disconnecting Snoodlr removes local connection credentials and prevents signed Snoodlr requests from authenticating. It does not remove local index tables, confirmed sources, or plugin settings.</p>
<p>Uninstall removes plugin options including connection credentials, settings, schema status, API error status, and widget settings. Local Snoodlr database tables are preserved by default to avoid unexpected merchant/site data loss.</p>
<h3>Limitations</h3>
<p>Production Snoodlr service URLs must remain accurate for the release build.</p>
<p>The plugin returns structured evidence to Snoodlr. Final answer synthesis happens in Snoodlr’s external service, not inside WordPress.</p>
<p>Online payments are not supported. Orders created by the commerce API are pending WooCommerce orders only.</p>


Snoodlr AI Assistant for WordPress and WooCommerce

Snoodlr AI Assistant for WordPress and WooCommerce connects a WordPress or WooCommerce site to Snoodlr's external AI assistant service to collect …

Syed Balkhi

SeedProd

<p>Your WordPress site just became MCP-ready. <a href="https://wpvibe.ai/?utm_source=wprepo&utm_medium=link&utm_campaign=liteplugin" rel="nofollow ugc">Vibe AI</a> (also known as WPVibe) is the Model Context Protocol server for WordPress, connecting your self-hosted site to any AI assistant that speaks MCP: Claude, ChatGPT, Cursor, Windsurf, OpenCode, and more. No copy-pasting between tabs. No switching between your AI chat and wp-admin. Tell your AI what you want, and it happens on your live WordPress site.</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/AsasOvrSWgI?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h4>The Model Context Protocol Server for WordPress</h4>
<p>Vibe AI is a complete MCP server implementation for WordPress. The Model Context Protocol, introduced by Anthropic and now adopted across the AI industry, lets AI assistants discover and call tools on connected services through a standard interface. Vibe AI packages every meaningful WordPress operation (content management, media uploads, theme file browsing, REST API access, and plugin abilities) as MCP tools your AI can call.</p>
<p>You install this free WordPress plugin, connect your site once, and every MCP-compatible AI client becomes a WordPress co-pilot. The Vibe AI WordPress MCP server handles authentication, encrypts credentials with AES-256-GCM, and relays your AI’s tool calls to the WordPress REST API. Your WordPress site, your data, your choice of AI.</p>
<h4>Connect Claude to WordPress</h4>
<p>Vibe AI is the easiest way to connect Claude to WordPress. Use it with Claude Desktop, Claude on the web, or Claude Code in your terminal. Once connected, ask Claude to draft a blog post, schedule an article, reorganize categories, update site settings, or run any WordPress task through conversation. Claude sees your WordPress site through the MCP bridge and responds with direct action, not just suggestions.</p>
<p>Connecting Claude to WordPress takes about 30 seconds. Install Vibe AI, open the plugin admin, click to authorize, then add the MCP server URL to Claude’s connectors. From that moment, Claude can manage WordPress content, search WordPress files, upload images, and interact with any WordPress plugin that exposes the Abilities API.</p>
<h4>Connect ChatGPT to WordPress</h4>
<p>Vibe AI is the ChatGPT WordPress plugin that actually connects the two systems instead of wrapping an API key. ChatGPT supports MCP servers directly in the web app and the desktop app, so once you add your Vibe AI MCP server URL, ChatGPT can read and write to your WordPress site through ordinary conversation.</p>
<p>Ask ChatGPT to turn a Google Doc into a WordPress blog post, find and tag every customer who downloaded a specific resource, update your About page in your own writing voice, or bulk-publish a content calendar. ChatGPT handles the language and strategy, Vibe AI handles the WordPress REST API calls behind the scenes.</p>
<h4>Connect Cursor, Windsurf, and Every MCP Client</h4>
<p>Vibe AI is not locked to a single AI vendor. Cursor, Windsurf, OpenCode, Claude Code, ChatGPT, Claude, and any other AI client that supports the Model Context Protocol can connect through the same MCP server URL. One WordPress MCP server, every AI assistant, no integration rewrite when you switch tools.</p>
<p>For developers, this means Cursor can edit your WordPress theme files with context-aware suggestions, Claude Code can run WordPress tasks as part of an agentic workflow, and Windsurf can scaffold new WordPress templates. For content creators and agencies, this means whichever AI writes best for your brand can publish directly to your WordPress site through the Vibe AI MCP bridge.</p>
<h4>AI-Powered WordPress Content Management via MCP</h4>
<p>Managing WordPress content through MCP has never been easier. Create blog posts, update pages, upload media, manage categories and tags, all through natural conversation with your AI assistant. Tell Claude to write a draft post about your latest product launch, ask ChatGPT to update your about page, or have Cursor reorganize your blog categories. Your AI assistant handles the WordPress REST API calls behind the MCP protocol, so you never have to touch wp-admin.</p>
<p>Vibe AI does not replace your AI assistant or lock you into a single provider. It works with every AI client that supports the Model Context Protocol, giving you the freedom to use Claude Desktop, ChatGPT, Cursor, Windsurf, OpenCode, or any future MCP-compatible AI tool for WordPress management.</p>
<h4>WordPress Abilities API Support for MCP</h4>
<p>WordPress 6.9 introduced the Abilities API, a powerful way for plugins to declare self-describing operations that AI assistants can discover and execute. Vibe AI fully supports this WordPress MCP integration. Your AI can discover what abilities your installed plugins expose, inspect their input schemas, and run them directly through natural conversation.</p>
<p>This means AI-powered WordPress plugin management works automatically over MCP. If a plugin registers abilities (WPForms, SeedProd, and others are adopting this standard), your AI assistant can interact with it without any custom integration. The WordPress Abilities API and Vibe AI together make every compatible plugin MCP-ready.</p>
<h4>Safely Edit WordPress Theme Files</h4>
<p>Vibe AI lets your MCP client browse and edit your WordPress theme files safely. Your AI can list files, search file contents, analyze code structure, and make edits through a draft theme workflow. The draft clones the active WordPress theme into a sandbox, makes changes there, and exposes a preview URL so you can see the results before going live. Your live WordPress site is never touched until you explicitly approve and publish.</p>
<p>Every file operation runs through WordPress capability checks, a path sandbox scoped to the draft theme, and PHP syntax validation before save. You keep the safety of wp-admin’s file editing guardrails while giving your AI a real place to work.</p>
<h4>WordPress WP-CLI Commands over MCP</h4>
<p>Run WordPress administration commands through your MCP client. Activate plugins, switch themes, update options, flush caches, query the database, and more, all via native PHP dispatch with a security-first command allowlist. No shell access required, no dangerous commands exposed. Your AI gets a productive WordPress admin surface without the risks of raw command execution.</p>
<h4>Smart MCP Notifications on Your WordPress Admin</h4>
<p>Every change your AI makes over MCP triggers a smart notification in your browser. Edit a post and you will see a toast with a direct link to view or edit the updated content. The Vibe AI notification system knows whether you are in the WordPress admin dashboard or viewing the frontend and adapts the link accordingly, so your workflow is never disrupted while your AI is working in the background.</p>
<h4>One-Click WordPress MCP Authorization</h4>
<p>Connecting your WordPress site to an MCP server should take seconds, not half an afternoon. Vibe AI does away with application passwords you type by hand and API keys you copy between tabs. Provide your WordPress site URL, click the authorization link that appears in your WordPress admin, and approve the connection. Your WordPress credentials are encrypted with AES-256-GCM and stored securely on Cloudflare-hosted Vibe AI servers. One click, done.</p>
<h4>WordPress MCP Server for Every Use Case</h4>
<p>Whether you are a blogger managing content, a developer building WordPress themes, or an agency managing multiple client sites, Vibe AI makes AI-powered WordPress management accessible through whichever MCP client you already use.</p>
<p><strong>Bloggers and Content Creators</strong> write and publish posts, manage media, organize categories and tags, and update WordPress site settings through conversation with Claude, ChatGPT, or any MCP assistant.</p>
<p><strong>WordPress Developers and Designers</strong> browse theme files, analyze code structure, and edit WordPress themes using a safe draft-preview-publish workflow. Build classic WordPress themes from scratch with AI-powered design directly from Cursor, Claude Code, or your favorite MCP client.</p>
<p><strong>Agencies and WordPress Site Managers</strong> connect client WordPress sites and manage content at scale. Use the WordPress Abilities API over MCP to interact with installed plugins. Automate routine WordPress tasks with whichever AI assistant fits the job.</p>
<h4>Full Vibe AI MCP Server Feature List</h4>
<ul>
<li>WordPress MCP server connection with one-click authorization and AES-256 encrypted credential storage</li>
<li>AI content management – create, update, and manage WordPress posts, pages, media, categories, and tags through AI conversation</li>
<li>Full WordPress REST API access exposed as MCP tools, including custom post types and plugin routes</li>
<li>WordPress Abilities API support – discover and execute plugin abilities on WordPress 6.9+ sites automatically</li>
<li>Connect Claude Desktop, Claude on the web, or Claude Code to WordPress via MCP</li>
<li>Connect ChatGPT’s web app and desktop app to WordPress via MCP</li>
<li>Connect Cursor, Windsurf, OpenCode, and any other MCP-compatible AI client</li>
<li>WordPress theme file browsing – list, search, and analyze theme file structure and code</li>
<li>AI WordPress theme editing with a draft-preview-publish workflow, safe sandboxed file operations, and PHP syntax validation</li>
<li>Classic WordPress theme builder – create new themes from scratch with AI-powered scaffolding</li>
<li>WordPress WP-CLI commands – run allowlisted admin commands through your MCP client via native PHP dispatch</li>
<li>WordPress media uploads – download images from URLs directly into your media library via MCP</li>
<li>Unsplash stock photo search – find high-quality images for your WordPress site from AI conversation</li>
<li>WordPress live reload – smart browser notifications when your AI makes changes, with context-aware navigation</li>
<li>Per-user WordPress scoping – live reload only activates for the WordPress admin using Vibe AI, not other team members</li>
<li>WordPress credential encryption – AES-256-GCM encryption at rest with per-site salting for application passwords</li>
<li>AI WordPress skills – on-demand workflow guides that teach your AI the right approach for each WordPress task</li>
<li>Progressive MCP tool discovery – your MCP client discovers WordPress tools as it needs them, keeping context efficient</li>
<li>Built on the open Model Context Protocol standard – no vendor lock-in, any MCP-compatible AI works</li>
<li>OAuth magic link authentication – no passwords typed into chat, no long-lived tokens on your laptop</li>
</ul>
<h4>Third-Party Service</h4>
<p>This plugin connects to the Vibe AI service at <a href="https://wpvibe.ai" rel="nofollow ugc">wpvibe.ai</a> to relay requests between your AI assistant and your WordPress site over the Model Context Protocol. When you connect your site, a WordPress application password is created and encrypted with AES-256-GCM on Vibe AI servers hosted on Cloudflare. All communication between the plugin and the Vibe AI MCP service occurs over HTTPS.</p>
<p>No data is collected, tracked, or shared with third parties beyond what is necessary to relay your AI assistant’s MCP requests to your WordPress REST API. Your content stays on your WordPress server.</p>
<ul>
<li><a href="https://wpvibe.ai/privacy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>
<h4>Third-Party Libraries</h4>
<p>Vibe AI bundles one third-party JavaScript library for use inside scaffolded classic starter themes:</p>
<ul>
<li><strong>Alpine.js</strong> v3.15.12, MIT License — <a href="https://alpinejs.dev/" rel="nofollow ugc">https://alpinejs.dev/</a> — included at <code>starter-themes/classic/assets/js/alpine.min.js</code>. Used as the interactivity layer (modals, dropdowns, tabs, accordions, sliders) for AI-generated classic themes. Not loaded outside scaffolded themes.</li>
</ul>
<h4>Built by SeedProd</h4>
<p>Vibe AI is built by the team behind <a href="https://www.seedprod.com/?utm_source=wprepo&utm_medium=link&utm_campaign=liteplugin" rel="nofollow ugc">SeedProd</a>, the most popular WordPress landing page and theme builder plugin, trusted by over 1 million WordPress websites. We have been building WordPress tools since 2012 and know what WordPress site owners need from AI-powered management tools.</p>
<h4>Better Than Custom AI WordPress Integrations</h4>
<p>If you have tried connecting AI to your WordPress site before, you have probably dealt with custom API wrappers, writing fetch calls in Python scripts, hand-rolling a ChatGPT Custom GPT, or copying content back and forth between Claude and your browser. Vibe AI eliminates all of that friction with a proper MCP server for WordPress.</p>
<p>Unlike custom scripts or one-off WordPress AI integrations, Vibe AI uses the Model Context Protocol, an open standard supported by Claude, ChatGPT, Cursor, Windsurf, and a growing list of AI tools. Connect your WordPress site once, use it with any MCP client. No vendor lock-in, no custom code to maintain for your AI WordPress workflow.</p>
<p>Unlike hosted AI WordPress services (AI Engine, GetGenie, Bertha, AI Power, WPCode AI, and similar bundled-AI plugins) that ship one model and one prompt style, Vibe AI lets you bring your own AI. Use whichever model reasons best for your task. Claude for long-form writing, ChatGPT for research, Cursor for theme editing, all connected through the same WordPress MCP server. Your data stays on your WordPress server. No third-party servers processing your WordPress content. Your WordPress site, your data, your control.</p>
<h4>Branding Guidelines</h4>
<p>This plugin is a product of SeedProd LLC. It has two names you may encounter:</p>
<ul>
<li><strong>WPVibe</strong> is the product brand used across our marketing site, documentation, and in-product UI (<a href="https://wpvibe.ai/" rel="nofollow ugc">wpvibe.ai</a>).</li>
<li><strong>Vibe AI</strong> is the name used on the WordPress.org plugin directory and inside the WordPress admin. WordPress.org’s plugin slug policy prevented us from using “WPVibe” as the listing name, so the plugin ships as “Vibe AI” on WP.org while the broader product is WPVibe.</li>
</ul>
<p>Both names refer to the same product. When writing about the WordPress plugin specifically, please use the correct spelling of either name:</p>
<ul>
<li>WPVibe (correct — product brand)</li>
<li>Vibe AI (correct — WordPress.org listing name)</li>
<li>WPvibe (incorrect)</li>
<li>Wp Vibe (incorrect)</li>
<li>VibeAI (incorrect)</li>
<li>vibe ai (incorrect)</li>
<li>Vibe Ai (incorrect)</li>
</ul>
<h4>WordPress MCP Server Resources</h4>
<ul>
<li><a href="https://wpvibe.ai/docs/?utm_source=wprepo&utm_medium=link&utm_campaign=liteplugin" rel="nofollow ugc">Vibe AI WordPress MCP Documentation</a></li>
<li><a href="https://wpvibe.ai/privacy/" rel="nofollow ugc">Privacy Policy</a></li>
</ul>


Vibe AI – MCP Server for WordPress. Connect Claude, ChatGPT & Cursor

MCP server for WordPress. Connect Claude, ChatGPT, Cursor & other AI assistants to manage content, edit themes & automate your WordPress site.

Snoodlr AI Assistant for WordPress and WooCommerce vs Vibe AI – MCP Server for WordPress. Connect Claude, ChatGPT & Cursor