BeeClear WebMCP AI Visibility vs Code Engine – PHP Snippets, AI Functions & Automation for WordPress

AI visibility and WebMCP discovery for WordPress BeeClear WebMCP AI Visibility helps WordPress sites describe public content, navigation, media, forms and selected actions in a structured way for compatible AI agents and browser clients. The plugin adds WebMCP-style REST tools, agent discovery files, Markdown content output and OpenAPI metadata so automated clients can understand what the site offers before making requests. It is designed for site owners, publishers, agencies and developers who want their public WordPress content to be easier for AI assistants, browser agents and discovery tools to inspect without changing the normal frontend experience for visitors. What the plugin adds REST manifest: Provides a machine-readable entry point at /wp-json/beeclear-webmcp/v1/manifest. Agent discovery files: Adds optional /agent-manifest.txt, /agents-manifest.txt, /agents.txt and /.well-known/api-catalog endpoints, detects whether /llms.txt and /llms-full.txt are already available, and can optionally provide WebMCP fallback output for each llms file independently. Agent policy hints: Publishes controlled capability tokens, robots.txt cross-reference directives and optional DID / W3C Verifiable Credential identity hints with admin-side previews. Markdown for agents: Serves singular content as Markdown when compatible clients request Accept: text/markdown. OpenAPI schema: Publishes endpoint metadata at /wp-json/beeclear-webmcp/v1/openapi. Content discovery tools: Exposes public post search, post retrieval, post types, taxonomies, terms, menus and media metadata. Contact Form 7 tools: Detects Contact Form 7 forms, exposes field schemas and supports authenticated submission testing. Custom form definitions: Lets administrators describe frontend forms with selectors, fields, labels and field purposes. Custom REST functions: Exposes selected same-site REST endpoints as structured WebMCP tools. Discovery links and headers: Adds HTML head links and HTTP Link headers for configured agent-facing resources. Origin Trial support: Optionally sends a WebMCP Origin Trial token as an Origin-Trial header and HTML meta tag for Chrome 149+ production testing. Current browser API support: Registers page tools with document.modelContext, keeps a compatibility fallback for older navigator.modelContext builds, and can expose tools to configured secure cross-origin iframe hosts. Content signals: Adds optional headers and robots.txt directives for automated content-use preferences. Read-only tools can be exposed publicly. State-changing tools require the normal WordPress REST nonce and current-user context. Public agent endpoints include simple transient-based rate limiting to reduce accidental repeated load. Built for… Publishers and content sites If your site contains articles, guides, documentation or resources, the plugin helps compatible agents discover the right content and request a cleaner text version for analysis. Agencies and developers If you manage WordPress sites for clients, the plugin provides a structured way to expose public content, menus, media and selected business actions without building a custom agent API for each project. Businesses using forms If Contact Form 7 or custom frontend forms are part of your conversion flow, the plugin can describe form fields and purposes so authenticated browser-agent tests can work with structured input. AI visibility workflows If you are testing how AI clients understand a site, BeeClear WebMCP AI Visibility gives you manifest, Markdown, OpenAPI and discovery-file outputs from one admin-controlled plugin. Admin controls In wp-admin, go to BeeClear WebMCP to: Enable or disable the integration. Add a Chrome WebMCP Origin Trial token for production testing. Configure secure origins that may discover tools when this site is embedded in an iframe with allow="tools". Choose which public post types are exposed. Enable or disable content, navigation, media, form and custom-function tool groups. Configure agent discovery documents and content-signal preferences. Detect existing /llms.txt and /llms-full.txt files from another plugin or static file. Independently decide whether WebMCP should generate /llms.txt or /llms-full.txt fallback output. Preview the generated agent-manifest.txt, agents-manifest.txt and agents.txt policy files. Add optional trusted issuer hints and site-specific x- capability tokens. Describe Contact Form 7 fields and form purposes. Disable selected Contact Form 7 forms from WebMCP visibility. Define custom forms with CSS selectors and field metadata. Define custom functions that proxy to same-site REST endpoints. Run quick checks for the manifest, discovery files and enabled tools. Additional resources BeeClear website WordPress REST API documentation Translations BeeClear WebMCP AI Visibility is prepared for translation with the beeclear-webmcp-ai-visibility text domain. The source translation template is included in languages/beeclear-webmcp-ai-visibility.pot. Plugin interface strings and readme strings should be translated through translate.wordpress.org after the plugin is imported into the WordPress.org Plugin Directory. Reviewed translations approved as Current by a Project Translation Editor or General Translation Editor are distributed to sites automatically as WordPress.org language packs. Before each release, run scripts/update-translations.sh from the plugin directory to refresh the POT file, merge existing PO files, compile MO files and generate JavaScript translation JSON files when PO files are present. If you maintain a translation outside translate.wordpress.org, use the POT file as the source, review all machine-assisted output with a fluent human translator, and import the resulting PO file into the matching locale and subproject on translate.wordpress.org. External services This plugin does not send data to third-party external services by default. The plugin may send same-site HTTP requests to the WordPress site where it is installed. These requests are used to detect whether local discovery files such as /llms.txt or /llms-full.txt already exist, and to call administrator-configured custom REST functions. Custom REST functions are restricted to same-site endpoints or relative paths; external URLs are rejected. Administrators can optionally enter DID values for trusted VC issuers or agent identities. Those values are published as policy hints in agent-manifest.txt; the plugin does not contact those identifiers, send data to them, or verify them cryptographically. Administrators can optionally enter secure HTTPS origins for cross-origin WebMCP iframe testing. When a matching embedding page delegates allow="tools", the browser may expose this site’s registered WebMCP tool metadata and allow tool execution to that configured origin. The plugin does not contact those origins by itself. Administrators can optionally enter a Chrome WebMCP Origin Trial token. The plugin publishes that token as an Origin-Trial HTTP header and an HTML meta tag; it does not send the token to Google or any other external service.

Code Engine is a snippets manager that doesn’t stop at snippets. Yes, it runs your PHP and JavaScript exactly where and when you want: frontend, backend, on a schedule, or inside your content. But its real magic is what happens after you write a function: the same little piece of code instantly becomes a tool your AI chatbots can call, a step you can drag into a visual workflow, and an endpoint the outside world can trigger. One function, three superpowers. Most “code snippets” plugins stop at a textarea and a toggle. Code Engine treats your functions as first-class building blocks for the whole Meow Apps ecosystem, and for anything that can speak REST. Think out of the box, let your creativity flow, because the possibilities really are endless! ✨ For more, check the official website and come say hi on the Discord. Quick Intro Hello! ☀️ I built Code Engine because I was tired of pasting mystery snippets into functions.php and praying. I wanted a place where small bits of code are organized, safe, AI-assisted, and reusable everywhere. Here’s the idea. You write a function (or let the AI write it for you from a plain-English description). That function immediately shows up in three places: AI Engine: your chatbots and MCP clients (Claude, ChatGPT, Claude Code) can call it as a tool, with real arguments. Ask “how many orders shipped today?” and your chatbot runs your function to answer. Workflow Engine: your function appears in the step picker as its very own block. Drag it onto the canvas, wire it between an AI step and a Slack step, done. No glue code. REST / External tools: give it a secure endpoint and a token, then trigger it from Make.com, n8n, Zapier, a cron job, or a webhook. You never wrote an “integration.” You just wrote a function. Code Engine did the rest. 🤝 Core Modules 🧩 Snippets Manager Backend, Frontend, Persistent, Scheduled, Functions, and in-content (PHP/JS) snippets, all in one clean dashboard with tags, search, scope filters, and priorities. 🪄 AI-Assisted Coding Describe what you want in plain English and let AI Engine write the snippet: code, name, arguments, and scope included. Refine existing code or implement it straight from your comments. 🤖 Functions as AI Tools Every Function snippet becomes a function-calling tool and an MCP tool, so your AI Engine chatbots (and external AI agents) can actually do things on your site, not just talk. 🔀 Functions as Workflow Steps Workflow Engine surfaces each of your functions as its own draggable step. Your custom logic becomes a first-class citizen on the automation canvas. 🌐 External Access (REST) Expose any runnable snippet through a secured REST endpoint with a bearer token. Perfect for Make.com, n8n, webhooks, and scheduled external jobs. 🛡️ Safe Mode A snippet that throws a fatal error is automatically caught and disabled before it can take your site down. Code with confidence. ⏰ Scheduling Run a snippet daily at a chosen time via WP-Cron (reports, cleanups, syncs) without touching the server crontab. 🧱 Code Blocks & Shortcodes (Pro) Drop PHP or JS straight into a post or page with a Gutenberg block or the [code-engine] shortcode, with safety guards. 🧩 Snippets, the way they should be Code Engine organizes your code by scope, so each snippet runs exactly where it belongs: Persistent: runs everywhere (frontend and backend). Your everyday “add this to functions.php” code, but managed. Frontend: runs only on the public site. Backend: runs only in the admin. Function: a named, callable function with typed arguments and defaults. This is the reusable building block (see below). Scheduled: runs on a WP-Cron schedule, at the hour and minute you pick. Content (PHP / JS): runs inside a specific post or page, via a Gutenberg Code Block or the [code-engine] shortcode (Pro). Everything is searchable, taggable, sortable by priority, and importable/exportable. The CodeMirror editor gives you proper syntax highlighting and keyboard shortcuts (Cmd+S to save, Cmd+Enter to run). A nikic/php-parser pass validates your PHP before it ever runs. 🪄 Let AI write it for you Don’t feel like writing the boilerplate? Describe the snippet in plain language and Code Engine, powered by AI Engine, generates the whole thing: the code, a sensible name, a description, the right scope, and, for functions, the argument list with names, types, and defaults. Already have code? Ask the AI to modify it from a prompt, or write a few comments describing what you want and let it fill in the implementation. It’s pair programming, right inside your dashboard. ✨ The big idea: write once, use everywhere This is what makes Code Engine different. A Function snippet is not just code you call from other code. It’s a reusable capability that the rest of your stack can plug into. The moment you save it, the same function is available in three places at once: 1. As an AI tool, for chatbots and AI agents With AI Engine active, your functions are exposed through function calling and over MCP (Model Context Protocol). Your on-site chatbot can run them mid-conversation, and external AI agents (Claude, Claude Code, ChatGPT, OpenClaw) can call them too. Want a chatbot that checks stock, looks up a booking, or kicks off a process? Write the function; the chatbot gains the skill. 2. As a workflow step, for automation With Workflow Engine, every active function shows up in the Add-step picker as its own block, named after your snippet, with one input per argument. Drag it onto the canvas and wire it between other steps: an AI step that summarizes, your function that saves, a Social Engine step that posts. There’s also a generic “Execute snippet (by ID / by name)” step when you want to call one dynamically. You never write integration code; your function is the integration. 3. As a REST endpoint, for the outside world Give a snippet a custom endpoint name and a bearer token, and it’s instantly callable from anywhere: POST /wp-json/code-engine/v1/snippets-endpoint/your-endpoint Pass arguments as JSON in the body, secure it with a token, and trigger it from Make.com, n8n, Zapier, GitHub Actions, or a humble cron job. Automation without a middleware bill. 🛡️ Safe by default Running arbitrary code is powerful, so Code Engine takes safety seriously: Safe Mode catches fatal errors and auto-disables the offending snippet, so a typo never white-screens your site. REST whitelisting means global snippets only run on trusted REST routes by default, so you choose what to open up. Per-snippet tokens secure your external endpoints. Validation with a real PHP parser before code is saved. For developers who want fewer guardrails, there’s a “Bypass REST Security” option and filters (mwcode_rest_authorized, mwcode_rest_whitelist) to tailor exactly what’s allowed. Works beautifully with the Meow Apps family Code Engine is one engine in a connected set, each one useful alone, magical together: AI Engine: chatbots, content generation, and MCP. Turns your functions into AI tools. Workflow Engine: visual automation. Turns your functions into draggable steps. SEO Engine: smart, lightweight AI SEO. Social Engine: schedule and automate social posts. Why Code Engine? Reusable, not throwaway Other snippet plugins give you a place to paste code. Code Engine gives you a place to build capabilities that your AI, your workflows, and your external tools can all use. Native to WordPress Clean, fast, and built the WordPress way. No clunky external dashboards, no bloat. AI-native Write snippets with AI, expose them to AI. The whole loop lives in your wp-admin. Developer friendly REST API, MCP tools, function calling, scheduling, import/export, and plenty of filters to hook into. Cared for Part of the Meow Apps family, with regular updates and a real human behind it. 💕