BeeClear WebMCP AI Visibility
详情介绍:
- 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.txtand/.well-known/api-catalogendpoints, detects whether/llms.txtand/llms-full.txtare 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-Trialheader and HTML meta tag for Chrome 149+ production testing. - Current browser API support: Registers page tools with
document.modelContext, keeps a compatibility fallback for oldernavigator.modelContextbuilds, 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.
- 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.txtand/llms-full.txtfiles from another plugin or static file. - Independently decide whether WebMCP should generate
/llms.txtor/llms-full.txtfallback output. - Preview the generated
agent-manifest.txt,agents-manifest.txtandagents.txtpolicy 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.
安装:
- Go to Plugins > Add New.
- Search for BeeClear WebMCP AI Visibility.
- Click Install Now, then Activate.
- Open BeeClear WebMCP in wp-admin and review which tools and discovery files should be enabled.
- Download the plugin ZIP file.
- Upload the
beeclear-webmcp-ai-visibilityfolder to your/wp-content/plugins/directory, or upload the ZIP from Plugins > Add New > Upload Plugin. - Activate BeeClear WebMCP AI Visibility in the WordPress admin.
- Open BeeClear WebMCP and save the settings once to confirm your preferred configuration.
- Test the manifest at
/wp-json/beeclear-webmcp/v1/manifest.
屏幕截图:
常见问题:
Does the plugin change my public website design?
No. The plugin adds REST endpoints, discovery files, optional Markdown responses and discovery links. It does not replace your theme or normal frontend templates.
Are WebMCP read tools public?
They can be public if enabled in the plugin settings. State-changing tools still require the normal logged-in WordPress REST nonce/current-user context.
Do I need an Origin Trial token?
For local development, Chrome can use the chrome://flags/#enable-webmcp-testing flag. For production testing in Chrome 149 and newer while WebMCP is in Origin Trial, register your site origin in Chrome Origin Trials and paste the WebMCP token into the plugin settings. The plugin will publish it as an Origin-Trial HTTP header and an HTML meta tag on uncached pages. If a page cache, CDN or server cache serves HTML before WordPress runs, add the same header at the cache/server layer.
Can WebMCP tools work from a cross-origin iframe?
Yes, but only when the embedding page delegates permission with allow="tools" on the iframe and the embedded site lists that secure HTTPS origin in the plugin's Cross-origin WebMCP setting. Leave the setting empty for same-origin tools only.
Can I disable specific tool groups?
Yes. You can enable or disable content, navigation, media, Contact Form 7, custom form and custom function tools from the admin screen.
Does the plugin expose private posts?
No. The content tools are intended for public content. Review the exposed post-type settings before enabling public read access. Password-protected posts and pages are not exposed through public content tools or Markdown output.
Does Markdown output replace my normal HTML pages?
No. Markdown is served only for compatible requests that explicitly ask for it, or through the dedicated REST Markdown endpoint.
Can I use another plugin to generate llms.txt?
Yes. WebMCP detects existing /llms.txt and /llms-full.txt files and links to them from discovery metadata. Keep Let WebMCP generate /llms.txt disabled when another plugin or static file should own /llms.txt. /llms-full.txt has a separate fallback toggle.
Why does the llms status say "Detected external file"?
It means the public URL exists, but the response does not look like WebMCP-generated output. This is expected when another plugin or a static file serves the llms document.
Does the plugin require Contact Form 7?
No. Contact Form 7 integration is optional. If Contact Form 7 is not active, the rest of the plugin can still expose content, discovery files, OpenAPI metadata, custom forms and custom functions.
Can custom functions call external APIs?
Custom functions are limited to same-site endpoints or relative paths. The target endpoint should handle validation, permissions and business logic.
Where can I test the configuration?
Use the Tests screen under BeeClear WebMCP in wp-admin. It includes quick checks for the manifest, discovery files and common read tools.
更新日志:
- Added the plugin translation domain path and generated translation template for WordPress.org language-pack workflows.
- Added frontend script translation registration so generated JavaScript translation files can be loaded when available.
- Documented the translation workflow for plugin strings and WordPress.org readme translations.
- Added Chrome WebMCP Origin Trial token support for production testing.
- Updated browser tool registration for the current
document.modelContextAPI, JSON-string tool execution arguments and optionalexposedTocross-origin iframe support. - Replaced inline admin script tags with WordPress script enqueue APIs.
- Restricted discovery REST permissions to plugin settings and manager capability checks.
- Documented external-service behavior and clarified same-site custom endpoint limits.
- Returned taxonomy terms keyed by term ID for stable agent parsing.
- Added agent policy file management for
/agent-manifest.txt,/agents-manifest.txtand/agents.txt. - Added optional DID / W3C Verifiable Credential identity hints and custom capability tokens.
- Added detection for existing
/llms.txtand/llms-full.txtfiles served by another plugin or static file. - Split WebMCP fallback generation into separate
/llms.txtand/llms-full.txttoggles. - Removed the llms content-limit setting from the admin UI.
- Improved custom forms UX with collapsible form cards, collapsible field mappings and add-new-form behavior that preserves existing collapsed state.
- Moved admin styling into
assets/admin.cssand aligned the UI with the BeeClear Marketing Source Tracking admin style. - Cleaned up inline styles and unused CSS selectors.
- Initial release.
- Added WebMCP-style REST manifest and tool endpoints.
- Added
/agent-manifest.txt,/agents-manifest.txt,/agents.txtand/.well-known/api-catalogdiscovery documents, plus optional/llms.txtand/llms-full.txtcompatibility output. - Added Markdown output for singular content and a REST Markdown endpoint.
- Added OpenAPI schema output.
- Added content, navigation, taxonomy, menu and media read tools.
- Added Contact Form 7 discovery and authenticated submission testing.
- Added custom form and custom function configuration screens.
- Added admin quick checks for discovery and tool testing.