[{"data":1,"prerenderedAt":429},["ShallowReactive",2],{"footer-primary":3,"footer-secondary":93,"footer-description":119,"mcp-showcase-ai-in-directus":121,"mcp-showcase-ai-in-directus-next":164,"sales-reps":177},{"items":4},[5,29,49,69],{"id":6,"title":7,"url":8,"page":8,"children":9},"522e608a-77b0-4333-820d-d4f44be2ade1","Solutions",null,[10,15,20,25],{"id":11,"title":12,"url":8,"page":13},"fcafe85a-a798-4710-9e7a-776fe413aae5","Headless CMS",{"permalink":14},"/solutions/headless-cms",{"id":16,"title":17,"url":8,"page":18},"79972923-93cf-4777-9e32-5c9b0315fc10","Backend-as-a-Service",{"permalink":19},"/solutions/backend-as-a-service",{"id":21,"title":22,"url":8,"page":23},"0fa8d0c1-7b64-4f6f-939d-d7fdb99fc407","Product Information",{"permalink":24},"/solutions/product-information-management",{"id":26,"title":27,"url":28,"page":8},"63946d54-6052-4780-8ff4-91f5a9931dcc","100+ Things to Build","https://directus.io/blog/100-tools-apps-and-platforms-you-can-build-with-directus",{"id":30,"title":31,"url":8,"page":8,"children":32},"8ab4f9b1-f3e2-44d6-919b-011d91fe072f","Resources",[33,37,41,45],{"id":34,"title":35,"url":36,"page":8},"f951fb84-8777-4b84-9e91-996fe9d25483","Documentation","https://docs.directus.io",{"id":38,"title":39,"url":40,"page":8},"366febc7-a538-4c08-a326-e6204957f1e3","Guides","https://docs.directus.io/guides/",{"id":42,"title":43,"url":44,"page":8},"aeb9128e-1c5f-417f-863c-2449416433cd","Community","https://directus.chat",{"id":46,"title":47,"url":48,"page":8},"da1c2ed8-0a77-49b0-a903-49c56cb07de5","Release Notes","https://github.com/directus/directus/releases",{"id":50,"title":51,"url":8,"page":8,"children":52},"d61fae8c-7502-494a-822f-19ecff3d0256","Support",[53,57,61,65],{"id":54,"title":55,"url":56,"page":8},"8c43c781-7ebd-475f-a931-747e293c0a88","Issue Tracker","https://github.com/directus/directus/issues",{"id":58,"title":59,"url":60,"page":8},"d77bb78e-cf7b-4e01-932a-514414ba49d3","Feature Requests","https://github.com/directus/directus/discussions?discussions_q=is:open+sort:top",{"id":62,"title":63,"url":64,"page":8},"4346be2b-2c53-476e-b53b-becacec626a6","Community Chat","https://discord.com/channels/725371605378924594/741317677397704757",{"id":66,"title":67,"url":68,"page":8},"26c115d2-49f7-4edc-935e-d37d427fb89d","Cloud Dashboard","https://directus.cloud",{"id":70,"title":71,"url":8,"page":8,"children":72},"49141403-4f20-44ac-8453-25ace1265812","Organization",[73,78,84,88],{"id":74,"title":75,"url":76,"page":77},"1f36ea92-8a5e-47c8-914c-9822a8b9538a","About","/about",{"permalink":76},{"id":79,"title":80,"url":81,"page":82},"b84bf525-5471-4b14-a93c-225f6c386005","Careers","#",{"permalink":83},"/careers",{"id":85,"title":86,"url":87,"page":8},"86aabc3a-433d-434b-9efa-ad1d34be0a34","Brand Assets","https://drive.google.com/drive/folders/1lBOTba4RaA5ikqOn8Ewo4RYzD0XcymG9?usp=sharing",{"id":89,"title":90,"url":8,"page":91},"8d2fa1e3-198e-4405-81e1-2ceb858bc237","Contact",{"permalink":92},"/contact",{"items":94},[95,101,107,113],{"id":96,"title":97,"url":8,"page":98,"children":100},"8a1b7bfa-429d-4ffc-a650-2a5fdcf356da","Cloud Policies",{"permalink":99},"/cloud-policies",[],{"id":102,"title":103,"url":81,"page":104,"children":106},"bea848ef-828f-4306-8017-6b00ec5d4a0c","License",{"permalink":105},"/bsl",[],{"id":108,"title":109,"url":81,"page":110,"children":112},"4e914f47-4bee-42b7-b445-3119ee4196ef","Terms",{"permalink":111},"/terms",[],{"id":114,"title":115,"url":81,"page":116,"children":118},"ea69eda6-d317-4981-8421-fcabb1826bfd","Privacy",{"permalink":117},"/privacy",[],{"description":120},"\u003Cp>A composable backend to build your Headless CMS, BaaS, and more. \u003C/p>",{"id":122,"slug":123,"vimeo_id":124,"description":125,"tile":126,"length":127,"resources":8,"people":8,"episode_number":128,"published":129,"title":130,"video_transcript_html":131,"video_transcript_text":132,"content":8,"status":133,"episode_people":134,"recommendations":146,"season":147,"seo":163},"3bf8ea55-3ff8-4dc8-937b-093ca713b8a9","ai-in-directus","1138986971","Rijk shared how we're approaching AI at Directus.","b2888cf3-877e-439a-a153-62e152f40260",2,3,"2025-11-20","Our Perspective on AI in Directus","\u003Cp>Speaker 0: Hello. It's Reik van Zonthe, cofounder and CTO here at Directus. Very excited with this MCP launch. Very excited to see what you're gonna integrate it with and what new use cases you might find. For this segment, I was asked to go in a little bit deeper on the philosophy of artificial intelligence here at Directus, how we treat it right now, how we're planning on using it now and in the future, and what it means for our end users.\u003C/p>\u003Cp>So over time, over the last months and years, we've seen a lot of different directions that AI can take, a lot of possibilities that were unlocked. Some of them very exciting and real. Some of them a little bit silver bullet magic. At the end of the day, for us, it's all about helping our users achieve their goals in the most efficient and easy to use way as possible. We're not here to just replace a bunch of tasks that a person might have to do.\u003C/p>\u003Cp>We're here to help you out get to your results faster. With that in mind, we're really treating this more as a collaboration tool rather than an automation tool. Christina will do a little segment on that later, so keep watching. We found that LLMs are pretty great at helping unblock users in tasks they're taking, but do wanna make sure that we offer those LLM tools when and where they make sense. So for our very first deep dive here into AI, we started with MCP as the focus area.\u003C/p>\u003Cp>That allows our users to be unblocked when using third party tools like Claw, JetGPT, Recursor, or any other tool that supports MCP, and allow them to use their content, their data within Directus from those tools directly. When it comes to AI use, we obviously have to make sure that we have some very strict control about what an LM is allowed to read, what it is allowed to do with your data. And in general, this this fits in neatly with DirectUs' permission system because we, of course, through policies in our RBAC system, we have some very strict access control in place. The same applies for your MCP, usage. In general, we're implementing AI here as a carefully considered approach with that real user value rather than gimmicky for the sake of it.\u003C/p>\u003Cp>I'm incredibly excited to see what you will integrate our MCP endpoint with. Please do let me know as well. As this technology progresses, we're seeing a lot more interesting use cases, things we might have never even thought of on how to use it. So please let us know all of your thoughts, feelings, concerns, cool experiments, and everything else on community.directus.ao. And keep your eyes peeled because we have a lot more cool AI stuff coming in the near future.\u003C/p>\u003Cp>Thank you.\u003C/p>","Hello. It's Reik van Zonthe, cofounder and CTO here at Directus. Very excited with this MCP launch. Very excited to see what you're gonna integrate it with and what new use cases you might find. For this segment, I was asked to go in a little bit deeper on the philosophy of artificial intelligence here at Directus, how we treat it right now, how we're planning on using it now and in the future, and what it means for our end users. So over time, over the last months and years, we've seen a lot of different directions that AI can take, a lot of possibilities that were unlocked. Some of them very exciting and real. Some of them a little bit silver bullet magic. At the end of the day, for us, it's all about helping our users achieve their goals in the most efficient and easy to use way as possible. We're not here to just replace a bunch of tasks that a person might have to do. We're here to help you out get to your results faster. With that in mind, we're really treating this more as a collaboration tool rather than an automation tool. Christina will do a little segment on that later, so keep watching. We found that LLMs are pretty great at helping unblock users in tasks they're taking, but do wanna make sure that we offer those LLM tools when and where they make sense. So for our very first deep dive here into AI, we started with MCP as the focus area. That allows our users to be unblocked when using third party tools like Claw, JetGPT, Recursor, or any other tool that supports MCP, and allow them to use their content, their data within Directus from those tools directly. When it comes to AI use, we obviously have to make sure that we have some very strict control about what an LM is allowed to read, what it is allowed to do with your data. And in general, this this fits in neatly with DirectUs' permission system because we, of course, through policies in our RBAC system, we have some very strict access control in place. The same applies for your MCP, usage. In general, we're implementing AI here as a carefully considered approach with that real user value rather than gimmicky for the sake of it. I'm incredibly excited to see what you will integrate our MCP endpoint with. Please do let me know as well. As this technology progresses, we're seeing a lot more interesting use cases, things we might have never even thought of on how to use it. So please let us know all of your thoughts, feelings, concerns, cool experiments, and everything else on community.directus.ao. And keep your eyes peeled because we have a lot more cool AI stuff coming in the near future. Thank you.","published",[135],{"people_id":136},{"id":137,"first_name":138,"last_name":139,"avatar":140,"bio":141,"links":142},"23ebcf2c-4374-4f5c-8198-f8ad497fd856","Rijk","van Zanten","7ef9652f-3835-432c-a43a-c5fe13001f31","CTO of Directus",[143],{"url":144,"service":145},"https://directus.io/team/rijk-van-zanten","website",[],{"id":148,"number":149,"year":150,"episodes":151,"show":160},"49af1154-dd24-49c1-a1fd-fb2da0a4484b",1,"2025",[152,153,122,154,155,156,157,158,159],"f1b56b45-9398-41c1-becd-1d08d15e593d","629c73cb-a886-4db1-9e45-a604316de145","f1c9f6ee-8760-4719-8834-e4da28f9b3eb","7df39746-4a7e-4916-ba9a-71c1fa291944","437dea6b-a229-449c-9437-3f6620c2898d","95ed81c1-d6f4-4f12-817c-ca7aaeb9ac85","3ac5e6eb-111e-4bcf-b2ab-66e70712b3a8","1848dd2c-dbff-4361-9571-eb64a629c46d",{"title":161,"tile":162},"MCP Showcase","ec743a55-2bce-414f-aa55-2c3aa3b32b6b",{"title":8,"meta_description":8},{"id":154,"slug":165,"season":148,"vimeo_id":166,"description":167,"tile":168,"length":128,"resources":8,"people":8,"episode_number":169,"published":129,"title":170,"video_transcript_html":171,"video_transcript_text":172,"content":8,"seo":173,"status":133,"episode_people":174,"recommendations":176},"collaborative-cms-mcp","1138969642","Christina talks through what we mean at Directus by 'collaborative CMS' and how the MCP is part of the story.","3407ff52-ee9a-47c3-966b-e3ebd4933606",4,"What is a Collaborative CMS?","\u003Cp>Speaker 0: Hi. I'm Christina. I'm director of product marketing at Directus. And I'm here to clear up one question. So what does collaborative CMS mean?\u003C/p>\u003Cp>The problem with CMS is has always been that any given product is geared either to developers who are building a CMS for their colleagues or their clients, or for people who are the nontechnical end users of the CMS that the devs are building. So marketing tends to think mainly in campaigns, narratives, and speed to market. Engineering tends to think mainly in data structures, validation rules, and system integrity. So this isn't a skills gap between them. It's something else.\u003C/p>\u003Cp>The result is that developer focused platforms give you power and flexibility, but they're opaque to non platforms give you power and flexibility, but they're opaque to non technical users. User friendly platforms make content editing accessible, but they constrain what the developers can build. Every time you build a CMS, you have to pick your poison and choose an architectural trade off. What we're exploring though with our new MCP tool at Directus and what we've implemented natively is bridging that divide. And here's what it looks like.\u003C/p>\u003Cp>A developer can build and change collections through the natural language interface of the MCP so that they can ship faster. You can add and delete fields, insert data into your collections, build automations like flows, edit existing collections, and create multiple new collections while still configuring all the kinds of fields that are added, like making them non nullable or adding conditions, setting up validation rules, and of course, creating relationships. Meanwhile, a marketer can describe what they need in their own language. They can use the MCP to completely change the brand tone of voice and pieces of writing, edit length, shorten content, generate SEO metadata, and alter slugs. Of course, they can update items and blog posts at scale and like you'd expect, they can create new content in bulk.\u003C/p>\u003Cp>So whichever user is tasked with doing something like importing the entire product catalog along with pricing tiers and regional variations, the AI understands this request and the underlying data schema creating properly structured entries with the right relationships and validation that developers have previously established. So this is the bridge between what developers and marketers traditionally do independently. The MCP allows either person to handle that middle work, and that speeds up both teams. And this is what we mean by collaborative CMS. And the MCP becomes a natural language interface for people to do all kinds of work together.\u003C/p>\u003Cp>Both technical and non technical users working in the same system, speaking in their own language without needing to translate their needs into another context or language. And what we're seeing so far is development teams setting up robust data models once. Marketing teams operating within those guardrails at their natural velocity. There's no tickets, no waiting, no translation errors, and it's an end to all the rework. So could natural language interfaces remove communication friction between teams?\u003C/p>\u003Cp>We think so. We're seeing it happen with our MCP integration. Companies are already using it to change how their teams work together. We're excited for you to try it. Let us know what you think.\u003C/p>","Hi. I'm Christina. I'm director of product marketing at Directus. And I'm here to clear up one question. So what does collaborative CMS mean? The problem with CMS is has always been that any given product is geared either to developers who are building a CMS for their colleagues or their clients, or for people who are the nontechnical end users of the CMS that the devs are building. So marketing tends to think mainly in campaigns, narratives, and speed to market. Engineering tends to think mainly in data structures, validation rules, and system integrity. So this isn't a skills gap between them. It's something else. The result is that developer focused platforms give you power and flexibility, but they're opaque to non platforms give you power and flexibility, but they're opaque to non technical users. User friendly platforms make content editing accessible, but they constrain what the developers can build. Every time you build a CMS, you have to pick your poison and choose an architectural trade off. What we're exploring though with our new MCP tool at Directus and what we've implemented natively is bridging that divide. And here's what it looks like. A developer can build and change collections through the natural language interface of the MCP so that they can ship faster. You can add and delete fields, insert data into your collections, build automations like flows, edit existing collections, and create multiple new collections while still configuring all the kinds of fields that are added, like making them non nullable or adding conditions, setting up validation rules, and of course, creating relationships. Meanwhile, a marketer can describe what they need in their own language. They can use the MCP to completely change the brand tone of voice and pieces of writing, edit length, shorten content, generate SEO metadata, and alter slugs. Of course, they can update items and blog posts at scale and like you'd expect, they can create new content in bulk. So whichever user is tasked with doing something like importing the entire product catalog along with pricing tiers and regional variations, the AI understands this request and the underlying data schema creating properly structured entries with the right relationships and validation that developers have previously established. So this is the bridge between what developers and marketers traditionally do independently. The MCP allows either person to handle that middle work, and that speeds up both teams. And this is what we mean by collaborative CMS. And the MCP becomes a natural language interface for people to do all kinds of work together. Both technical and non technical users working in the same system, speaking in their own language without needing to translate their needs into another context or language. And what we're seeing so far is development teams setting up robust data models once. Marketing teams operating within those guardrails at their natural velocity. There's no tickets, no waiting, no translation errors, and it's an end to all the rework. So could natural language interfaces remove communication friction between teams? We think so. We're seeing it happen with our MCP integration. Companies are already using it to change how their teams work together. We're excited for you to try it. Let us know what you think.","bad4717c-1b52-4ec0-a2e7-75ba94a65b42",[175],"8b786101-b7a5-498f-b45b-bf9450894079",[],{"reps":178},[179,235],{"name":180,"sdr":8,"link":181,"countries":182,"states":184},"John Daniels","https://meet.directus.io/meetings/john2144/john-contact-form-meeting",[183],"United States",[185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234],"Michigan","Indiana","Ohio","West Virginia","Kentucky","Virginia","Tennessee","North Carolina","South Carolina","Georgia","Florida","Alabama","Mississippi","New York","MI","IN","OH","WV","KY","VA","TN","NC","SC","GA","FL","AL","MS","NY","Connecticut","CT","Delaware","DE","Maine","ME","Maryland","MD","Massachusetts","MA","New Hampshire","NH","New Jersey","NJ","Pennsylvania","PA","Rhode Island","RI","Vermont","VT","Washington DC","DC",{"name":236,"link":237,"countries":238},"Michelle Riber","https://meetings.hubspot.com/mriber",[239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271,272,273,274,275,276,277,278,279,280,281,282,283,284,285,286,287,288,289,290,291,292,293,294,295,296,297,298,299,300,301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317,318,319,320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337,338,339,340,341,342,343,344,345,346,347,348,349,350,351,352,353,354,355,356,357,358,359,360,361,362,363,364,365,366,367,368,369,370,371,372,373,374,375,376,377,378,379,380,381,382,383,384,385,386,387,388,389,390,391,392,393,394,395,396,397,398,399,400,401,402,403,404,405,406,407,408,409,410,411,412,413,414,415,416,417,418,419,420,421,422,423,424,425,426,216,427,428],"Albania","ALB","Algeria","DZA","Andorra","AND","Angola","AGO","Austria","AUT","Belgium","BEL","Benin","BEN","Bosnia and Herzegovina","BIH","Botswana","BWA","Bulgaria","BGR","Burkina Faso","BFA","Burundi","BDI","Cameroon","CMR","Cape Verde","CPV","Central African Republic","CAF","Chad","TCD","Comoros","COM","Côte d'Ivoire","CIV","Croatia","HRV","Czech Republic","CZE","Democratic Republic of Congo","COD","Denmark","DNK","Djibouti","DJI","Egypt","EGY","Equatorial Guinea","GNQ","Eritrea","ERI","Estonia","EST","Eswatini","SWZ","Ethiopia","ETH","Finland","FIN","France","FRA","Gabon","GAB","Gambia","GMB","Ghana","GHA","Greece","GRC","Guinea","GIN","Guinea-Bissau","GNB","Hungary","HUN","Iceland","ISL","Ireland","IRL","Italy","ITA","Kenya","KEN","Latvia","LVA","Lesotho","LSO","Liberia","LBR","Libya","LBY","Liechtenstein","LIE","Lithuania","LTU","Luxembourg","LUX","Madagascar","MDG","Malawi","MWI","Mali","MLI","Malta","MLT","Mauritania","MRT","Mauritius","MUS","Moldova","MDA","Monaco","MCO","Montenegro","MNE","Morocco","MAR","Mozambique","MOZ","Namibia","NAM","Niger","NER","Nigeria","NGA","North Macedonia","MKD","Norway","NOR","Poland","POL","Portugal","PRT","Republic of Congo","COG","Romania","ROU","Rwanda","RWA","San Marino","SMR","São Tomé and Príncipe","STP","Senegal","SEN","Serbia","SRB","Seychelles","SYC","Sierra Leone","SLE","Slovakia","SVK","Slovenia","SVN","Somalia","SOM","South Africa","ZAF","South Sudan","SSD","Spain","ESP","Sudan","SDN","Sweden","SWE","Tanzania","TZA","Togo","TGO","Tunisia","TUN","Uganda","UGA","United Kingdom","GBR","Vatican City","VAT","Zambia","ZMB","Zimbabwe","ZWE","UK","Germany","Netherlands","Switzerland","CH","NL",1773850435476]