StoreAgent MCP runs store MCP servers on a gateway, not the store
The WordPress plugin StoreAgent hosts its MCP server on its own gateway, with Claude and ChatGPT connecting read-only via OAuth, plus rate limits and a kill switch.
The safest place for your store's MCP server is not on your store When we built StoreAgent MCP, we decided early that the store would never run the MCP server itself It runs on our gateway instead. Claude or ChatGPT connect with OAuth (tokens last an hour or less), read-only is the default, there's a limit of about 60 calls a minute, and a kill switch if anything gets weird The usual way to do this is the other way round. The MCP server sits on the store and logs in with an application password... so every agent call is a PHP request on your production site, and nothing built in stops a runaway loop An agent stuck in a loop sends a lot of requests. I'd rather those hit our gateway than your checkout Try it free: search "StoreAgent" on http://wordpress.org