Ivars Bariss

@strapijs Great call to be part of! Excited to figure out other ways we'll use the new Strapi MCP!

🚀 Exciting updates from the June Strapi Community Call! 👉 Full video: strapi.link/4v1kV7w In case you missed it, we held a Community Call yesterday covering the latest product updates, engineering highlights, and community contributions. Here are the highlights: ✅ Strapi is focusing on stability and AI innovation (Marco Autiero) ✅ Strapi MCP Server Launch (@codingthirty) ✅ MCP Chat Plugin for Non-Technical Users (Raul Balestra) ✅ Automating Marketing with AI (@IvarsBariss) ✅ Introduction of the Skills Repository (@codingthirty) A huge thanks to the community for their contributions. Strapi’s quality is truly a shared responsibility. 💜 👉 Full video: strapi.link/4v1kV7w

I add content to our CMS by chatting with Claude now. no forms, no copy-paste. strapi asked me to show how at their next community call: luma.com/erseos23

I love seeing people push Strapi in directions we didn’t explicitly design for. @IvarsBariss, an active Strapi community member, published a post explaining how to use n8n with Strapi 5. The workflow has `availableInMCP` enabled, which allows any agent to use it! This comes right after the n8n case study (330k pages managed in Strapi, through n8n) we published 10 days ago. Content Operations become increasingly important as we all must ship content at the speed of AI.

Refreshed our company logo today using Figma Make. Described what I wanted, it iterated, gave me download options. Few minutes total. Certain tasks don't need a long process anymore. They need a good prompt.

found out devs were averaging 19.65 hrs/week everyone knew btw turns out the underuse was on purpose. no visibility into contractors = the slack was the fire plan fixed it: jira, workload tracker, backup dev on every project same team. 2x revenue in a year ibsolutions.dev/insights/hope-…

In 10+ companies I've worked with, someone ends up owning the web layer full time because writers and web people don't speak the same language. That translation gap is one of the clearest spots for AI to actually help. Not replace anyone. Just help both sides see what the other sees.

10+ years of integrations. The failure pattern is almost always the same. Not the tool. The process was already broken. Automation amplifies — feed it mess, you get faster mess. Make sure you like what you're multiplying before you start building. #WorkflowAutomation #IBSolutions

Many ops problems aren't resource problems. They're visibility problems. At Solspace, devs averaged 19.65 hrs/week. Not laziness. The workload was just invisible, so nobody could allocate it. Once I could see it, revenue doubled. Your growth side has the same blind spots.

AI writes the code. I steer it away from debt. 2 years in: planning mode first for larger features, then review what ships. @cursor_ai knows what's called where. Still generates debt. Fast dev without review cycles is just faster debt accumulation. #Cursor #WebDevelopment

AI wrote the draft in 5 minutes. Publishing still took 15 minutes of manual steps. That's the relay problem. Built a custom n8n workflow + MCP so Claude handles it end-to-end. Draft to published, no CMS access needed.

Nobody at the client could explain how their own integration worked. Not fully. Fanucworld's ERP sync had passed through multiple dev teams. Partial docs, no complete picture. Monthly integration errors. Built the full map first. Then stabilized. Errors dropped to zero. Multi-team handoffs fragment knowledge, not just code.

I've watched well-built systems get quietly abandoned over a single inconvenient step. Friction does not just slow things down. It builds hesitation, breaks consistency, and kills the compounding value you were building toward.

Gave the AI Growth Director the ability to self-assign tasks. First 12 hours: 7 done, one run 21 times. Each fix cycle is shorter than the last. Enough cycles and it just runs.

2-5x more tasks handled with Claude, our AI Growth Director, than I could in a direct session. It checks every 10 min, picks up assigned tasks, does the work, writes a resolution note, reassigns to me for review. No conversation needed. ibsolutions.dev/insights/claud…

Starting Dev Fridays. Practical notes for developers building AI tools, or helping their business teams get there. First one: create a @cursor_ai profile per project (Settings > Profile), then set a distinct color theme for each. You'll always know which project you're in before you type.

I built an AI growth director. We plan, discuss, and refine posts together. My job is the judgment, not the admin. @claudeai Project + @nocodb + @n8n_io . I decide the angle, we refine the draft, I approve. 20 minutes per session. ibsolutions.dev/insights/ai-gr…

Most AI reliability issues aren't about the model. They're about context. When it doesn't have the right info, you compensate manually: re-upload, copy-paste, repeat yourself every session. Context isn't a setup task. It's a structural problem.

@pierre_burgy Oh, there were no technical issues with Strapi! I just tried to point Claude to your public guide (strapi.io/integrations/a…) to use it like a documentation to increase chances of Claude to one-shot Strapi integration. I wonder if we want to allow LLMs to read Strapi website.

@IvarsBariss Did you give Claude a Strapi API key? Alternative: open access in Users & Permissions forum.strapi.io/t/why-am-i-get…

@pierre_burgy my AI dev (Claude) is not allowed to read how to easily connect Strapi CMS to Astro ⏺ Fetch(strapi.io/integrations/a…) ⎿ Error: Request failed with status code 403

@pierre_burgy Despite that, @claudeai was able to one shot @astrodotbuild <-> @strapijs integration!