<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jakub Czapski</title>
    <description>The latest articles on DEV Community by Jakub Czapski (@jakub_czapski).</description>
    <link>https://dev.to/jakub_czapski</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3967933%2F2ef53444-10fd-4644-a398-cd41fbcfd3bc.png</url>
      <title>DEV Community: Jakub Czapski</title>
      <link>https://dev.to/jakub_czapski</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jakub_czapski"/>
    <language>en</language>
    <item>
      <title>MDCMS: Open-source CMS with AI agents built in</title>
      <dc:creator>Jakub Czapski</dc:creator>
      <pubDate>Mon, 08 Jun 2026 10:40:13 +0000</pubDate>
      <link>https://dev.to/blazity-software-house/mdcms-open-source-cms-with-ai-agents-built-in-43o</link>
      <guid>https://dev.to/blazity-software-house/mdcms-open-source-cms-with-ai-agents-built-in-43o</guid>
      <description>&lt;p&gt;Out of 800+ CMSs, only a handful are built for what you actually need.&lt;/p&gt;

&lt;p&gt;Most existing options on the market make teams choose between compromises that don’t really work for them.&lt;/p&gt;

&lt;p&gt;SaaS CMS platforms give editors a user interface, but they often lead to vendor lock-in, ongoing enterprise costs, proprietary APIs, tough migrations, and workflows that don’t work well with AI.&lt;/p&gt;

&lt;p&gt;Git or Markdown-based setups are great for developers and AI agents, but they force editors to deal with code, rebuilds, pull requests, terminal commands, and unstable content processes.&lt;/p&gt;

&lt;p&gt;MDCMS fills the missing middle: a real CMS that still works like a file-based system when developers or AI agents need to handle content.&lt;/p&gt;

&lt;p&gt;What sets it apart is the unique combination of features it offers:&lt;/p&gt;

&lt;p&gt;1) You own your content. MDCMS is MIT-licensed, open-source, and self-hosted, so there’s no risk of being locked into a proprietary API.&lt;br&gt;
2) One data layer, three interfaces. Everyone on your team gets a workspace built for their needs.&lt;br&gt;
3) AI agents can work with content, config, and eventually the CMS itself through CLI/API/MCP-style workflows.&lt;br&gt;
4) Switch fast with what you already have. MDCMS detects your schema, imports your content, sets up a visual Studio, and helps you switch your CMS in just a few weeks.&lt;/p&gt;

&lt;p&gt;We welcome contributions! Feel free to share any feedback.&lt;br&gt;
Want to see more? Check out MDCMS → &lt;a href="https://mdcms.io/" rel="noopener noreferrer"&gt;https://mdcms.io/&lt;/a&gt; &lt;/p&gt;

</description>
      <category>opensource</category>
      <category>ai</category>
      <category>webdev</category>
      <category>typescript</category>
    </item>
    <item>
      <title>MDCMS – Open-source CMS with MCP-native AI agents and Markdown-first content</title>
      <dc:creator>Jakub Czapski</dc:creator>
      <pubDate>Thu, 04 Jun 2026 10:38:03 +0000</pubDate>
      <link>https://dev.to/jakub_czapski/mdcms-open-source-cms-with-mcp-native-ai-agents-and-markdown-first-content-2nn7</link>
      <guid>https://dev.to/jakub_czapski/mdcms-open-source-cms-with-mcp-native-ai-agents-and-markdown-first-content-2nn7</guid>
      <description>&lt;p&gt;Hi Dev.to! I run Blazity, a Vercel &amp;amp; Next.js software house. For context, we've done 40+ CMS migrations (Contentful, Sanity, Storyblok, WordPress), and the challenge was always the same: extract content from one proprietary system, restructure it for another, and spend 3 to 6 months on the process.&lt;/p&gt;

&lt;p&gt;The thing that kept bothering me: every one of those projects already had Markdown or MDX files that worked fine. The content was available, but no CMS could import it. Every tool forced us to start over.&lt;/p&gt;

&lt;p&gt;So we built MDCMS. One of the core functionalities is brownfield import: run cms init in your existing project directory. It reads your Markdown/MDX files, infers a typed schema from your frontmatter, and sets up a PostgreSQL-backed CMS around your existing file structure.&lt;/p&gt;

&lt;p&gt;Developers define schemas in code and sync via CLI. Marketing team gets a collaborative visual Studio. AI agents process content through the same API. Each role works in the space designed for them. MIT licensed.&lt;/p&gt;

&lt;p&gt;⭐️ &lt;a href="https://github.com/mdcms-ai/mdcms" rel="noopener noreferrer"&gt;GitHub repo here!&lt;/a&gt;&lt;br&gt;
Give it a try: npm install -g @mdcms/cli&lt;/p&gt;

&lt;p&gt;We also welcome contributions! Feel free to share any feedback.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>typescript</category>
      <category>opensource</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
