For/WORDPRESS AGENCIES
CRM, projects, time, and invoicing, plus MCP-connected access to every client WordPress and WooCommerce site. AI agents handle the recurring site ops so your team ships work, not tickets.
Helm is an AI work platform for WordPress agencies. Run client relationships, projects, time tracking, and invoicing on one system, and manage every client's WordPress (and WooCommerce) site directly from the platform via Helm's site connections, which use the Model Context Protocol to give your AI agents real read/write access to posts, media, products, orders, and site settings.
Why wordpress agencies run on Helm
Most WordPress agencies run five or more tools in parallel: a site management dashboard (ManageWP, MainWP), a CRM, a PM tool, a time tracker, and an invoicing/accounting app. Each one stores a different piece of the same client, and the context never crosses the seams. Helm collapses those into one platform where the site, the project, the hours, and the invoice are the same record.
Plugin updates, content edits, comment moderation, user management, media uploads. The kind of low-skill recurring work that has to happen but shouldn't need a senior developer. In Helm, AI agents with scoped site access handle those routinely. A Content Strategist agent can publish a drafted post; an Account Manager agent can update the about page; an Operations Manager agent can flag plugin update backlogs.
Clients on WooCommerce need product catalog updates, order questions, refund processing, coupon management, and stock monitoring on top of standard WordPress work. Helm's WordPress integration auto-detects WooCommerce and unlocks a second set of agent scopes: products, orders, customers, coupons, analytics, shipping, and tax.
When a client asks about the decision behind their homepage hero or the plugin choice from two years ago, the answer is in Slack archives, a Google Doc, or someone's head. In Helm, every email, project, edit, and agent run accrues to the client account. Team turnover doesn't wipe the context. It stays with the workspace.
Most WP agencies bill flat monthly retainers and never actually reconcile what was delivered. Time tracking (rolled into retainers with allocation tracking) plus agent-generated activity summaries make it explicit. You see over- and under-consumption before invoice time, and the Payment Recovery agent chases anyone who pays late.
Apps a WordPress agency actually uses
AI agents for wordpress agencies
Pricing
Helm is priced per workspace, not per seat. When your AI staff help a smaller team do the work of a bigger one, your bill doesn't go up for being lean. All 12 apps are included on every plan.
See plans and pricingFAQ
Helm connects to client WordPress sites using the Model Context Protocol (MCP). The target site runs an mcp-adapter plugin that exposes WP endpoints as MCP tools. Authentication uses WordPress Application Passwords over basic auth. Because it's MCP, Helm doesn't maintain per-version WP REST API code. The adapter on the target site handles protocol translation.
Today: the mcp-adapter plugin on each client site plus a WordPress Application Password for Helm. MCP adapter support is heading into WordPress 7.0 core (projected April 2026), which means it will be built in for future sites. Until then, plugin-based adoption is the path.
For most workflows, yes. Helm agents can do the content, media, taxonomy, user, plugin, and settings operations those tools handle. Where Helm is weaker today: bulk core/plugin updates across many sites in one click (a dashboard-native ManageWP/MainWP strength). On the roadmap.
Yes. WooCommerce is a first-class sub-module. When the WP connection is established, Helm auto-detects WooCommerce and unlocks a second set of scopes: products (read/write), orders (read/write), customers (read/write), coupons (read/write), analytics (read), shipping & tax (read/write), and store settings (read/write). Agents with those scopes can manage e-commerce operations directly.
Site connections (WordPress, WooCommerce, and other platforms via the same MCP architecture) are a Pro-tier feature. Starter plans don't include site connections. Business tier adds white-label client portal and broader guest-seat allocations that help when your clients need portal access.
Per agent, per site, per scope. You can give a Content Strategist agent 'content:write' on one client site (so it can publish posts) and read-only on another. You can give a developer agent 'settings:write' on staging sites but restrict production to 'settings:read'. Assignments can be scoped to specific projects, specific agents, or both.
Every agent action on a connected site is logged on the agent_runs record with the specific tool call, parameters, and timestamp. Authentication uses Application Passwords (revocable from WP-Admin). You can also restrict the adapter plugin's permitted scopes server-side.
Per-workspace pricing. All 12 apps included. AI agents come standard.