--- title: Connect your WordPress fleet to Claude Code and let each site remember its client's rules canonical_url: https://lolacore.com/wordpress-fleet-claude-code-mcp/ last_updated: 2026-08-14T19:22:46+00:00 plugin_version: 1.2.3 --- ## What you're actually connecting Each site with LolaCore installed exposes two things over MCP: Lola's abilities, which are the concrete actions she can run on WordPress through your plugins' public APIs, and that site's persistent memory. The reasoning comes from Claude Code on your Claude plan, so in MCP mode you don't configure provider keys on each site. You talk in your IDE, Claude Code decides which of Lola's abilities to call, and Lola runs them against the right site. The ability list is hand-curated, not a dump of everything registered on each install. That matters at fleet scale. Your client sites are all different, often loaded with plugins. Lola always works from the same focused set, so reliability doesn't depend on how messy a given client's site happens to be. ## The free stack you're teaching Lola The free core already handles WordPress itself: content, users, plugins, settings, diagnostics, everyday WooCommerce. That's 75 abilities live from minute one. On top of it, six free add-ons teach Lola the tools you already work with every day. Together they add 189 more actions on top of the core's 75. Same plugin, same data. You stop clicking through the panel and start telling Lola what you need. * **LolaCore for FSE** adds 17 actions for block themes. Lola builds custom blocks, edits templates and global styles, and previews in WordPress Playground before anything touches the live site. * **LolaCore for Elementor** adds 91 actions. Manage Elementor pages and templates from chat: assemble layouts, update global styles, and work with widgets without opening the Elementor panel. * **LolaCore for ACF** adds 26 actions. Read and write Advanced Custom Fields in plain language, including batch updates, relationship fields, and options pages. * **LolaCore for SEO** adds 22 actions. Audit and edit SEO from chat: meta descriptions, keyphrases, indexability, and bulk fixes alongside Yoast or Rank Math. * **LolaCore for Statistics** adds 18 actions. Ask about your traffic and get the number, not a dashboard: page views, referrers, and trends from WP Statistics in plain language. * **LolaCore for Forms** adds 15 actions. Work with your forms and their entries: create fields, review submissions, and clear inbox tasks without opening WPForms. Each one shares the same site memory Lola already has. Install on each client whichever ones that client uses, and you're set. ## Set up MCP for your fleet **1. Install LolaCore on each client site.** The main plugin, [LolaCore – AI Admin Agent](https://wordpress.org/plugins/lolacore/), from WordPress.org. Add whichever free add-ons that client uses, all available on WordPress.org too. **2. Generate the MCP config.** On each site, go to Lola → Settings → MCP. Create a dedicated Application Password for that site and copy the JSON it gives you. **3. Connect each site to Claude Code.** Open the MCP settings in Claude Code, paste the JSON, and give the server a name you'll recognize at a glance: client-abc-production, shop-xyz-staging. Repeat per site. With that, Claude Code sees each site's Lola abilities as available tools, and can pull each site's memory when it needs it. ## Working a fleet from your IDE **Fleet briefing** Check client-abc, shop-xyz, and blog-personal. Give me a per-site summary sorted by priority: pending updates, security findings, and whatever I noted in each site's memory last time. The interesting part isn't that it checks all three sites. It's that, for each one, it pulls back what you saved to that client's memory last session, because that memory lives on the site. **Maintenance with each client's rules** On client-abc and shop-xyz, update the plugins except Elementor and WP Rocket. Show me the preview for each site before you run anything. Every write action goes through Preview, Confirm, and Execute: Lola shows you what she's about to do before she does it. If you'd already noted "don't touch this plugin" in a client's memory, that call is there to check against. **Everyday WooCommerce** On shop-xyz, how's the week going? Give me revenue, order count, and the ones that need action. Then create a 15% coupon, code COMEBACK15, no expiry. The 13 WooCommerce abilities in the free core cover a store's daily work: revenue reports, orders that need attention, status changes, products, coupons, and categories. **Custom fields across sites (ACF)** On client-abc, raise the ACF field "season_price" by 10% across all listing-type entries. Show me the list before applying. **A custom block for one client (FSE)** On blog-personal, build a custom cookie-notice block that matches the theme's global styles, and leave it tested in Playground for me. **Traffic without the dashboard (Statistics)** On shop-xyz, what were the 5 most-viewed pages last month, and where did that traffic come from? **Content and SEO (SEO)** On blog-personal, find the 5 posts with the worst SEO score and draft optimized meta descriptions. Apply them only once I approve each one. **Elementor templates without the panel (Elementor)** On client-def, update the brand color in Elementor's global styles and check the header template still lines up. ## The step you can't skip: save the memory when you close There's a difference between the in-wp-admin chat and working over MCP, and it's worth getting straight. In the wp-admin chat, Lola saves and manages her memory on her own. You can tell her "save this to memory" if you want, but you don't have to stay on top of it. She keeps what matters by herself. Over MCP it works differently. Saving isn't automatic. When you finish working, you trigger the save with an explicit instruction: Save today's session to Lola's memory on every site we worked on. With that, Claude Code or Cursor use LolaCore's memory tool to write the session into each site's persistent memory format, leaving every client you touched updated. It's a ten-second move at the end, and it's what makes each site show up next time knowing where you left it. Make it a habit: finish the session, save, close. ## What makes a fleet with Lola different **Memory per client.** Each site builds its own history: what was done, what preferences it has, what rules you set. The more clients you run, the more those memories are worth, because they're the knowledge of your operation that used to live only in your head. They're stored on each client's own server, alongside the rest of Lola's data. **Reliability that doesn't depend on how messy the site is.** Curated abilities keep Lola's behavior steady on a clean site and on one with eighty plugins alike. **Builders from your IDE.** When a client needs something specific that no catalog plugin covers well, Lola builds it. The Plugin Builder and Block Builder ship in the free core: Lola writes a focused plugin or a custom block, tests it in Playground, and installs it inactive until you switch it on, all from the same conversation. ## Before you dive in Use a dedicated Application Password per client and revoke it when the relationship ends. Test heavier changes in staging before production. Keep an eye on your Claude plan usage, since one operation across several sites at once burns tokens. Keep backups current. And if you work with multisite, note that direct install of built plugins isn't available there: the Playground test still works, and you deploy across the network manually. ## Getting started A fleet connected over MCP takes away the constant hop between wp-admins and, more than that, takes away the weight of being your clients' memory yourself. Install LolaCore and the free add-ons you use on one site, connect it to Claude Code, and hand it a briefing. If you run several clients, start with the one that eats the most of your week. Everything in this tutorial runs on the free stack, so the only investment is the time it takes to connect your first site. Tell us in the comments how you handle client memory right now, by hand or in some system of your own. It's the part of the job nobody talks about.