| 开发者 | itamarsilvacc |
|---|---|
| 更新时间 | 2026年8月22日 15:28 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
toolname, tooldescription, toolparamdescription) to existing contact and lead forms. In-browser AI agents (Chrome with WebMCP) can then discover those forms on the page and fill them without guessing the DOM.
It is for site owners who already use a form plugin and want agents to fill lead, contact, or support requests. It does not replace your form plugin, and it does not submit the form for the visitor.
How it works
<form> markup. Lead and support forms never use toolautosubmit — a human confirms send.toolparamdescription.wp_head when set).llms.txt and it is not an SEO or GEO plugin.chrome://flags/#enable-webmcp-testing or a valid Origin Trial token, plus a WebMCP inspector extensionsilvaitamar-form-annotator-for-webmcp folder to /wp-content/plugins/.WebMCP is a browser API: the page declares tools in HTML. This plugin adds those attributes to WordPress forms so an in-browser agent can fill a contact or lead form from the current page.
No. WebMCP runs in the browser, on the page. MCP servers for IDEs (Cursor, Claude Desktop) are a different protocol. This plugin is not an MCP server and does not need an API key.
Yes, after you enable that form in Settings → Form Annotator and annotate it. The agent sees toolname, tooldescription, and toolparamdescription on the real form. The visitor still confirms submit.
No. Lead, contact, and support forms never get toolautosubmit. The human confirms the send.
No. Annotation is HTML on the form. Testing today uses Chrome with the WebMCP flag (or an Origin Trial token) and an inspector extension.
No. Those plugins still create and process the form. This plugin only adds WebMCP attributes when you enable a form. If a builder is not active, its adapter does not load.
No. It does not write llms.txt, sitemaps, or schema for search engines. It annotates forms for in-browser agents. The Lighthouse Agentic Browsing audit webmcp-form-coverage looks for these attributes on the real <form>; the plugin does not guarantee a score.
Use Chrome with chrome://flags/#enable-webmcp-testing (or an Origin Trial token under Settings → Form Annotator → Origin Trial) and a WebMCP inspector extension. Enable a form, view it on the front end, and confirm toolname, tooldescription, and toolparamdescription on the markup.
Translations are managed on translate.wordpress.org after the plugin is listed. Language packs install automatically — do not bundle .mo files for locales that already have a pack.