Content & CreativeDone with custom-built or unnamed agent Jan 14, 2026
Keep a personal website's content updated automatically
A developer's setup for automating their site's content with agents and MCP.
- What They Did
- Debbie O'Brien saved her podcast-page prompt as a Goose recipe that takes the episode URL as a parameter. Goose used the Playwright MCP to read the episode page, the Cloudinary MCP to upload the image, and then ran the dev server and checked the podcasts page. It opened a pull request through the GitHub MCP, and she reviewed the code and merged it.
- How It Went
- New podcast episodes with images were added to her Nuxt site and merged after her review. She hasn't tested it on large batches of URLs, and setup took longer than copying by hand would have.
- Worth Knowing
- Setup took longer than doing one episode manually. She still reviewed the PR, especially the Cloudinary URL, and only wrote that one recipe so far.
Try it yourself with custom-built or unnamed agent
Look at my personal website repo at [path or URL] and set up automation so its content ([blog, projects, or reading list]) updates from [source such as Notion, GitHub, or RSS]. Use an MCP server if it helps. Finished means one command refreshes the content and shows me a diff of the changes, and nothing gets deployed or committed until I approve.