BeeClear WebMCP AI Visibility
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.
Top keywords
- txt17×1.68%
- webmcp14×1.38%
- wordpress12×1.19%
- content10×0.99%
- files10×0.99%
- discovery9×0.89%
- form9×0.89%
- rest9×0.89%
- ai8×0.79%
- custom8×0.79%
- agent7×0.69%
- contact7×0.69%
