MCPify - WebMCP for WooCommerce
MCPify turns your WordPress and WooCommerce site into a set of structured WebMCP tools that AI agents can discover and call - so an assistant can search your content and browse your catalog through a defined, permissioned interface instead of scraping pages.
It is self-hosted and privacy-first: your content and the tools stay inside your own WordPress install, with no telemetry.
What it doesโ
MCPify serves the same tools three ways from one plugin:
- In the browser for WebMCP-capable AI agents, via
document.modelContext(with fallbacks). - Over REST at
/wp-json/mcpify/v1/manifestand/execute, for any HTTP agent. - As OpenAPI at
/wp-json/mcpify/v1/openapi, for Custom GPT Actions and similar tools, plus RFC 8288Linkdiscovery headers.
All authorization is decided server-side. The browser is never trusted.
WebMCP is an emerging web standard (from the W3C Web Machine Learning Community Group) that lets a page offer tools to an AI agent running in the browser. MCPify implements the current API - document.modelContext.registerTool() - and falls back gracefully on browsers that expose an older shape. Agents that cannot use the in-page API use the REST or OpenAPI endpoints instead.
Requirementsโ
- WordPress 6.4 or higher
- PHP 8.1 or higher
- WooCommerce (optional; only needed for the store tools)
MCPify ships ready to run. There is no composer install and no build step - upload, activate, done.
Installationโ
- Download the plugin ZIP.
- In your WordPress admin, go to Plugins > Add New > Upload Plugin.
- Choose the ZIP file and click Install Now.
- Click Activate.
Alternatively, extract the ZIP into wp-content/plugins/mcpify and activate it from the Plugins screen.
After activation, a new MCPify menu appears in the WordPress admin sidebar.
Verify it worksโ
There are two quick ways to confirm MCPify is live.
From the adminโ
Open MCPify > Dashboard. You should see the plugin status and a count of enabled tools. On a WooCommerce site, the WooCommerce tools appear automatically; on a plain WordPress site they are hidden.
From the REST manifestโ
Visit the manifest endpoint in your browser (replace the domain with your own):
https://example.com/wp-json/mcpify/v1/manifest
You will get a JSON document listing every enabled tool with its name, description, and input schema. This is exactly what an agent reads to discover what your site can do.
Free vs Proโ
| Capability | Free | Pro |
|---|---|---|
| WordPress read tools (search, posts, terms, site info) | โ | โ |
| WooCommerce catalog read tools (products, categories, stock) | โ | โ |
| REST + OpenAPI + in-page WebMCP | โ | โ |
| Security gate, rate limiting, activity log | โ | โ |
| Cart tools (add / update / remove / view) | - | โ |
| Checkout tools (coupons, checkout fields) | - | โ |
| Order tools (a customer's own orders) | - | โ |
| Custom Post Type tools | - | โ |
| Per-tool granular permission overrides | - | โ |
| Audit log export (CSV) | - | โ |
See Pro features for the full list.
Next stepsโ
- How it works - the three delivery surfaces and the request lifecycle.
- Tools reference - every tool, its type, and its parameters.
- Security model - access tiers, nonces, and what is never exposed.
- Admin guide - manage tools, settings, logs, and the request playground.
- Developer guide - register your own tools without editing core files.