Community MCP Build: Content Handling

Speaker 0: My name is Wayne Eldridge. I run a company called Anamica in sunny Cape Town, South Africa. We build everything from mobile apps to custom business internal facing apps, primarily indirectus, and that's how we discovered directus at the back end. When the directors MCP server got announced, we were very excited. We've done a whole internal shift, from programming line by line to, obviously, tab completions to agentic, coding and agentic software development, with the human in the loop.

So everything's still verified by a human, but we have a whole system of, feedback loops loops, error logging, everything like that. So when the the director's MCP server, arrived, we were in the process of porting our website from Webflow, to Next. Js. Webflow did have its own built in CMS. However, we needed the customization of Directus, and we were very familiar with the product.

So when the Directus MCP server was announced, we saw a great opportunity to port all of our blogs and content, from the, web flow CMS, into directors, specifically using, autonomous agents. Typically, what we would do is self host direct us. However, you can use Directus Cloud, to initiate this as a general blog post engine itself. We used Next. Js in the front end and, obviously, Directus in the back end.

We would use Cursor and Sonnet four, whatever model that you wish to select in Cursor to take the content from, Webflow, via the Webflow MCP server, use cursor and sonnet to connect to the director's MCP server, choose an updated, updated director's blog post, and associate that content to that blog post category. We then discovered that whilst we ported several of our blogs, we still had a whole bunch of links of interesting, tech articles that we stored in Notion, and we thought ourselves, you know, we could share these links and specific content extremely quickly with the director's MCP server. We dropped in one or two links into Cursor, asked the, agent in Cursor to write a blog post about it, and send it to the MCP server associating the blog post category to, these content of the article. This happened very quickly and very seamlessly between the directors, MCP server, our agent, and the links sitting locally on our machine. We then decided to port all our links of interesting tech that we store internally at Dynamic and, put them on the websites under our resource hub.

We can also receive articles written by our copywriters, put them within our code base, and ask the director's MCP server to, post the content onto our website. And along with that, update the website, which is written in Next. Js with any SEO, requirements that has been picked up by the content of the article itself, or without leaving cursor, linked to a director's MCP, and directors either sitting on a self hosted instance or, if you wish, in the directors cloud.