Open for Agents: AI Toolkit with MCP

Publish WordPress content, forms and WooCommerce capabilities as MCP and WebMCP tools for compatible AI agents. You choose what agents may discover, and supported changes require approval before they run. Install the plugin, enable Standard Tools, review the catalog, then publish and verify it. Core works without an Open for Agents account, AI API key or paid license, and nothing is published merely because the plugin was activated. Open for Agents is for website owners who want agents to use reviewed site capabilities. It is not unrestricted WordPress administration. What you can do

• Publish reviewed public content, navigation, search, supported forms and WooCommerce capabilities.
• Give compatible agents one owner-approved catalog instead of exposing arbitrary WordPress actions.
• Verify the selected tools through the same public routes agents use.
• Keep private, dangerous, unsupported and unapproved actions out of public exports.
• Require trusted, argument-bound visitor approval before supported changes run.

Your first useful result

1. Install and activate Open for Agents.
2. Open Open for Agents > Setup and enable Standard Tools.
3. Review the catalog and confirm what may be public.
4. Choose Publish Safe Public and verify.
5. Ask a currently verified compatible agent a tested question, such as requesting the site's public information, and confirm the expected result.

Safe by default Activation alone publishes nothing. Public publishing and the browser runtime are disabled by default, and detected forms or endpoints do not become tools automatically. Safe Public includes only the reviewed public selection. An exact session-bound read such as cart inspection can be enabled without cart changes. Write tools still require the write framework and trusted, argument-bound visitor approval. Checkout, payment, order placement and account changes remain unavailable. Core requires no Open for Agents account, model API key, paid license or hosted service. Every included capability remains available without a paid upgrade. Supported content, forms and commerce

• WordPress public site information, post types, navigation, posts, search, individual posts and terms.
• WooCommerce 10.5.1 and 10.9.4: tested product discovery, session-bound cart inspection, visitor-approved reversible cart tools and declared HPOS compatibility.
• Contact Form 7 6.1.5 and 6.1.6: tested detection, reviewed publication, and certified execution for supported single-page contact and choice fields.
• WPForms Lite 1.9.9.2 and 1.10.2.1: tested detection, reviewed publication, and certified execution for supported single-page contact, number, choice, name and address fields.

Executable forms exclude captcha, consent, payment, upload, account, signature, calculation and multi-page workflows. Generic REST and AJAX mining is lower-confidence discovery for administrator review, not native provider support. Detection never means automatic publication; execution requires provider enablement, exact per-form opt-in and a trusted approval verifier. How agents discover the catalog MCP lets compatible external clients discover and call reviewed tools through a bounded server endpoint. WebMCP makes the same reviewed capabilities available to compatible browser agents on the relevant pages. Core can also publish the owner-approved catalog through llms.txt, an API Catalog, an MCP Server Card, Agent Skills and optional Agentic Resource Discovery output. AI crawler controls for robots.txt, validation, diagnostics and scan history help administrators understand the published surface. Optional Assistant The separately distributed Open for Agents Assistant is optional and is not included in this WordPress.org package. It is available only for approved deployments, not general public download. Core works without it. Documentation and demonstration https://www.youtube.com/watch?v=G1JDZRRWRBk

• Getting started guide
• Documentation
• Live WordPress demonstration
• Open for Agents website

1. Install and activate Open for Agents.
2. Open Open for Agents > Setup and enable Standard Tools.
3. Optionally scan for supported site-specific workflows.
4. Review the catalog, visibility, risk and execution policy.
5. Choose Publish Safe Public and verify to check, publish and verify the selected public tools.

Upgrading preserves existing settings, reviewed actions, scan history and publication state.

0.3.46

• Allow exact opt-in cart inspection without enabling write tools or an approval verifier. Cart changes keep their existing gates.

0.3.45

• Keep Agent Readiness Baseline exports internally consistent when a scan contains protected findings or several endpoint checks share the same response code.

0.3.44

• Let browser agents inspect the current cart without a redundant scope argument while preserving approval for cart mutations.