Open for Agents: AI Toolkit with MCP

by Matt Gibbs

Description

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

Install and activate Open for Agents.
Open Open for Agents > Setup and enable Standard Tools.
Review the catalog and confirm what may be public.
Choose Publish Safe Public and verify.
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

External services

Core does not contact an external service operated by Enoki Limited or another provider.

Published MCP Server Card and Agent Skills documents contain $schema identifiers at static.modelcontextprotocol.io and schemas.agentskills.io. The plugin does not request those URLs, transmit data to them or require them to be available.

Deep scan is an optional developer integration point, not a bundled service. When enabled, the plugin passes a page URL and non-secret request settings only to locally installed code attached to open_for_agents_deep_scan_report; it never passes authentication cookies, authorization headers or WordPress nonces. A developer who connects an external renderer must disclose that separate service, its data, terms and privacy policy. Without an integration, the plugin uses its same-site static scan and sends nothing externally.

Privacy

Core does not create an Enoki Limited account, load remote tracking code or transmit site data to an Open for Agents service.

Normal scanning and verification make HTTP requests to the WordPress site’s own public or administrator-authorized same-origin URLs. Authenticated scan cookies are used only for same-origin requests during that scan and are never included in public output.

Any configured third-party renderer may process page URLs, request context or rendered content and must be governed separately.

Terms: Open for Agents terms

Installation

Install and activate Open for Agents.
Open Open for Agents > Setup and enable Standard Tools.
Optionally scan for supported site-specific workflows.
Review the catalog, visibility, risk and execution policy.
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.

Screenshots

See a compatible agent use a reviewed public Core capability; the separately deployed Assistant shown is optional and is not included in Core.
Review each capability's visibility, risk and execution policy before publication.
Publish and verify the selected tools through the public routes agents use.
Confirm tested provider support and distinguish lower-confidence discovery.

Faq

Does activation immediately expose my site to agents?

No. Public publishing and the browser runtime are disabled by default. An administrator must review and enable them.

Does the plugin send my content or credentials to Open for Agents?

No. Core sends no site content, credentials, scan results or visitor data to Enoki Limited or Open for Agents. A separately configured deep-scan renderer controls its own data handling.

Do I need an AI API key?

No. Scanning, review, validation, publication, discovery endpoints, MCP and WebMCP runtime support do not require a model API key.

Which integrations are supported?

The scanner supports WordPress core, WooCommerce core, Contact Form 7 and WPForms Lite. Selected custom REST and AJAX surfaces appear as lower-confidence review candidates.

Can an agent place an order or make a payment?

No. Checkout, payment, order placement and account changes are excluded. Cart inspection is an exact opt-in session read. Cart changes remain disabled by default and require trusted, argument-bound visitor approval.

What is published?

Only the administrator-approved public catalog and enabled discovery formats. Private scan evidence, cookies, credentials, nonces, logs and admin-only data are not published.

Reviews

Changelog

0.3.52

Normalize successful environment diagnostics in Agent Readiness exports.

0.3.51

Fix repeated Agent Readiness checks.

0.3.50

Add a privacy-minimized Agent Readiness evidence export with exact capability and document identities while retaining the version 1 export.

0.3.49

Return compact product summaries with accurate counts, resumable pages and numeric price ordering.