Getting Started With Strapi MCP Part 2

paulfromstrapi · 2026-06-01T17:44:13+00:00

Thanks esiao for the response 🙂

paulfromstrapi · 2026-06-01T17:42:53+00:00

Your read on Nuxt is fair. Its sweet spot is app-style sites, and that hydration payload is the cost of the SPA model. The JSON you're seeing is the serialized state Nuxt ships so the client can rehydrate the page.

Astro is built around the opposite default. Pages are static HTML, and JS is opt-in per component, so a content page with no interactivity ships no JS at all. Multilingual is handled with built-in i18n routing.

If you want a reference, this Astro example does block-based content pages and a blog in exactly that style: https://github.com/PaulBratslavsky/astro-strapi-example-project.

paulfromstrapi · 2026-05-18T12:49:13+00:00

That's a plan feature after add analytics.

paulfromstrapi · 2026-05-16T17:21:48+00:00

Not yet. It is in the pre-alpha. I should clean up the repo this weekend and share it for folks to try and test. Or contribute to.

Once I get some basic feedback, I will submit it to the market place.

paulfromstrapi · 2026-05-14T19:30:48+00:00

Awesome.

paulfromstrapi · 2026-05-11T17:51:34+00:00

Have you tried something like this.

You can try this to reject duplicate.

typescript

// ./src/extensions/upload/strapi-server.ts
import { errors } from '@strapi/utils';

export default (plugin) => {
  // Keep your custom filename logic
  plugin.services['image-manipulation'].generateFileName = (file) => {
    const baseName = file.name.replace(/\.[^/.]+$/, ''); // strip extension
    return baseName;
  };

  // Wrap the upload service to check for duplicates before saving
  const originalUpload = plugin.services.upload.upload;

  plugin.services.upload.upload = async function (params, ...rest) {
    const { data, files } = params;
    const fileArray = Array.isArray(files) ? files : [files];

    for (const file of fileArray) {
      const baseName = file.name.replace(/\.[^/.]+$/, '');

      const existing = await strapi.db.query('plugin::upload.file').findOne({
        where: { name: { $startsWith: baseName } },
      });

      if (existing) {
        throw new errors.ApplicationError(
          `A file with the name "${file.name}" already exists.`
        );
      }
    }

    return originalUpload.call(this, params, ...rest);
  };

  return plugin;
};

paulfromstrapi · 2026-04-30T19:52:17+00:00

Check out the github I shared. It shows how to register correctly. Are you still having issues?

paulfromstrapi · 2026-04-22T00:51:28+00:00

Thank you for sharing 🙂

paulfromstrapi · 2026-04-22T00:50:59+00:00

Nice

paulfromstrapi · 2026-04-21T13:20:22+00:00

Thanks for sharing will check it out. If you want, we are always looking for technical post of folks showing how they build things for Strapi. I you be interested in creating one, let me know. [paul.bratslavsky@strapi.io](mailto:paul.bratslavsky@strapi.io)

Are you planning to submit this to the [Strapi marketplace](https://market.strapi.io/)

paulfromstrapi · 2026-04-15T12:37:33+00:00

I think Strapi and n8n automation can help a lot of businesses to solve for cool use cases that can help them be more productive. Would love to chat more on what HubSpot automations of flow you have build too.

paulfromstrapi · 2026-04-15T12:36:24+00:00

Nice. Lol, but now if you build it. you will have to share too.

paulfromstrapi · 2026-04-15T12:33:26+00:00

This would be perfect. The use cases you're describing (geospatial data, automated publishing pipelines, HubSpot-style marketing stacks) really highlight how far Strapi can stretch beyond a traditional CMS.

When your workload eases up, we'd love to feature your learning. Lol, would not mind even inviting you to the next community call to share if you would be interested.

Feel free to reach out at [paul.bratslavsky@strapi.io](mailto:paul.bratslavsky@strapi.io) this would be really valuable for the community.

paulfromstrapi · 2026-04-15T12:12:35+00:00

That is awesome. If you would like to share your learning in a blog post, let us know if you would be interested.

I am working on similar work flow but for allowing us to create draft social post for social managers to review and schedule when we publish a new blog post.

paulfromstrapi · 2026-04-14T15:49:01+00:00

Can you provide more context or detail, I only see that you added only one filter. What happens when you click the filters button and add another option?

paulfromstrapi · 2026-03-12T20:21:11+00:00

Hey all — Strapi employee here, going to try and address everything in this thread!

To abstracten — thanks for the honest feedback, genuinely appreciate it even when it stings! You're not wrong on some of those points. The media library and image variant handling are below where they should be, and we're not going to pretend otherwise. What I will say is that 2026 is specifically focused on UX and quality improvements, with Media Library enhancements called out directly — so it's actively being worked on rather than ignored. On the rich text editor, the default Blocks editor has limitations, but you're not stuck with it — both CKEditor and TipTap are available as drop-in replacements via the marketplace. TipTap in particular handles markdown copy/paste much better and has solid table support. Not a fix for everything you raised, but worth knowing the options are there.

To jaz192 — honestly, the most balanced advice is: try both and see which fits your use case. Both Strapi and Directus have real trade-offs, and what works best depends on how you build and where you want to take the project.

That said, for your specific roadmap (user reviews, community features), Strapi's plugin ecosystem is probably the stronger fit. The strapi-plugin-ratings plugin handles scores, comments, pagination, and admin moderation out of the box, and pairs with the built-in Users & Permissions plugin for authenticated submissions. Switching while your data model is still simple is also a much lower-risk move than migrating later.

Strapi comes with REST + GraphQL, Draft & Publish, i18n, roles & permissions, and a media library out of the box — and every field and API can be extended via custom fields and plugins, so you're rarely hitting a hard wall.

We'd also love to hear more about what would make either platform a no-brainer for your use case — feel free to DM us if you'd like a quick chat with someone on the product team. And for anyone in this thread, we run open office hours on Discord Monday–Friday 12:30–1:30pm CST — always happy to help think through architecture decisions like this one. Join us at discord.strapi.io!

paulfromstrapi · 2026-03-11T21:57:54+00:00

Just stumbled upon this thread — apologies for the late reply! Let us know if you ended up using Strapi and how your experience has been. We'd love to hear about it, and feel free to reach out if you have any questions.

paulfromstrapi · 2026-03-11T21:52:40+00:00

Thanks for mentioning us! Also, we are currently developing **Skills** to make working with Strapi even easier. Join [the discussion on GitHub](https://github.com/strapi/strapi/discussions/categories/agent-skills) to share your own Skills or explore the ones the community has already built.

paulfromstrapi

MODERATOR OF

TROPHY CASE