WordForge

My girlfriend started a pottery business and needed an online shop. Rather than lock her into Shopify’s subscription and transaction fees, I set her up on a 3€/month Hetzner VPS running WordPress and WooCommerce, giving her real, self-hosted control over her own store.

The gap was tooling: I live in AI-assisted development, but none of my usual tools spoke WordPress. WordPress’s own team had shipped the building blocks, an Abilities API and an MCP Adapter bridging it to the Model Context Protocol, but no one had implemented the actual abilities for real-world site management.

So I built WordForge, an open-source MCP server extending WordPress’s own adapter with abilities for content (posts, pages, custom post types), the media library, Gutenberg block editing, Full Site Editing theme styles, and full WooCommerce product management, auto-detected only when WooCommerce is active.

The result: she manages her shop through plain-language requests to Claude, “add a product called Bol Rustique at 35€, 3 in stock”, while the WordPress admin panel stays available whenever she wants direct control. I open-sourced it because the gap surprised me: WordPress had the foundation for AI-native management, and nobody had filled it in yet.

My role: sole creator, from infrastructure setup to the plugin architecture and every registered ability.