Hi all. After using Laravel and Laravel Boost in a couple of projects, I saw the benefit of having a MCP server inside the project for faster debugging and development. So here comes the MCP server for the Roots stack for those of you that are using LLMs for your work 
Open to any feedback or questions.
Awesome idea 
starred it and will try it out when I have some time. Thanks!
Came here to thank you for making this, exactly what I was looking for, will check it out on an upcoming new build. But it’s implied in that README.md you might have to surrender your repo.
Cool! Can I also use this purely for a Sage theme that is not in a Bedrock installation?
@Leon_Gotje I haven’t tested this. I think it should be possible as long as you install it inside the theme folder (it uses Acorn under the hood). Let me know how it goes and if fixes are needed.
@nbyloff Happy to surrender the repo to the Roots team!
Hey TJ! Really appreciate you putting this together and sharing it
Clearly a lot of work went into it and people are excited about it
I’ve been thinking a bit about the technical direction
Our stack is already pretty CLI-native which agents can use directly: WP-CLI, wp acorn, Composer, Trellis.
But Substrate’s value is the Roots-specific patterns that an agent can’t infer on its own
What I’d love to see on the Roots side is agent skills with structured markdown that captures how Sage themes are put together, Blade component conventions, Bedrock deploy patterns, service provider architecture, etc.
Skills are more lightweight in context/tokens than an always-on MCP server
Substrate already gets us partway there by mapping the inventory of what an agent needs to understand about a Roots project which is huge 
. That plus the resources/guidelines content could translate pretty directly into skill files.
Would you be up for collaborating on something like that? The groundwork you already laid would be a big head start
What I’m leaning towards: individual SKILLS.md files in repos for our major projects 
