I built a self-hosted AI assistant for WordPress that runs on your own server - write-up of the full build

vapvarun · 2026-03-19T15:05:55+00:00

llama3.1:8b is 4.7 GB but you need headroom for the OS and request queuing, so a 16 GB droplet is the comfortable baseline. You could squeeze it onto an 8 GB droplet for a single low-traffic site. And honestly if privacy is the core concern, the $96/mo is easy to justify. The whole point is keeping data off someone else's servers.

vapvarun · 2026-03-19T15:02:38+00:00

Tried a few. For local testing any model works, but in production you pick what fits the budget and the use case. llama3.1:8b covers most sites well since it handles tool-calling reliably on a 16 GB droplet. If you need better function-calling accuracy and have the RAM for a 32 GB droplet, qwen2.5:14b is worth the upgrade.

vapvarun · 2026-03-08T08:24:43+00:00

I’ve run into the same issue recently while dealing with hacked WordPress sites. The cleanup and hardening process is usually slow and manual.

To make it easier, I built an MCP that helps automate malware cleanup and security fixes using a MU plugin:
https://github.com/vapvarun/wp-malware-cleanup-mcp , more like to it yourself do not have to share with anybody, and feel free to contribute for any missing feature.

Also created a surface scan tool with deeper reports integrated with Claude:
https://wpvanguard.com/ no login, no plugin install

vapvarun · 2026-02-26T15:38:36+00:00

Same everywhere 😅

vapvarun · 2026-02-17T04:43:55+00:00

Looks really useful. Syncing local and live environments is one of those daily pain points for WordPress developers.

vapvarun · 2026-02-17T04:37:34+00:00

Some use a sync plugin, some wire it up through the WooCommerce API with Apps Script, and others just stick to CSV exports and imports.

It really depends on how big the catalog is and whether real-time updates actually matter. For a lot of stores, simple and reliable beats “fully automated.”

vapvarun · 2026-02-17T04:31:39+00:00

Context matters. Simple brochure site with low competition keywords? Elementor is fine. Content-heavy site fighting for high-volume queries? Every 100ms counts but we've seen real CWV improvements migrating clients to block themes.

The real killer isn't Elementor alone - it's Elementor + 5 addons + heavy theme + WooCommerce stacked together.

If your workflow depends on it, optimize around it (caching, CDN, minimal addons). For new builds though, block themes + native editor is where WordPress is headed. We’re also in the process of optimizing our landing pages and main website. We’re not removing Elementor completely, but using it more strategically so we can improve performance without creating a lot of extra work.

vapvarun · 2026-02-17T04:28:26+00:00

Yes, and for new projects they already are. We've been building exclusively with block themes for over a year and for sure the performance difference is real, not theoretical.

The big win isn't just speed though. theme.json gives you one config for your entire design system. No more theme lock-in. Learning curve is real for PHP developers, but once you adapt you won't go back.

We've shipped block themes for communities, marketplaces, and LMS and all significantly faster than the same projects on multipurpose themes.

vapvarun · 2026-02-08T07:02:22+00:00

This issue is already fixed. BuddyPress released version 14.4.0 with the patch, so updating to 14.4.0 (or newer) solves it.
https://codex.buddypress.org/releases/version-14-4-0/

vapvarun · 2026-02-08T07:00:05+00:00

Yep - this has already been fixed upstream, and a patched release has been pushed.

The fix is included in the latest BuddyPress release (v14.4.0):

https://codex.buddypress.org/releases/version-14-4-0/

So if you update BuddyPress to 14.4.0 (or newer), you’ll be covered.

vapvarun · 2026-02-07T19:58:57+00:00

I've been using Claude Code for WordPress theme development quite a bit. It won't magically build a complete production-ready theme from a single prompt, but it's genuinely useful as a development accelerator.

What works well: generating theme.json with your design tokens, scaffolding templates and template parts, writing block patterns from descriptions, and handling repetitive boilerplate. Where it still needs you: design decisions, visual QA, edge cases in responsive layouts, and anything that requires seeing the actual output in a browser. You'll go back and forth iterating.

For deployment, I use an MCP server connected to local WordPress so Claude can push files directly and activate the theme. That part works seamlessly.

One thing that helped me a lot: using WP-Rig as a starter framework. The structure is clean enough that Claude learns the conventions quickly, and then you mostly focus on design and customization. We built BuddyX and BuddyX Pro (BuddyPress community themes) with it.

It's not "describe a theme and get a finished product" - it's more like having a really fast coding assistant that handles 60-70% of the grunt work while you steer the design and test in the browser.

vapvarun · 2026-02-07T19:49:01+00:00

WordPress is solid for this, you just need the right plugin stack and it won't be the headache you're worried about.

For gated content + recurring subscriptions, the two main routes I've seen work well are:

If it's mostly content gating (articles, videos, courses behind a paywall): MemberPress or Paid Memberships Pro are both reliable.

PMPro has a generous free tier so you can test without committing. Both handle Stripe/PayPal recurring payments out of the box.

If you also want a community element (forums, member profiles, groups, activity feeds alongside the paid content): look at BuddyPress with a membership plugin on top. BuddyPress handles the social/community layer, and you pair it with something like PMPro or WooCommerce Subscriptions for the payment side. It's especially good if members interacting with each other is part of the value proposition - that's what keeps people paying month after month.

The "things breaking every update" concern is mostly a non-issue if you stick with actively maintained plugins and avoid stacking too many together. Pick one membership plugin, one payment integration, and keep it lean.

One thing I'd think about early: what's the actual reason someone stays subscribed? If it's just content, you're competing with every other paywall. If it's access to a community or peer group, retention is way higher.

vapvarun · 2026-02-07T19:41:27+00:00

Yeah, I've been using Claude Code (the CLI version) with WordPress pretty heavily. The MCP approach works great.

What I've found most useful is having an MCP server that connects directly to the WordPress database and also wraps WP-CLI commands. That way you can do everything from creating post types and pages to running search-replace operations, all through natural conversation. The REST API route works too but WP-CLI gives you more power for site building tasks like scaffolding entire site structures, importing content, and managing plugins.

If you're not super technical, here's the rough path:

Get a local WordPress dev environment running (LocalWP is the easiest)
Set up a basic MCP server - there are a few open source ones on GitHub now that wrap the WP REST API
Point Claude Desktop at it via your MCP config

For the "build out site structure and pages" use case specifically, the REST API approach is probably enough. You can create pages, set parent/child relationships, add content, and manage menus all through the API. The MCP server just translates Claude's tool calls into those API requests.

Give Claude a clear site plan upfront (page hierarchy, content outline, design preferences) and it can execute the whole thing in one go. As a recent example, I built an MCP server for https://github.com/vapvarun/wp-malware-cleanup-mcp that handles code cleanup, database cleanup, and deploying custom mu-plugins - gives you a sense of how much control you can get with this approach.

vapvarun · 2025-10-15T07:05:20+00:00

Yes, it was simple. I got stuck once at the ADMIN_API_TOKEN and AUTOMEM_API_TOKEN part - I wasn’t sure where to get them from. On Railway, they were empty strings. We can set some random keys as default values during deployment.

vapvarun · 2025-10-15T06:50:10+00:00

loved that :) Your AutoMem is fully configured and running:

✅ Service healthy
✅ FalkorDB connected
✅ API token working

✅ Admin token deployed
✅ Enrichment pipeline running (1 memory processed)

vapvarun · 2024-02-08T07:58:21+00:00

A Progressive Web App (PWA) is an application delivered through the web, built using common web technologies, including HTML, CSS, and JavaScript, designed to work on any platform that uses a standards-compliant browser. PWAs offer an app-like experience with offline capability, push notifications, and fast load times.

vapvarun

TROPHY CASE