# AI MCP server for Roots Stack (Bedrock, Acorn, Sage)

**URL:** https://discourse.roots.io/t/ai-mcp-server-for-roots-stack-bedrock-acorn-sage/30119
**Category:** showcase
**Tags:** skills, sage11, bedrock, sage10, acorn
**Created:** 2026-01-14T10:59:42Z
**Posts:** 9

## Post 1 by @trajche — 2026-01-14T10:59:42Z

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 :slight_smile:

Open to any feedback or questions.

> **[GitHub - digitalnodecom/substrate: AI MCP for Development with Bedrock, Acorn, Sage.](https://github.com/digitalnodecom/substrate)**
>
> AI MCP for Development with Bedrock, Acorn, Sage.

---

## Post 2 by @eduwass — 2026-01-17T01:39:34Z

Awesome idea :clap: starred it and will try it out when I have some time. Thanks!

---

## Post 3 by @nbyloff — 2026-02-05T03:57:59Z

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.

 ![kalkite](https://discourse.roots.io/uploads/default/original/2X/1/123df150124ba2b83946cea89d26d751dfc6b735.jpeg)

---

## Post 4 by @Leon_Gotje — 2026-02-14T13:55:14Z

Cool! Can I also use this purely for a Sage theme that is not in a Bedrock installation?

---

## Post 5 by @trajche — 2026-03-15T01:18:28Z

@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! :slight_smile:

---

## Post 6 by @ben — 2026-03-15T14:42:50Z

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 :heart:. That plus the [`resources/guidelines`](https://github.com/digitalnodecom/substrate/tree/main/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

---

## Post 7 by @ben — 2026-05-04T02:48:14Z

What I’m leaning towards: individual `SKILLS.md` files in repos for our major projects :eyes:

---

## Post 8 by @Zak_Core — 2026-05-21T08:32:57Z

@ben having a central repository for Roots based skills sounds good. Is there any kind of roadmap for this?

---

## Post 9 by @ben — 2026-05-21T16:16:56Z

Honest answer: we don’t do roadmaps, and Roots is in real need of more sponsor funding to make dedicated time for ecosystem work possible.

Sponsorships have dropped significantly over the past year. Individual sponsorships at $10/month genuinely add up — they’re what allow me to prioritize Roots work over client work.

For context: Roots funding doesn’t just pay me. It also covers hosting and infra, domains, licenses, AI tokens, paying other team and community members for their contributions, etc. What’s left over to pay myself works out to less than a quarter of my client rate. Gotta put food on the table, so client work has to take priority right now. More sponsors = more hours I can put into Roots.

If you or your company get value from Roots, please consider sponsoring: [Sponsor @roots on GitHub Sponsors · GitHub](https://github.com/sponsors/roots)