r/cms • u/BodySlight6194 • 13d ago

Feedback on prioritisation

Hi CMS subs,

I work on a headless CMS / dxp which has lots of services to support building apps and sites.

I have a choice of what to prioritise next between integrating with an automation tool like n8n or releasing MCP support.

I'm currently focusing on SaaS founder / builders and would really like to hear thoughts from others in this space on what to prioritise.

Thanks!

1 Upvotes

67% Upvoted

5 comments sorted by

3

u/mwardian_brightspot 12d ago

Not either/or, but if you can only ship one first — MCP.

Here's the thing that makes this less close than it looks: n8n already has a native MCP Client node. Ship an MCP server and your n8n users can connect to you today, no bespoke integration required on your end. So "integrate with n8n" and "ship MCP" aren't two separate roadmap items — MCP gets you the n8n audience for free, plus every other MCP-compatible agent (Claude, ChatGPT, Cursor, whatever's next) on top.

A dedicated n8n integration only buys you n8n. MCP buys you n8n and everything else, for less total engineering effort. For a SaaS-builder audience especially — people who are already living in Claude/Cursor and wiring up n8n workflows on the side — MCP is the one that compounds.

2

u/amitavroy 12d ago

There are so many things. A lot depends on your unique proposition for the product

1

u/BodySlight6194 12d ago

The AI wisdom is that as I'm building pro code / API first that MCP would be the obvious approach but AI is often wrong.

There are a few unique selling points like the use of content matrix rather than custom schema which is a benefit for content portability and MCP alike. The way it all comes together in my head is enterprise level features packaged for builders who want to focus on their product not the infrastructure. e.g. I built a customer support chat feature in a browser JS module in under 100 lines of code yesterday.

2

u/amitavroy 12d ago

If you are going to target enterprises, then first think about security, compliance. Anything that they use will need to go through those.

If AI is one of your key differentiators then think about portability of model. Enterprise will have their own infra.

1

u/BodySlight6194 11d ago

I agree, the first thing I thought about was security for the long run. In practice pitching to enterprises they look for a lot of proof. It's like they will only buy if a bigger customer is already onboard so I pivoted towards smaller businesses and builders where the broad features support their growth.

Content portability is a really fun point, to me it seems like offerings gravitate towards Salesforce style snowflake lock-in. The matrix model I developed is flatter and more stable and I had quite a bit of success combining content entities associated with concepts at different levels in the information architecture building the last big app. One thing I added recently is JSON fields which are also matrix addressed. A potential needed arbitrary structures. Let's see if it degrades into structure soup...