Playing with WordPress Studio Code, I was quite impressed with how much information about WordPress development is added as context, and that Claude or Mistral can and so use the same SKILL.md files. However as an environment, I much prefer LocalWP.
Using the same .agents/* files in a LocalWP site seems to be no real problem, but one thing Studio has and which I thought really neat is the ability to create and use screenshots during development.
Is there work being done on a MCP server and maybe a WP CLI SKILL.md? Considering that WP Engine’s communications talk a lot about AI, I would not be surprised if there was.
(I’m aware that there’s a project by 10up, but I’m hoping to be able to lazily bypass messing with git and npm).
Hi @philby - thanks for reaching out! I’m glad you brought this up.
Considering that WP Engine’s communications talk a lot about AI, I would not be surprised if there was
You would be right to not be surprised Yes, we’re working on a first release of a Local CLI tool that would allow users (or agents) to control the app and the sites it is running from wherever you’re already building - Claude in a terminal, for example. List your sites, start the right one, run WP CLI commands it, etc etc.
I’m thinking that is out in a beta release within the next 1-2 weeks, and we’ll post it here in the forums.
Thanks a lot @austinwendt – I actually did miss the release completely.
Did not have time yet to really get into it, unfortunately, but basically what I’m hoping to have in the end is WordPress Studio but on LocalWP platform and using Visual Code with Claude or Mistral instead of some built-in “Code”: Studio for its impressive integration of AI based tools (seeing Claude automatically create screenshots of a site it is developping a plugin in to debug functionality impressed me), but using Local which has been far more reliable for importing/recreating existing client sites.
I think a migration-related skill could be pretty useful here. Something that checks the local and production environments before running WP-CLI commands.
The part I’d be most careful with is wp search-replace. It would be nice to see exactly what the skill intends to change before it touches the database, especially when serialized data is involved.
Not sure how much of that the new Local CLI exposes yet. Could a skill handle those checks without needing extra tooling?
Yes, we’re working on a first release of a Local CLI tool that would allow users (or agents) to control the app and the sites it is running from wherever you’re already building - Claude in a terminal, for example. List your sites, start the right one, run WP CLI commands it, etc etc.