By : codemypain Published On Tuesday, September 22, 2026, 12:37 In WordPress
Agent Gateway is the missing production layer that lets AI assistants like Claude, ChatGPT, and Cursor connect to your self-hosted WordPress & WooCommerce site over the open Model Context Protocol (MCP). It ships a spec-compliant OAuth 2.1 server, per-agent permissions, and a human approval queue, so an agent can search your catalog, check stock, and draft an order, but never touches anything you have not explicitly allowed. Everything runs on your own domain. No SaaS backend, no phone-home, no API keys to copy by hand.
Try the live demo before you buy: agent-gateway-demo.instawp.site is a real WooCommerce store with the plugin active. Inspect the live OAuth endpoints yourself: resource metadata (RFC 9728) and authorization server metadata (RFC 8414). Or point any MCP client at https://agent-gateway-demo.instawp.site/wp-json/agw/mcp and watch the whole flow work.
allow, hold, or deny), with optional rate limits and auto-approve constraints. Change or revoke any of it live.Agent Gateway is not a demo of what AI could do. It is the governance layer for what agents actually do on your store:
Add your site as a remote MCP server in Claude, ChatGPT, or Cursor. Discovery, dynamic client registration, and the OAuth handshake all happen automatically, with no keys to paste. On a single consent screen you choose exactly which scopes each agent gets, and you can change or revoke them any time.
Agents are never mapped to your admin account. Each is a zero-capability principal. Set every ability to allow, hold (queue for approval), or deny, add hourly rate limits and JSON auto-approve constraints (for example a maximum order value), and revoke access live no matter what tokens are already out there.
Write actions can be held for your review. Approve or reject from a clean queue, with constraint-based auto-approval for the routine cases, a global kill switch, and per-agent dry-run mode. Approvals run as the agent, never as your admin account, re-validating the arguments against the current schema before anything executes.
Almost every free “connect AI to WordPress” plugin funnels your store through a hosted service you do not control, so your catalog, orders, and customer data pass through someone else’s backend, and you pay a monthly fee forever. Agent Gateway is the opposite:
Self-hosted MCP has been stuck on application passwords and hand-copied tokens. Agent Gateway brings the full standard to your own domain:
A one-click self-test verifies your discovery documents, that the Authorization header reaches WordPress, that credentialed responses are not cached, and a full register → PKCE → token → MCP → revoke round-trip, so you catch hosting issues before your AI clients ever do.
Every consent, tool call, hold, approval, and revocation is recorded: who did what, when, and with what outcome. Nothing an agent does is invisible.
Ship a working agent-commerce demo on day one. Read tools run instantly; writes wait for your approval:
Need your own actions? Register any ability with a filter and it flows through the same scope, grant, policy, and queue machinery automatically.
Claude (custom connectors), ChatGPT (connectors), Cursor, and any MCP client, plus the @automattic/mcp-wordpress-remote stdio proxy as a fallback. Targets the MCP authorization spec (revision 2025-11-25).
No. Agent Gateway is a one-time purchase that runs entirely on your own server. There is no monthly fee and no hosted service to pay for.
No. Install the plugin, activate it, connect from your AI client, and manage agents, permissions, and the approval queue from the WordPress admin. Developers can extend it by registering their own abilities through a filter, but that is optional.
No. The core OAuth 2.1 and MCP layer runs on plain WordPress. WooCommerce is only needed for the prebuilt commerce abilities pack, which activates automatically when WooCommerce is present.
Never. There is no SaaS backend and no phone-home. Discovery, authorization, tokens, and every agent call happen on your domain and stay on your domain.
No. Each agent is its own zero-capability principal, completely separate from your WordPress users. You grant permissions per agent and per ability, and you can revoke them live at any time.
Write actions can be held for your approval before they run, you can auto-approve only within limits you set (for example a maximum order value), and a global kill switch plus per-agent dry-run mode let you pause or simulate everything instantly.
Claude, ChatGPT, and Cursor via their standard remote-MCP connectors, and any other MCP-compliant client. Because it is built on open standards, you are not locked to one vendor.
Yes. Updates are delivered through CodeCanyon, and support is available through your item page.
== 1.0.3 (released 13 August 2026) == Initial release. + OAuth 2.1 authorization server: PKCE S256, dynamic client registration, protected-resource and authorization-server discovery metadata (RFC 9728 / RFC 8414), audience-bound tokens (RFC 8707), revocation (RFC 7009). + Agent principals with per-agent, per-ability permissions. + Human approval queue: auto-approve constraints, rate limits, global kill switch, and per-agent dry-run mode. + Append-only audit log of every consent, call, hold, approval, and revocation. + Built-in external self-test diagnostics. + Prebuilt WooCommerce abilities pack (search, stock, shipping, order status, draft orders, returns) with agent-attributed, HPOS-safe orders.
Secure by construction: all secrets are generated with a CSPRNG and stored only as SHA-256 hashes, compared in constant time; replaying a used code or refresh token revokes the entire token family; agent scopes can only ever map to virtual per-ability capabilities, never real WordPress capabilities.